printer-applet.py crashed with SIGSEGV in PyEval_EvalFrameEx()

Bug #274371 reported by ledzep974
6
Affects Status Importance Assigned to Milestone
sip4-qt3 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdeutils

NOTHING MORE

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
InterpreterPath: /usr/bin/python2.5
Package: kde-printer-applet 4:4.1.1-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/bin/printer-applet
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdeutils
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/python2.5/site-packages/sip.so
 ?? ()
 PyEval_EvalFrameEx ()
Title: printer-applet.py crashed with SIGSEGV in PyEval_EvalFrameEx()
Uname: Linux 2.6.27-4-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
ledzep974 (ledzep974) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:release_QString (sipCppV=0x27e0c20) at sipQtCorepart2.cpp:7813
sipWrapper_dealloc (self=0x2362848) at /build/buildd/sip4-qt3-4.7.7/siplib/siplib.c:7478
subtype_dealloc (self=0x2362848) at ../Objects/typeobject.c:709
PyEval_EvalFrameEx (f=0x2762410, throwflag=<value optimized out>) at ../Python/ceval.c:967
PyEval_EvalFrameEx (f=0x26ac900, throwflag=<value optimized out>) at ../Python/ceval.c:3681

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdeutils:
importance: Undecided → Medium
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still an issue in more recent versions of Kubuntu?

affects: python-qt4 (Ubuntu) → sip4-qt3 (Ubuntu)
Changed in sip4-qt3 (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in sip4-qt3 (Ubuntu):
status: Incomplete → Invalid
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.