systray.py crashed with SIGSEGV in g_type_module_use()

[Karsten S. Opdal]

First login after dist-upgrade

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
 W [24/Aug/2011:10:18:41 +0200] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Photosmart_C7200_series_Gray__' has already been added
 W [24/Aug/2011:10:18:41 +0200] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Photosmart_C7200_series_RGB__' has already been added
 W [24/Aug/2011:11:21:57 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 W [24/Aug/2011:11:22:02 +0200] failed to CreateProfile: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 W [24/Aug/2011:11:22:07 +0200] failed to CreateDevice: org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Date: Wed Aug 24 11:25:06 2011
ExecutablePath: /usr/share/hplip/systray.py
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-Photosmart-C7200-series: hp:/net/Photosmart_C7200_series?zc=printer
MachineType: ASUSTeK Computer Inc. G73Sw
PackageArchitecture: all
Papersize: a4
PpdFiles: HP-Photosmart-C7200-series: HP Photosmart c7200 Series, hpcups 3.11.5
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
 PATH=(custom, no user)
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=127f47cf-355e-4fce-99f9-522ffcb0f00c ro quite splash vt.handoff=7
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/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_type_module_use () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gtk_theme_engine_get () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
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.asset.tag: ATN12345678901234567
dmi.board.name: G73Sw
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG73Sw.205:bd02/10/2011:svnASUSTeKComputerInc.:pnG73Sw:pvr1.0:rvnASUSTeKComputerInc.:rnG73Sw:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G73Sw
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Apport retracing service (apport)]

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.