systray.py crashed with SIGSEGV in g_return_if_fail_warning()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Starting hplip via hplip-gui led to crash.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.5-1ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-4-generic-pae i686
NonfreeKernelMo
Architecture: i386
Date: Mon Jul 11 20:55:16 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: LENOVO 0221A16
PackageArchitec
Papersize: a4
ProcCmdline: python /usr/bin/hp-systray --force-startup
ProcEnviron:
LANGUAGE=de_AT:de
LANG=de_AT.UTF-8
SHELL=/bin/bash
LC_CTYPE=C
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x80dc8f4: mov 0x8(%eax),%eax
PC (0x080dc8f4) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
g_return_
gtk_widget_
QGtkStyle:
QScrollBar:
QAbstractScrol
Title: systray.py crashed with SIGSEGV in g_return_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/05/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 85ET39WW (1.12 )
dmi.board.name: 0221A16
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 0221A16
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #809009, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.