Bug 284408 - crash after closing system settings since upgrading to 11.10
Summary: crash after closing system settings since upgrading to 11.10
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: System Settings Bugs
URL:
Keywords: investigated, triaged
: 284991 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-18 21:01 UTC by michael
Modified: 2018-10-27 03:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.25 KB, text/plain)
2011-10-28 12:38 UTC, Martin Pagh Goodwin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description michael 2011-10-18 21:01:01 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

Crashes whenever I close or exit out of system settings after upgrading to 11.10

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7837930 (LWP 2271))]

Thread 2 (Thread 0xb53efb70 (LWP 2272)):
#0  0x008f1d54 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x00392f54 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#2  0x04e357e1 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x04e36637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x04e36c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x028afb37 in QEventDispatcherGlib::processEvents (this=0x8f3a2a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x028801dd in QEventLoop::processEvents (this=0xb53ef2b0, flags=...) at kernel/qeventloop.cpp:149
#7  0x02880421 in QEventLoop::exec (this=0xb53ef2b0, flags=...) at kernel/qeventloop.cpp:201
#8  0x0278390b in QThread::exec (this=0x8f4f870) at thread/qthread.cpp:498
#9  0x02860e2d in QInotifyFileSystemWatcherEngine::run (this=0x8f4f870) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x027867b3 in QThreadPrivate::start (arg=0x8f4f870) at thread/qthread_unix.cpp:331
#11 0x008eed31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x003850ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb7837930 (LWP 2271)):
[KCrash Handler]
#7  0x041ff30c in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#8  0x027a4c99 in QHashData::detach_helper2 (this=0x93542e0, node_duplicate=0x41ff300 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x41ff2f0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=16, nodeAlign=4) at tools/qhash.cpp:235
#9  0x0420430c in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#10 0x04cddc00 in sipWrapper_traverse (arg=0x0, visit=0x33c1720 <visit_decref>, self=0xb481e77c) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648
#11 sipWrapper_traverse (self=0xb481e77c, visit=0x33c1720 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
#12 0x0333d252 in subtype_traverse (self=<QApplication at remote 0xb481e77c>, visit=0x33c1720 <visit_decref>, arg=0x0) at ../Objects/typeobject.c:838
#13 0x033c1990 in subtract_refs (containers=0x3538728) at ../Modules/gcmodule.c:345
#14 collect (generation=2) at ../Modules/gcmodule.c:874
#15 0x033c26bc in PyGC_Collect () at ../Modules/gcmodule.c:1386
#16 0x033adadb in Py_Finalize () at ../Python/pythonrun.c:437
#17 Py_Finalize () at ../Python/pythonrun.c:393
#18 0x021d2f75 in KPythonPluginFactory::~KPythonPluginFactory (this=0x91ff1d8, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:262
#19 0x021d3002 in KPythonPluginFactory::~KPythonPluginFactory (this=0x91ff1d8, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:268
#20 0x0289bb45 in QObjectCleanupHandler::clear (this=0x8f6ee40) at kernel/qobjectcleanuphandler.cpp:140
#21 0x0289bb8d in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x8f6ee40, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:86
#22 0x0289bc02 in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x8f6ee40, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:87
#23 0x00682512 in destroy () at ../../kdecore/util/kpluginfactory.cpp:29
#24 0x004f6339 in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0x7330f0, __in_chrg=<optimized out>) at ../../kdecore/kernel/kglobal.h:62
#25 0x002e5981 in ?? () from /lib/i386-linux-gnu/libc.so.6
#26 0x002e5a0d in exit () from /lib/i386-linux-gnu/libc.so.6
#27 0x02e89d90 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#28 0x0892ad6b in _XError () from /usr/lib/i386-linux-gnu/libX11.so.6
#29 0x0892793d in ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
#30 0x08928927 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#31 0x0890d2b8 in XGetWindowProperty () from /usr/lib/i386-linux-gnu/libX11.so.6
#32 0x00c6d730 in NETWinInfo::update (this=0xbfd5b3e8, dirty_props=0xbfd5b368) at ../../kdeui/windowmanagement/netwm.cpp:3962
#33 0x00c6efd6 in NETWinInfo::event (this=0xbfd5b3e8, event=0xbfd5b4cc, properties=0xbfd5b3d4, properties_size=2) at ../../kdeui/windowmanagement/netwm.cpp:3925
#34 0x00c632d0 in KWindowSystemPrivate::x11Event (this=0x922e828, ev=0xbfd5b4cc) at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:198
#35 0x00b2b0fb in publicX11Event (e=0xbfd5b4cc, this=<optimized out>) at ../../kdeui/kernel/ksystemeventfilter.cpp:43
#36 KSystemEventFilterPrivate::filterEvent (this=0x922ea90, message=0xbfd5b4cc) at ../../kdeui/kernel/ksystemeventfilter.cpp:102
#37 0x00b2b196 in _k_eventFilter (message=0xbfd5b4cc) at ../../kdeui/kernel/ksystemeventfilter.cpp:91
#38 0x028737cc in QAbstractEventDispatcher::filterEvent (this=0x8cb7bb0, message=0xbfd5b4cc) at kernel/qabstracteventdispatcher.cpp:501
#39 0x01071181 in x11EventSourceDispatch (s=0x8cd9468, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143
#40 0x04e3625f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 0x04e36990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#42 0x04e36c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#43 0x028afada in QEventDispatcherGlib::processEvents (this=0x8cb7bb0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#44 0x01070e3a in QGuiEventDispatcherGlib::processEvents (this=0x8cb7bb0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#45 0x028801dd in QEventLoop::processEvents (this=0xbfd5b7d4, flags=...) at kernel/qeventloop.cpp:149
#46 0x02880421 in QEventLoop::exec (this=0xbfd5b7d4, flags=...) at kernel/qeventloop.cpp:201
#47 0x0288519d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#48 0x00fb68f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#49 0x080502b8 in main (argc=0, argv=0x19) at ../../../systemsettings/app/main.cpp:49

Possible duplicates by query: bug 284385, bug 284378, bug 284333, bug 284298, bug 284265.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-10-18 22:15:59 UTC
Did you visit the printer settings page? Are there any other System Settings modules installed that use the Python language?
Comment 2 Christoph Feck 2011-10-25 09:24:53 UTC
If you can provide the information requested in comment #1, please add it.

If the crash is caused by visiting the printer settings page, it would be a duplicate of bug 283611.
Comment 3 Christoph Feck 2011-10-26 20:21:02 UTC
*** Bug 284991 has been marked as a duplicate of this bug. ***
Comment 4 Martin Pagh Goodwin 2011-10-28 12:38:02 UTC
Created attachment 64976 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:
I had just asked the printer to print a test page. 
I previously had crashes when deleting a printer and when adding a printer.

-- Backtrace (Reduced):
#6  0x00007f9e4cdce0f5 in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7  0x00007f9e6206c637 in QHashData::detach_helper2 (this=0x205f050, node_duplicate=0x7f9e4cdce0f0 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7f9e4cdce0e0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=<optimized out>, nodeAlign=8) at tools/qhash.cpp:235
#8  0x00007f9e4cdd2ca7 in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9  0x00007f9e4ca4571e in sipWrapper_traverse (arg=0x0, visit=0x7f9e4dc8b620 <visit_decref>, self=0x2167170) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648
#10 sipWrapper_traverse (self=0x2167170, visit=0x7f9e4dc8b620 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
Comment 5 michael 2011-10-28 17:45:38 UTC
I am not really sure anymore, but it is possible that I may have tried to add a new network printer to the system.  I had to get my system back up and running in working order so, I just went and did a complete new install of my dual boot system.  Did not want to get stuck with only windows.  The new install did not take very long since I do routine backups of certain folders.
Comment 6 Andrew Crouthamel 2018-09-22 02:06:10 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 03:58:18 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!