apport-kde crashed with SIGSEGV in QWidgetPrivate::deleteExtra()

Bug #403361 reported by Kernel-1
626
This bug affects 101 people
Affects Status Importance Assigned to Milestone
KDE Bindings
Invalid
High
Linux Mint
Triaged
Medium
Unassigned
python-qt4 (Ubuntu)
Triaged
High
Unassigned

Bug Description

Binary package hint: apport

apport-kde crashed with SIGSEGV in QWidgetPrivate::deleteExtra()

ProblemType: Crash
Architecture: amd64
Date: Thu Jul 23 09:09:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-kde
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.6-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x7fbeb2ca6580: mov 0x10(%rax),%rdi
 PC (0x7fbeb2ca6580) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 QWidgetPrivate::deleteExtra() ()
 QWidgetPrivate::~QWidgetPrivate() ()
 ?? () from /usr/lib/libQtGui.so.4
Title: apport-kde crashed with SIGSEGV in QWidgetPrivate::deleteExtra()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
In , Perilibri (perilibri) wrote :

Application that crashed:
Version of the application: 2.0
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
kubuntu 8.10 updated to 9.04.
Crash always closing EnvyNG

 -- Backtrace:
Application: EnvyNG (), signal: Segmentation fault
[KCrash Handler]
#5 0xb6592b82 in ~QX11WindowSurface (this=0xa007b08) at painting/qwindowsurface_x11.cpp:84
#6 0xb658bbb6 in ~QWidgetBackingStore (this=0xa003c28) at painting/qbackingstore.cpp:828
#7 0xb63bf066 in QWidgetPrivate::deleteExtra (this=0xa0099f0) at kernel/qwidget.cpp:1503
#8 0xb63bf845 in ~QWidgetPrivate (this=0xa0099f0) at kernel/qwidget.cpp:224
#9 0xb6874a79 in ~QDialogPrivate (this=0xa0099f0) at ../../include/QtGui/private/../../../src/gui/dialogs/qdialog_p.h:67
#10 0xb73e22e1 in ~QObject (this=0xa0096b0) at kernel/qobject.cpp:865
#11 0xb63c484f in ~QWidget (this=0xa0096b0) at kernel/qwidget.cpp:1386
#12 0xb688c776 in ~QDialog (this=0xa0096b0) at dialogs/qdialog.cpp:298
#13 0xb709acb5 in ?? () from /usr/lib/python2.6/dist-packages/PyQt4/QtGui.so
#14 0xb703ef8c in ?? () from /usr/lib/python2.6/dist-packages/PyQt4/QtGui.so
#15 0xb703efce in ?? () from /usr/lib/python2.6/dist-packages/PyQt4/QtGui.so
#16 0xb76775a3 in ?? () from /usr/lib/python2.6/dist-packages/sip.so
#17 0x080a90d5 in ?? ()
#18 0x0808cb61 in ?? ()
#19 0x0808ee69 in PyDict_SetItem ()
#20 0x080909c1 in _PyModule_Clear ()
#21 0x080f17a2 in PyImport_Cleanup ()
#22 0x080fd90d in Py_Finalize ()
#23 0x0805c129 in Py_Main ()
#24 0x0805b972 in main ()

Reported using DrKonqi

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

There was an error, EnvyNG is not supported in this bugtracker (the maintainer was contacted)
You need to report this crash to its maintainer: http://albertomilone.com/nvidia_scripts1.html

Thanks

Revision history for this message
Kernel-1 (oligofrenolog) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:~QX11WindowSurface (this=0x23fa9d0)
~QWidgetBackingStore (this=0x23e3eb0)
QWidgetPrivate::deleteExtra (this=0x23ca7d0)
~QWidgetPrivate (this=0x23ca7d0)
~QDialogPrivate (this=0x23ca7d0)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in apport (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Martin Pitt (pitti)
affects: apport (Ubuntu) → qt4-x11 (Ubuntu)
affects: qt4-x11 (Ubuntu) → python-qt4 (Ubuntu)
Revision history for this message
starslights (starslights) wrote :

hello,

i have this crash with excately same errors.

card nvidia 180.25 , kubuntu 2.6.31-9.29 , apport KDE 1.8.1

The rapport made by apport was not send. seem sometime fail

Revision history for this message
starslights (starslights) wrote :

hello,

i have this crash with excately same errors on kubuntu karmic alpha5

card nvidia 180.25 , kubuntu 2.6.31-9.29 , apport KDE 1.8.1

The rapport made by apport was not send. seem sometime fail

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :
Download full text (3.3 KiB)

A trace using gdb on karmic. Application (patched version of apport-kde) crashes on exit. The run and exit code:

    # Don't exec_() here. There is no main interface and the dialogs are
    # exec_()ed independently.
    ret = int(UserInterface.run_argv())
    print "run_argv returned"
    KApplication.exit(ret)
    print "kapplication.exit returned"
    sys.exit(ret)

The output and trace:
run_argv returned
kapplication.exit returned

Program received signal SIGSEGV, Segmentation fault.
0x052c1ce2 in ~QX11WindowSurface (this=0x8ad3e20, __in_chrg=<value optimized out>) at painting/qwindowsurface_x11.cpp:84
84 painting/qwindowsurface_x11.cpp: No such file or directory.
        in painting/qwindowsurface_x11.cpp
Current language: auto; currently c++
(gdb) backtrace
#0 0x052c1ce2 in ~QX11WindowSurface (this=0x8ad3e20, __in_chrg=<value optimized out>) at painting/qwindowsurface_x11.cpp:84
#1 0x052ba946 in ~QWidgetBackingStore (this=0x8ad3df0, __in_chrg=<value optimized out>) at painting/qbackingstore.cpp:829
#2 0x0511c944 in QWidgetPrivate::deleteExtra (this=0x8aadf30) at kernel/qwidget.cpp:1503
#3 0x0511d0e5 in ~QWidgetPrivate (this=0x8aadf30, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:227
#4 0x055a6189 in ~QDialogPrivate (this=0x8aadf30, __in_chrg=<value optimized out>) at ../../include/QtGui/private/../../../src/gui/dialogs/qdialog_p.h:67
#5 0x005de85a in ~QObject (this=0x8b825d8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:857
#6 0x0512294f in ~QWidget (this=0x8b825d8, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1380
#7 0x055bde44 in ~QDialog (this=0x8b825d8, __in_chrg=<value optimized out>) at dialogs/qdialog.cpp:298
#8 0x01278653 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
#9 0x012177a6 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
#10 0x012177e9 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtGui.so
#11 0x0038d588 in ?? () from /usr/lib/pymodules/python2.6/sip.so
#12 0x0038d5c1 in ?? () from /usr/lib/pymodules/python2.6/sip.so
#13 0x080a8e13 in subtype_dealloc (self=0x8baf4ac) at ../Objects/typeobject.c:1024
#14 0x0808e574 in dict_dealloc (mp=0x88464f4) at ../Objects/dictobject.c:911
#15 0x0806a3eb in instance_dealloc (inst=0x8cc1a8c) at ../Objects/classobject.c:668
#16 0x0808ce59 in insertdict (mp=0xb7fd61c4, key=0xb7ebb4a8, hash=-414803461, value=0x8245f58) at ../Objects/dictobject.c:459
#17 0x0808f2b7 in PyDict_SetItem (op=0xb7fd61c4, key=0xb7ebb4a8, value=0x8245f58) at ../Objects/dictobject.c:701
#18 0x08090c13 in _PyModule_Clear (m=0xb7fa411c) at ../Objects/moduleobject.c:138
#19 0x080ed7a5 in PyImport_Cleanup () at ../Python/import.c:444
#20 0x080fa0d5 in Py_Finalize () at ../Python/pythonrun.c:434
#21 0x080f9b7f in Py_Exit () at ../Python/pythonrun.c:1714
#22 handle_system_exit () at ../Python/pythonrun.c:1116
#23 0x080f9d6d in PyErr_PrintEx (set_sys_last_vars=1) at ../Python/pythonrun.c:1126
#24 0x080f9fa2 in PyErr_Print () at ../Python/pythonrun.c:1035
#25 0x080faacb in PyRun_SimpleFileExFlags (fp=0xbffffa8b, filename=0xbffffa8b "/usr/share/apport/apport-kde", closeit=1, flags=0xbffff80c) at ../Python/pythonrun.c:935
#26 0x0805c898 in Py_Main (argc...

Read more...

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Setting to high because this needs to be fixed to fix bug #405378.

Changed in python-qt4 (Ubuntu):
importance: Medium → High
status: New → Triaged
Revision history for this message
emorrp1 (emorrp1) wrote :

Thank you Yuriy for the confirmation

Changed in linuxmint:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
In , Yuriy Kozlov (yuriy-kozlov) wrote :

*** Bug 204367 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Yuriy Kozlov (yuriy-kozlov) wrote :

*** Bug 202132 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Yuriy Kozlov (yuriy-kozlov) wrote :

I think this may actually be a bug in Qt or PyQt. It has also come up here:
https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/403361
and possibly here:
https://bugs.launchpad.net/ubuntu/+source/kile/+bug/357016

Changed in kdebindings:
status: Unknown → New
Revision history for this message
Geoff123 (gsking1) wrote :

I've had this error upon the last 2 kde logins.
Upgraded to Karmic a few days ago.
Linux version 2.6.31-12-generic
nvidia drivers

Revision history for this message
MiXiM (mixim) wrote :

've had this error upon the last 2 kde logins.
Upgraded to Karmic a few days ago.
Linux version 2.6.31-12-generic
nvidia drivers

same to me

Changed in kdebindings:
importance: Unknown → High
Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)

Changed in kdebindings:
status: New → Incomplete
Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Revision history for this message
In , Andrew-crouthamel (andrew-crouthamel) wrote :

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

Changed in kdebindings:
status: Incomplete → Invalid
To post a comment you must log in.