systray.py crashed with SIGSEGV in g_type_module_use()

Bug #862759 reported by Michele Olivo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was updating the system.

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 i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CurrentDmesg:
 [ 918.394652] show_signal_msg: 3 callbacks suppressed
 [ 918.394663] python[1474]: segfault at 8 ip 080dce34 sp bf99e300 error 4 in python2.7[8048000+223000]
Date: Thu Sep 29 22:35:44 2011
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Deskjet_F4500: hp:/net/Deskjet_F4500_series?zc=HP363DB8
MachineType: eMachines eM355
PackageArchitecture: all
Papersize: a4
PpdFiles: Deskjet_F4500: HP Deskjet f4500 Series, hpcups 3.11.7
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=17c0eeed-b6e8-409d-9adb-adae833bddc6 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x80dce34: mov 0x8(%eax),%eax
 PC (0x080dce34) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 g_type_module_use () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 gtk_theme_engine_get () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: systray.py crashed with SIGSEGV in g_type_module_use()
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 02/15/2011
dmi.bios.vendor: eMachines
dmi.bios.version: V3.15(DDR3)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HM02_PT
dmi.board.vendor: eMachines
dmi.board.version: V3.15(DDR3)
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: V3.15(DDR3)
dmi.modalias: dmi:bvneMachines:bvrV3.15(DDR3):bd02/15/2011:svneMachines:pneM355:pvrV3.15(DDR3):rvneMachines:rnHM02_PT:rvrV3.15(DDR3):cvneMachines:ct10:cvrV3.15(DDR3):
dmi.product.name: eM355
dmi.product.version: V3.15(DDR3)
dmi.sys.vendor: eMachines

Revision history for this message
Michele Olivo (micheleolivo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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='Impossibile trovare il motore del tema in module_path: \xc2\xabpixmap\xc2\xbb,', category=<type at remote 0x8a4506c>, stack_level=1) at ../Python/_warnings.c:594
 PyErr_WarnEx (category=<type at remote 0x8a4506c>, text=0x8a8d850 "Impossibile trovare il motore del tema in module_path: \302\253pixmap\302\273,", stack_level=1) at ../Python/_warnings.c:720
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in hplip (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in hplip (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

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.

visibility: private → public
Revision history for this message
Robert Roth (evfool) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.