systray.py crashed with SIGSEGV in g_type_module_use()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed after reboot with repeated message
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-0ubuntu5
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
W [14/Sep/
W [14/Sep/
Date: Wed Sep 14 22:57:39 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Deskjet-
MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-USB3
PackageArchitec
Papersize: a4
PpdFiles: Deskjet-
ProcCmdline: python /usr/bin/hp-systray
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x49c60b: mov 0x10(%rax),%rdi
PC (0x0049c60b) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
?? () from /usr/lib/
g_type_module_use () from /usr/lib/
gtk_theme_
?? () from /usr/lib/
?? () from /usr/lib/
Title: systray.py crashed with SIGSEGV in g_type_module_use()
UpgradeStatus: Upgraded to oneiric on 2011-09-12 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/04/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-785GMT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-MA785GMT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 #632066, 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.