systray.py crashed with SIGSEGV in g_type_module_use()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
First login after dist-upgrade
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-0ubuntu4
ProcVersionSign
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
W [24/Aug/
W [24/Aug/
W [24/Aug/
W [24/Aug/
W [24/Aug/
Date: Wed Aug 24 11:25:06 2011
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-Photosmart-
MachineType: ASUSTeK Computer Inc. G73Sw
PackageArchitec
Papersize: a4
PpdFiles: HP-Photosmart-
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
PATH=(custom, no user)
LANG=da_DK.UTF-8
SHELL=/bin/bash
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()
UdevDb: Error: [Errno 2] Ingen sådan fil eller filkatalog
UpgradeStatus: Upgraded to oneiric on 2011-07-15 (39 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
dmi.bios.date: 02/10/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G73Sw.205
dmi.board.
dmi.board.name: G73Sw
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: G73Sw
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
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.