dbus stop cause crash in printer-applet.py SIGSEGV in QSocketNotifier::setEnabled() KDE bug #171572

Bug #419847 reported by jth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: printer-applet

Source kdeutils

From bugs.kde.org #171572
------- Comment #1 From Jonathan Riddell 2008-10-06 21:31:02 -------
I can confirm this but it's probably a pykde bug.

Should we assign it to python-qt4?

ProblemType: Crash
Architecture: amd64
Date: Thu Aug 27 12:23:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InterpreterPath: /usr/bin/python2.6
Package: printer-applet 4:4.3.0-0ubuntu2
ProcCmdline: python /usr/bin/printer-applet
ProcEnviron:
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0x7f98d2376425 <_ZN15QSocketNotifier10setEnabledEb+21>: mov 0x30(%rdx),%rdx
 PC (0x7f98d2376425) ok
 source "0x30(%rdx)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdeutils
StacktraceTop:
 QSocketNotifier::setEnabled (this=0x1e08e50, enable=true)
 pyqtDBusHelper::readSocket (this=0x1f851e0, fd=10)
 pyqtDBusHelper::qt_metacall (this=0x1f851e0,
 QMetaObject::activate (sender=0x1e08e50,
 QSocketNotifier::activated (this=0x1e08e50, _t1=10)
Title: printer-applet.py crashed with SIGSEGV in QSocketNotifier::setEnabled()
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: games

Revision history for this message
jth (jth) wrote :
jth (jth)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QSocketNotifier::setEnabled ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdeutils (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

kdelibs5-data: installed version 4:4.3.0-0ubuntu6, latest version: 4:4.3.0-0ubuntu7
libgl1-mesa-glx: installed version 7.6.0~git20090825.87f83e19-0ubuntu0tormod, latest version: 7.6.0~git20090817.7c422387-0ubuntu3
libglu1-mesa: installed version 7.6.0~git20090825.87f83e19-0ubuntu0tormod, latest version: 7.6.0~git20090817.7c422387-0ubuntu3
kdelibs5: installed version 4:4.3.0-0ubuntu6, latest version: 4:4.3.0-0ubuntu7
libdrm2: installed version 2.4.12+git20090825.ce6c68dc-0ubuntu0tormod, latest version: 2.4.12+git20090801.45078630-0ubuntu1
kdelibs-bin: installed version 4:4.3.0-0ubuntu6, latest version: 4:4.3.0-0ubuntu7
libplasma3: installed version 4:4.3.0-0ubuntu6, latest version: 4:4.3.0-0ubuntu7

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.