systray.py crashed with SIGSEGV in QWidget::hide()

Bug #554531 reported by Kai Kasurinen
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: hplip

(on logout/login cycle)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: hplip-data 3.10.2-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Sat Apr 3 13:40:39 2010
ExecutablePath: /usr/share/hplip/systray.py
InterpreterPath: /usr/bin/python2.6
Lpstat: device for HP_Laserjet_5L: hp:/net/HP_LaserJet_5L?ip=10.10.16.79
MachineType: Hewlett-Packard HP Compaq 6910p
PackageArchitecture: all
Papersize: a4
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
PpdFiles: HP_Laserjet_5L: HP LaserJet 5L Foomatic/ljet4 (recommended)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=0836dd3e-309a-4cbc-8df9-916b9c8ed39a ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_GB:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: hplip
StacktraceTop:
 QWidget::hide (this=0x21f0890)
 QSystemTrayIconPrivate::remove_sys (this=0x21f0890)
 ~QSystemTrayIcon (this=0x21ebfe0,
 ?? ()
 QObjectCleanupHandler::clear (this=0x22768a0)
Title: systray.py crashed with SIGSEGV in QWidget::hide()
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev staff video
dmi.bios.date: 11/04/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MCU Ver. F.17
dmi.board.name: 30BE
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 68.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68MCUVer.F.17:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6910p:pvrF.17:rvnHewlett-Packard:rn30BE:rvrKBCVersion68.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6910p
dmi.product.version: F.17
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QSystemTrayIconSys::mousePressEvent (this=0x3,
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Changed in hplip (Ubuntu):
status: New → Incomplete
Revision history for this message
Rick (rickledford) wrote :

photosmart 6180 was powered off when I booted. This message was initiated after boot.

Revision history for this message
Rick (rickledford) wrote :

it crashed again.

Revision history for this message
Rick (rickledford) wrote :

I am reporting this one more time, it happens each time I boot.

Revision history for this message
Cesare Mastroianni (cece) wrote :

I'm experiencing this bug every day at every boot.

I tried to collect info for a complete backtrace, but I can't understand how to do this. I followed the instructions here:
https://wiki.ubuntu.com/Backtrace

Actually, after boot I need some times (up to 1 minute) to open a terminal, get the process pid, run gdb, set up gdb for the proper parameters and then attach the pid. During all this time, the process crash before I complete the task.

So it is really impossible to detect the crashing event using GDB.

Please, let me know how to help You in help us!

Ciao
Grazie.
CM

Changed in hplip (Ubuntu):
status: Incomplete → New
Revision history for this message
Cesare Mastroianni (cece) wrote :

After upgrading to maverick the problem vanished. I cannot add anything else.

Happy new year!

CM

Changed in hplip (Ubuntu):
status: New → Fix Released
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.