crashed with SIGSEGV in g_type_module_use()

Bug #632066 reported by las on 2010-09-07
This bug affects 17 people
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
qt4-x11 (Ubuntu)

Bug Description

Binary package hint: hplip

apport reported

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: hplip-data 3.10.6-1ubuntu5 [modified: usr/share/hplip/base/__init__.pyc usr/share/hplip/base/codes.pyc usr/share/hplip/base/g.pyc usr/share/hplip/base/logger.pyc]
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
 E [06/Sep/2010:17:33:06 +0530] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
 E [06/Sep/2010:17:33:34 +0530] [cups-driverd] Bad driver information file "/usr/share/cups/drv/sample.drv"!
Date: Sun Sep 5 18:11:23 2010
ExecutablePath: /usr/share/hplip/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100215)
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Deskjet_D1500: hp:/usb/Deskjet_D1500_series?serial=TH96O5D3SF058V
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Kobian KN6100M
PackageArchitecture: all
Papersize: a4
PpdFiles: Deskjet_D1500: HP Deskjet d1500 Series hpijs, 3.10.6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=32eb576a-bffd-44df-90ce-526c0652eb1c ro spUser Nameh quiet spUser Nameh
ProcCmdline: python /usr/bin/hp-systray
 Segfault happened at: 0x80d1c48: mov 0x8(%edx),%edx
 PC (0x080d1c48) ok
 source "0x8(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
 ?? () from /usr/lib/
 g_type_module_use () from /usr/lib/
 gtk_theme_engine_get () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
Title: crashed with SIGSEGV in g_type_module_use()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access sambashare tape vboxusers video 06/01/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG KN6100M
dmi.board.vendor: Kobian
dmi.chassis.type: 3
dmi.chassis.vendor: Kobian
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/01/2007:svnKobian:pnKN6100M:pvr:rvnKobian:rnKN6100M:rvr:cvnKobian:ct3:cvr: KN6100M
dmi.sys.vendor: Kobian

las (bandara-ls) wrote :

 gtk_theme_engine_load (module=0xa391b20)
 g_type_module_use () from /usr/lib/
 IA__gtk_theme_engine_get (name=0xa44aa68 "0�D\n")
 gtk_rc_parse_engine (context=0xa449898, scanner=0xa5c3fa0,
 gtk_rc_parse_style (context=<value optimized out>,

Changed in hplip (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in hplip (Ubuntu):
status: New → Confirmed
visibility: private → public

Still present in Oneiric Beta 1.

Just happened again in Oneiric Beta 2 while browsing wallpapers in System Settings, causing my HPLIP tray icon to disappear. I'd say this is probably the most common crash I'm seeing on my system now. hplip version 3.11.7-1ubuntu3.

Till Kamppeter (till-kamppeter) wrote :

Can you please do all updates (on the command line "sudo apt-get update; sudo apt-get dist-upgrade" or with Update Manager), log out and log in again, and then check again? Several bugs got fixed to solve this problem.

Changed in hplip (Ubuntu):
status: Confirmed → Incomplete

I have just rerun Update Manager to get all the latest updates and logged out/in, as you requested. But these crashes are difficult to reproduce and seem to happen completely at random. As such, I have not had a crash just yet, but I will come back once I see one.

...sorry, but I just had this crash happen again this morning while changing my status in Empathy. This bug is still alive and well.

Forgot to note that during the weekend I've been keeping my system fully up to date and had it rebooted a couple of times.

A possible cause is bug 805303, which should be fixed.

Can you run the following commands in a terminal window:

pkill -f hp-systray

Does hp-systray stay stable now?

Does your desktop stay stable when you are running vlc?

Can also be another problem in qt4-x11, adding qt4-x11 package ...

Changed in qt4-x11 (Ubuntu):
status: New → Incomplete

I've been running hp-systray from a terminal since the last crash to try and catch any error messages (couldn't get it to run from gdb), but it did not crash since then. I've just killed that and now I'm running it using the commands you provided far everything seems okay, but I cannot say for sure since I still have no idea how to reliably reproduce this crash.

As for vlc, I don't have that installed, and being in the US I am hesitant to install these types of things due to potential software patent issues with the codecs.

I'm now testing Precise and getting this problem every now and then, seemingly at random. The annoying part about this bug is that I have no idea how to reproduce it, though I'm currently suspecting changing the theme could be part of the problem.

At the moment I'm currently affected by bug 908805 on Precise, where for me Nautilus crashes just about every single time I start it up, which temporarily reverts the theme back to standard GNOME and seems to reliably reproduce this hplip crash.

After I reboot my system, I'll try the above commands again and try to capture the terminal output.

Yep, I can reliably reproduce this and just got another crash. For me, all I have to do is run the commands as given in comment 11 (or not, since it occurs during "normal" usage as well), open Nautilus, and wait or go into the Ubuntu One folder. Nautilus then crashes a few seconds later thanks to bug 908805, and that in turn causes this bug to occur. I strongly suspect it has something to do with the hplip-systray indicator being somehow unable to cope with theme changes.

Attached is my terminal output.

Precise Beta 1 and I'm still affected by this, typically whenever I change the theme.

I actually got some help on how to run hp-systray from gdb, and got a backtrace (triggered the crash simply by switching from Ambiance to Radiance in Appearance).

Let me know if this helps any, and if there's anything else I can do.

tags: added: precise
Roger James (rogerjames99) wrote :

Just upgraded to 13.10 and am getting this on every login. It was working fine on 13.04.

Can someone at HP have a look? Seems to be a problem with Ubuntu 13.10 which was released yesterday.

Roger James (rogerjames99) wrote :
Download full text (13.0 KiB)

Still happening at 14.04. Managed to do apport-retrace and run gdb. This is what the stack trace looks like now. It may be another bug is hiding the first one.

 info "(gdb)Auto-loading safe path"
warning: core file may not match specified executable file.
[New LWP 6922]
[New LWP 7063]
[New LWP 7064]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/".
Traceback (most recent call last):
  File "/tmp/apport_sandbox_XIhMcU/usr/lib/debug/usr/lib/i386-linux-gnu/", line 63, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
Core was generated by `/usr/bin/python /usr/bin/hp-systray -x'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 setup_context (registry=<synthetic pointer>, module=<synthetic pointer>,
    lineno=<synthetic pointer>, filename=<synthetic pointer>, stack_level=1,
    stack_level@entry=16) at ../Python/_warnings.c:449
449 ../Python/_warnings.c: No such file or directory.
(gdb) bt
#0 setup_context (registry=<synthetic pointer>, module=<synthetic pointer>,
    lineno=<synthetic pointer>, filename=<synthetic pointer>, stack_level=1,
    stack_level@entry=16) at ../Python/_warnings.c:449
#1 do_warn.29441 (message=message@entry=0xb6a40020,
    category=category@entry=0xb3b5f78c, stack_level=stack_level@entry=1)
    at ../Python/_warnings.c:594
#2 0x081f34cf in PyErr_WarnEx (category=category@entry=0xb3b5f78c,
    text=text@entry=0x97516e0 "/usr/lib/i386-linux-gnu/pango/1.8.0/modules/ cannot open shared object file: No such file or directory",
    stack_level=stack_level@entry=1) at ../Python/_warnings.c:720
#3 0xb4612aec in _log_func (log_domain=log_domain@entry=0xb3d35a56 "Pango",
    message=message@entry=0x97516e0 "/usr/lib/i386-linux-gnu/pango/1.8.0/modules/ cannot open shared object file: No such file or directory", user_data=user_data@entry=0xb3b5f78c)
    at /build/buildd/pygobject-2-2.28.6/gobject/gobjectmodule.c:2316
#4 0xb5f6f2f7 in g_logv (log_domain=log_domain@entry=0xb3d35a56 "Pango",
    format=format@entry=0xb3d40925 "%s",
    args=args@entry=0xbff769ec "\300\027u\t")
    at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1012
#5 0xb5f6f523 in g_log (log_domain=log_domain@entry=0xb3d35a56 "Pango",
---Type <return> to continue, or q <return> to quit---
    format=format@entry=0xb3d40925 "%s")
    at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1071
#6 0xb3d1b7d6 in pango_module_load (module=0x9747ce0)
    at /build/buildd/pango1.0-1.36.3/./pango/modules.c:225
#7 0xb4b1bdfe in g_type_module_use (module=0x9747ce0)
    at /build/buildd/glib2.0-2.40.0/./gobject/gtypemodule.c:244
#8 0xb3d1b89b in pango_engine_pair_get_engine (pair=0x973da60)
    at /build/buildd/pango1.0-1.36.3/./pango/modules.c:321
#9 0xb3d1b967 in append_engines (engine_list=engine_list@entry=0xbff7704c,
    pair_list=<optimised out>)
    at /build/buildd/pango1.0-1....

tags: added: utopic
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers