systray.py crashed with SIGSEGV in setup_context()

[Pedro Nariyoshi]

I went to settings, when I clicked "ok", the applet hung for a couple of seconds then crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: hplip-data 3.12.6-3ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Wed Sep 5 22:04:07 2012
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
Lpstat:
 p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
 device for Photosmart-C4600-series: hp:/usb/Photosmart_C4600_series?serial=CN978MG0DT05BQ
MachineType: Apple Inc. MacBookPro8,1
PackageArchitecture: all
Papersize: letter
PpdFiles: Photosmart-C4600-series: HP Photosmart c4600 Series, hpcups 3.12.6
ProcCmdline: /usr/bin/python /usr/share/hplip/systray.py --force-startup
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=763c5bc8-6479-4726-b801-ef603ad83e22 ro quiet i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=7 drm.vblankoffdelay=1 usbcore.autosuspend=1 hpet=force
SegvAnalysis:
 Segfault happened at: 0x54ba0b: mov 0x10(%rax),%rax
 PC (0x0054ba0b) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
 gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so
 ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction()
UpgradeStatus: Upgraded to quantal on 2012-07-12 (55 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video
dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B27.1201241646
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245B3640C91C81
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245B3640C91C81
dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
dmi.product.name: MacBookPro8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[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.29446 (message=message@entry="IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed", category=category@entry=<type at remote 0x27de0f0>, stack_level=stack_level@entry=1) at ../Python/_warnings.c:594
 PyErr_WarnEx (category=<type at remote 0x27de0f0>, text=<optimized out>, stack_level=1) at ../Python/_warnings.c:720
 _log_func (log_domain=<optimized out>, log_level=G_LOG_LEVEL_CRITICAL, message=0x2d74580 "IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed", user_data=0x27de0f0) at /build/buildd/pygobject-2-2.28.6/gobject/gobjectmodule.c:2353
 ?? ()

[Till Kamppeter (till-kamppeter)]

Can someone of the HPLIP developers at HP have a look into this? Thanks.

[Launchpad Janitor (janitor)]

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

[Roger James (rogerjames99)]

This bug is still affecting me in 14.04.

Have looked at this further using gdb. It seems that there is a generic problem in do_warn when called from systray.py. A number of other bugs have reported this with different warning messages cuasing the crash. So anything that causes a warning message wlll cause a crash. In my case the message is related to pango. When I first saw this bug on a previous distribution it was caused by a different warning message.