Bug 294562 - System settings crashes after exiting from multimedia with unsaved changes
Summary: System settings crashes after exiting from multimedia with unsaved changes
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
Depends on:
Blocks:
 
Reported: 2012-02-21 13:51 UTC by nakki
Modified: 2018-10-27 04:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description nakki 2012-02-21 13:51:29 UTC 
Application: systemsettings (1.0)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
I was surfing on the system settings, I watched multimedia settings, then when i exited I don't saved settings and it crashed.

-- Backtrace:
Application: Impostazioni di sistema (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0x7facb4e8e780 (LWP 11994))]

Thread 4 (Thread 0x7fac9f48a700 (LWP 11995)):
#0  0x00007facb00e4034 in __pthread_mutex_lock (mutex=0x204f9e8) at pthread_mutex_lock.c:61
#1  0x00007facafc0f023 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007facafc0fdfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007facafc10429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007facb2abdf3e in QEventDispatcherGlib::processEvents (this=0x204e380, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007facb2a91cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007facb2a91ef7 in QEventLoop::exec (this=0x7fac9f489dd0, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007facb29a927f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#8  0x00007facb2a74cbf in QInotifyFileSystemWatcherEngine::run (this=0x20570a0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007facb29abd05 in QThreadPrivate::start (arg=0x20570a0) at thread/qthread_unix.cpp:331
#10 0x00007facb00e1efc in start_thread (arg=0x7fac9f48a700) at pthread_create.c:304
#11 0x00007facb236189d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fac8cc60700 (LWP 12649)):
#0  0x00007facb00e4040 in __pthread_mutex_lock (mutex=0x4b6af78) at pthread_mutex_lock.c:62
#1  0x00007facafc0f361 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007facafc0fe6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007facafc10792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fac7fc4a516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007facafc352b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007facb00e1efc in start_thread (arg=0x7fac8cc60700) at pthread_create.c:304
#7  0x00007facb236189d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fac8d461700 (LWP 12650)):
#0  0x00007facb00e4034 in __pthread_mutex_lock (mutex=0x35503e8) at pthread_mutex_lock.c:61
#1  0x00007facafc0f75f in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007facafc0ff82 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007facafc10429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007facb2abdf3e in QEventDispatcherGlib::processEvents (this=0x21dc1f0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007facb2a91cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007facb2a91ef7 in QEventLoop::exec (this=0x7fac8d460dd0, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007facb29a927f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#8  0x00007facb2a74cbf in QInotifyFileSystemWatcherEngine::run (this=0x4afe870) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007facb29abd05 in QThreadPrivate::start (arg=0x4afe870) at thread/qthread_unix.cpp:331
#10 0x00007facb00e1efc in start_thread (arg=0x7fac8d461700) at pthread_create.c:304
#11 0x00007facb236189d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7facb4e8e780 (LWP 11994)):
[KCrash Handler]
#6  0x00007fac9cd760f5 in QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*) () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#7  0x00007facb29c7637 in QHashData::detach_helper2 (this=0x26c3af0, node_duplicate=0x7fac9cd760f0 <QHash<void*, PyQtProxy*>::duplicateNode(QHashData::Node*, void*)>, node_delete=0x7fac9cd760e0 <QHash<void*, PyQtProxy*>::deleteNode2(QHashData::Node*)>, nodeSize=<optimized out>, nodeAlign=8) at tools/qhash.cpp:235
#8  0x00007fac9cd7aca7 in sipQtFindSipslot () from /usr/lib/python2.7/dist-packages/PyQt4/QtCore.so
#9  0x00007fac9d04171e in sipWrapper_traverse (arg=0x0, visit=0x7fac9e45e620 <visit_decref>, self=0x2784c20) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9648
#10 sipWrapper_traverse (self=0x2784c20, visit=0x7fac9e45e620 <visit_decref>, arg=0x0) at /build/buildd/sip4-4.12.4/siplib/siplib.c:9629
#11 0x00007fac9e45e8c7 in subtract_refs (containers=0x7fac9e7dec80) at ../Modules/gcmodule.c:345
#12 collect (generation=2) at ../Modules/gcmodule.c:874
#13 0x00007fac9e45f5e4 in PyGC_Collect () at ../Modules/gcmodule.c:1386
#14 0x00007fac9e44baa6 in Py_Finalize () at ../Python/pythonrun.c:437
#15 Py_Finalize () at ../Python/pythonrun.c:393
#16 0x00007fac9e84a9e5 in KPythonPluginFactory::~KPythonPluginFactory (this=0x245db10, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:262
#17 0x00007fac9e84aa49 in KPythonPluginFactory::~KPythonPluginFactory (this=0x245db10, __in_chrg=<optimized out>) at ../../kpythonpluginfactory/kpythonpluginfactory.cpp:268
#18 0x00007facb2aab926 in QObjectCleanupHandler::clear (this=0x1df2f80) at kernel/qobjectcleanuphandler.cpp:140
#19 0x00007facb2aab96b in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x1df2f80, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:86
#20 0x00007facb2aab9b9 in QObjectCleanupHandler::~QObjectCleanupHandler (this=0x1df2f80, __in_chrg=<optimized out>) at kernel/qobjectcleanuphandler.cpp:87
#21 0x00007facb22bb821 in __run_exit_handlers (status=1, listp=0x7facb26185a8, run_list_atexit=true) at exit.c:78
#22 0x00007facb22bb8a5 in __GI_exit (status=<optimized out>) at exit.c:100
#23 0x00007fac77057b9e in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#24 0x00007facb16b606f in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#25 0x00007facb16b2e21 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#26 0x00007facb16b3d77 in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#27 0x00007facb169834b in XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#28 0x00007facb45640db in NETWinInfo::update (this=0x7fff83a365c0, dirty_props=<optimized out>) at ../../kdeui/windowmanagement/netwm.cpp:3962
#29 0x00007facb45658a6 in NETWinInfo::event (this=0x7fff83a365c0, event=0x7fff83a36670, properties=0x7fff83a36590, properties_size=2) at ../../kdeui/windowmanagement/netwm.cpp:3925
#30 0x00007facb455a988 in KWindowSystemPrivate::x11Event (this=0x223d510, ev=0x7fff83a36670) at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:198
#31 0x00007facb444a3e6 in publicX11Event (e=0x7fff83a36670, this=<optimized out>) at ../../kdeui/kernel/ksystemeventfilter.cpp:43
#32 KSystemEventFilterPrivate::filterEvent (this=0x4375860, message=0x7fff83a36670) at ../../kdeui/kernel/ksystemeventfilter.cpp:102
#33 0x00007facb37b4418 in x11EventSourceDispatch (s=0x1a5a600, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143
#34 0x00007facafc0fa5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007facafc10258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007facafc10429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007facb2abded6 in QEventDispatcherGlib::processEvents (this=0x1a30a10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#38 0x00007facb37b410e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#39 0x00007facb2a91cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#40 0x00007facb2a91ef7 in QEventLoop::exec (this=0x7fff83a36a40, flags=...) at kernel/qeventloop.cpp:201
#41 0x00007facb2a96789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#42 0x000000000040a7c5 in main (argc=5, argv=0x7fff83a36d78) at ../../../systemsettings/app/main.cpp:49

Possible duplicates by query: bug 293413, bug 292729, bug 292290, bug 292205, bug 291668.

Reported using DrKonqi
Comment 1 Christoph Feck 2012-02-21 15:50:56 UTC 
Did you visit the printer settings page? Are there any other System Settings
modules installed that use the Python language?
Comment 2 nakki 2012-02-22 10:52:49 UTC 
(In reply to comment #1)
> Did you visit the printer settings page? 
I think yes, but I'm not sure...I was watching many settings in that moment...

> Are there any other System Settings modules installed that use the Python language?

I don't know...Can you explain the question, please?
Comment 3 Christoph Feck 2012-02-22 12:59:52 UTC 
The problem with the backtrace from comment #0 is that it does not reveal which System Settings module (Printer settings, Language settings etc.) is responsible for the crash, since the backtrace only shows a crash in the Python interpreter.

To find out which modules are using the Python interpreter, you would have to check your installation, as KDE itself only supplies the Printer module implemented in Python. Many other third-party (synaptiks, grub manager, etc.) or distribution specific (language installation, user management, etc.) modules are also written in Python.

Since we are getting many duplicates of this crash, it would be nice to have a list of possible offenders. It could also be a bug in the Python interpreter or bindings, but that is impossible to tell from the backtrace.
Comment 4 nakki 2012-02-22 18:45:53 UTC 
How do I know if I have other python modules in addition to that printer?
Comment 5 Andrew Crouthamel 2018-09-22 01:47:25 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 6 Andrew Crouthamel 2018-10-27 04:19:51 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!