Application: kded4 ($Id$) KDE Platform Version: 4.7.1 (4.7.1) Qt Version: 4.7.4 Operating System: Linux 3.0.0-12-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: I copied music to my android phone using dolphin and when I ejected the phone amarok crashed -- Backtrace: Application: KDE Daemon (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0x7f478d0e3780 (LWP 2722))] Thread 3 (Thread 0x7f477152f700 (LWP 2731)): #0 __libc_enable_asynccancel () at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:66 #1 0x00007f478a933758 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:85 #2 0x00007f4787b33f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f4787b34792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f477180c516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x00007f4787b592b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f47883fdefc in start_thread (arg=0x7f477152f700) at pthread_create.c:304 #7 0x00007f478a93f89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #8 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f4770b22700 (LWP 2732)): #0 0x00007f478a933773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f4787b33f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f4787b34429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f478bd7af3e in QEventDispatcherGlib::processEvents (this=0xda93e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #4 0x00007f478bd4ecf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f478bd4eef7 in QEventLoop::exec (this=0x7f4770b21dd0, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007f478bc6627f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #7 0x00007f478bd31cbf in QInotifyFileSystemWatcherEngine::run (this=0xda5d70) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f478bc68d05 in QThreadPrivate::start (arg=0xda5d70) at thread/qthread_unix.cpp:331 #9 0x00007f47883fdefc in start_thread (arg=0x7f4770b22700) at pthread_create.c:304 #10 0x00007f478a93f89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f478d0e3780 (LWP 2722)): [KCrash Handler] #6 QMap (other=..., this=0x7fff053b08e0) at /usr/include/qt4/QtCore/qmap.h:185 #7 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #8 0x00007f4765bb4787 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #9 0x00007f4765bb4934 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #10 0x00007f4765bb499c in RandrMonitorModule::resumedFromSuspend (this=0xe75f50) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202 #11 0x00007f4765bb528c in RandrMonitorModule::qt_metacall (this=0xe75f50, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at ./randrmonitor.moc:77 #12 0x00007f47893240e9 in QDBusConnectionPrivate::deliverCall (this=0xb48cc0, object=0xe75f50, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:942 #13 0x00007f478932d38f in QDBusCallDeliveryEvent::placeMetaCall (this=<optimized out>, object=<optimized out>) at qdbusintegrator_p.h:103 #14 0x00007f478bd66a5e in QObject::event (this=0xe75f50, e=<optimized out>) at kernel/qobject.cpp:1217 #15 0x00007f478b100424 in notify_helper (e=0x100af80, receiver=0xe75f50, this=0xb507e0) at kernel/qapplication.cpp:4486 #16 QApplicationPrivate::notify_helper (this=0xb507e0, receiver=0xe75f50, e=0x100af80) at kernel/qapplication.cpp:4458 #17 0x00007f478b105291 in QApplication::notify (this=0x7fff053b1460, receiver=0xe75f50, e=0x100af80) at kernel/qapplication.cpp:4365 #18 0x00007f478cabd1e6 in KApplication::notify (this=0x7fff053b1460, receiver=0xe75f50, event=0x100af80) at ../../kdeui/kernel/kapplication.cpp:311 #19 0x00007f478bd4fafc in QCoreApplication::notifyInternal (this=0x7fff053b1460, receiver=0xe75f50, event=0x100af80) at kernel/qcoreapplication.cpp:787 #20 0x00007f478bd5351f in sendEvent (event=0x100af80, receiver=0xe75f50) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xabe5e0) at kernel/qcoreapplication.cpp:1428 #22 0x00007f478bd7aa73 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277 #24 0x00007f4787b33a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007f4787b34258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007f4787b34429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f478bd7aed6 in QEventDispatcherGlib::processEvents (this=0xac0d30, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #28 0x00007f478b1a807e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007f478bd4ecf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007f478bd4eef7 in QEventLoop::exec (this=0x7fff053b13f0, flags=...) at kernel/qeventloop.cpp:201 #31 0x00007f478bd53789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #32 0x00007f477b585d65 in kdemain (argc=1, argv=0xaff920) at ../../kded/kded.cpp:924 #33 0x0000000000408547 in launch (argc=1, _name=0x40b2d7 "kded4", args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b15e "0") at ../../kinit/kinit.cpp:746 #34 0x0000000000405949 in main (argc=4, argv=0x7fff00000001, envp=0x7fff053b25c0) at ../../kinit/kinit.cpp:1861 Reported using DrKonqi
*** Bug 284599 has been marked as a duplicate of this bug. ***
Created attachment 65196 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Closed my laptop and carried it with me to my desk. -- Backtrace (Reduced): #7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185 #8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 65197 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Closed my laptop and carried it with me to my desk. -- Backtrace (Reduced): #7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185 #8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 65198 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Closed my laptop and carried it with me to my desk. -- Backtrace (Reduced): #7 QMap (other=..., this=0xbfe206f8) at /usr/include/qt4/QtCore/qmap.h:185 #8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #9 0xa9a7842e in RandrMonitorModule::outputs (this=0x864fae8, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #10 0xa9a78658 in RandrMonitorModule::connectedOutputs (this=0x864fae8, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #11 0xa9a786ca in RandrMonitorModule::resumedFromSuspend (this=0x864fae8) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 285693 has been marked as a duplicate of this bug. ***
*** Bug 287892 has been marked as a duplicate of this bug. ***
*** Bug 288382 has been marked as a duplicate of this bug. ***
*** Bug 288456 has been marked as a duplicate of this bug. ***
Created attachment 66730 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4 - What I was doing when the application crashed: Closed my laptop to carry it. This happens each time it suspends to ram. -- Backtrace (Reduced): #6 QMap (other=..., this=0x7fffa80d17c0) at /usr/include/QtCore/qmap.h:185 #7 RandRScreen::outputs (this=0x0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/randrscreen.cpp:231 #8 0x00007f7034140517 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:250 #9 0x00007f70341406c4 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:232 #10 0x00007f703414072c in RandrMonitorModule::resumedFromSuspend (this=0x9c90f0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 66729 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4 - What I was doing when the application crashed: Closed my laptop to carry it. This happens each time it suspends to ram. -- Backtrace (Reduced): #6 QMap (other=..., this=0x7fffa80d17c0) at /usr/include/QtCore/qmap.h:185 #7 RandRScreen::outputs (this=0x0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/randrscreen.cpp:231 #8 0x00007f7034140517 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:250 #9 0x00007f70341406c4 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:232 #10 0x00007f703414072c in RandrMonitorModule::resumedFromSuspend (this=0x9c90f0) at /usr/src/debug/kde-workspace-4.7.2/kcontrol/randr/module/randrmonitor.cpp:202
Created attachment 66984 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: Going into Sleep mode or coming out of Sleep mode (not sure) - Custom settings of the application: Dual headed display -- Backtrace (Reduced): #7 QMap (other=..., this=0xbfe1a4e8) at /usr/include/qt4/QtCore/qmap.h:185 #8 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #9 0xa998642e in RandrMonitorModule::outputs (this=0x904bcb0, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #10 0xa9986658 in RandrMonitorModule::connectedOutputs (this=0x904bcb0, display=...) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #11 0xa99866ca in RandrMonitorModule::resumedFromSuspend (this=0x904bcb0) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 294581 has been marked as a duplicate of this bug. ***
*** Bug 294685 has been marked as a duplicate of this bug. ***
Created attachment 69209 [details] New crash information added by DrKonqi kded4 ($Id$) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4 - What I was doing when the application crashed: Waking up the system after sleep. - Unusual behavior I noticed: It always happens. -- Backtrace (Reduced): #6 QMap (other=..., this=0x7fff9ad9fe80) at /usr/include/qt4/QtCore/qmap.h:185 #7 RandRScreen::outputs (this=0x0) at ../../../../kcontrol/randr/randrscreen.cpp:231 #8 0x00007fa961dd0787 in RandrMonitorModule::outputs (this=<optimized out>, display=..., connected=true, active=false, validCrtc=false) at ../../../../kcontrol/randr/module/randrmonitor.cpp:250 #9 0x00007fa961dd0934 in RandrMonitorModule::connectedOutputs (this=<optimized out>, display=<optimized out>) at ../../../../kcontrol/randr/module/randrmonitor.cpp:232 #10 0x00007fa961dd099c in RandrMonitorModule::resumedFromSuspend (this=0x15bc220) at ../../../../kcontrol/randr/module/randrmonitor.cpp:202
*** Bug 296124 has been marked as a duplicate of this bug. ***
*** Bug 296131 has been marked as a duplicate of this bug. ***
*** Bug 300552 has been marked as a duplicate of this bug. ***
Thank you for your bug report or feature request. Unfortunately, we did not have a maintainer for the "krandr" components, which are used to manage displays and monitors in the KDE Workspaces. The "krandr" components has been superseded by "KScreen" in newer releases of the KDE Workspaces. It is compatible with all versions since 4.11, and is also used with Plasma 5. Please check with your distribution how to update to KScreen. If this issue or feature request is still applicable to KScreen version 1.0.5 or newer, please add a comment. We will then reassign this ticket to KScreen developers. If you are already using KScreen to manage displays or monitors, and found a different bug or need a specific feature, please create a new ticket for "KScreen" product in this bugzilla using this link: https://bugs.kde.org/enter_bug.cgi?product=KScreen (This is an automatic message from the KDE Bug Triaging Team)