Bug 196800 - launched EnvyNG: crash in closure
Summary: launched EnvyNG: crash in closure
Status: RESOLVED WORKSFORME
Alias: None
Product: bindings
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords: triaged
: 202132 204367 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-16 20:54 UTC by perilibri
Modified: 2018-10-27 02:32 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description perilibri 2009-06-16 20:54:41 UTC
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
Comment 1 Dario Andres 2009-06-16 21:20:01 UTC
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
Comment 2 Yuriy Kozlov 2009-09-13 19:03:36 UTC
*** Bug 204367 has been marked as a duplicate of this bug. ***
Comment 3 Yuriy Kozlov 2009-09-13 19:04:35 UTC
*** Bug 202132 has been marked as a duplicate of this bug. ***
Comment 4 Yuriy Kozlov 2009-09-13 19:08:31 UTC
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
Comment 5 Christoph Feck 2013-09-12 21:46:00 UTC
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)
Comment 6 Andrew Crouthamel 2018-09-24 02:20:20 UTC
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!
Comment 7 Andrew Crouthamel 2018-10-27 02:32:39 UTC
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!