systray.py crashed with SIGSEGV in QSystemTrayIcon::~QSystemTrayIcon()

Bug #564461 reported by HX_unbanned
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: hplip

Possible duplicate.

Reporting because versions do not match.

Happened on system startup.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: hplip-data 3.10.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
CheckboxSubmission: 40c56929f643c4d957cbd51429c47433
CheckboxSystem: 9a8dfd7f83677f101ab201cb214a9227
CrashCounter: 1
Date: Fri Apr 16 09:57:27 2010
Disassembly: => 0x19: Cannot access memory at address 0x19
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
Lpstat:
 device for Officejet-5600-series: usb://HP/Officejet%205600%20series?serial=CN72GDF25204B2
 device for Officejet_5600: hp:/usb/Officejet_5600_series?serial=CN72GDF25204B2
 device for Officejet_5600_fax: hpfax:/usb/Officejet_5600_series?serial=CN72GDF25204B2
MachineType: OEM OEM
PackageArchitecture: all
Papersize: letter
PpdFiles:
 Officejet_5600_fax: HP Fax hpijs
 Officejet-5600-series: HP Officejet 5600 Series hpijs, 3.10.2
 Officejet_5600: HP Officejet 5600 Series hpijs, 3.10.2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic-pae root=UUID=0c231c7e-1d96-4302-b35f-572ed6c07203 ro quiet splash
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=lv_LV.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x19: Cannot access memory at address 0x19
 PC (0x00000019) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libQtGui.so.4
 QSystemTrayIcon::~QSystemTrayIcon() ()
 ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
 QObjectCleanupHandler::clear() ()
Title: systray.py crashed with SIGSEGV in QSystemTrayIcon::~QSystemTrayIcon()
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
dmi.bios.date: 09/19/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: LP UT P35
dmi.board.vendor: DFI Inc.
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/19/2008:svnOEM:pnOEM:pvrOEM:rvnDFIInc.:rnLPUTP35:rvr1.0:cvnOEM:ct3:cvrOEM:
dmi.product.name: OEM
dmi.product.version: OEM
dmi.sys.vendor: OEM

Revision history for this message
HX_unbanned (linards-liepins) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ~QSystemTrayIcon (this=0x9405dd0)
 ?? ()
 QObjectCleanupHandler::clear (this=0x9405dd0)
 ~QObjectCleanupHandler (this=0x9403820)

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
Changed in hplip (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul Broadhead (pjbroad) 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 #557710, 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.