systray.py crashed with SIGSEGV in g_type_module_use()

[Jason]

Just opened System Settings>System Info and was presented with a crash notification

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-1ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Wed Sep 28 21:08:08 2011
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for HP-Photosmart-C4700-series: hp:/net/Photosmart_C4700_series?zc=HP540012
MachineType: Acer Aspire 5553
PackageArchitecture: all
Papersize: a4
PpdFiles: HP-Photosmart-C4700-series: HP Photosmart c4700 Series, hpcups 3.11.7
ProcCmdline: python /usr/bin/hp-systray
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=60f0c782-83dd-4c6f-a03b-2f53b2d68588 ro quiet 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()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/23/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.20
dmi.board.name: JV51_DN
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.20:bd12/23/2010:svnAcer:pnAspire5553:pvrNotApplicable:rvnAcer:rnJV51_DN:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5553
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

[Apport retracing service (apport)]

StacktraceTop:
 setup_context (registry=<synthetic pointer>, module=<synthetic pointer>, lineno=<synthetic pointer>, filename=<synthetic pointer>, stack_level=1) at ../Python/_warnings.c:449
 do_warn (message='Unable to locate theme engine in module_path: "pixmap",', category=<type at remote 0x29a4c20>, stack_level=1) at ../Python/_warnings.c:594
 PyErr_WarnEx (category=<type at remote 0x29a4c20>, text=<optimized out>, stack_level=1) at ../Python/_warnings.c:720
 _log_func (log_domain=<optimized out>, log_level=G_LOG_LEVEL_WARNING, message=0x2b53d60 "Unable to locate theme engine in module_path: \"pixmap\",", user_data=0x29a4c20) at /build/buildd/pygobject-2-2.28.6/gobject/gobjectmodule.c:2353
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robert Roth (evfool)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #861771, so it 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. Feel free to continue to report any other bugs you may find.

[Robert Roth (evfool)]

Sorry, commented on the wrong bug, meant to comment that for #869551.