Application: plasma-overlay (0.0) KDE Platform Version: 4.11.00 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.8.0-29-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: I tried it a few times with the same exact steps; for some reason, it seems to fail to cleanly exit after unlocking the screen. It might be an issue with one of the Plasmaoids I'm using that communicates with MPRIS. The crash can be reproduced every time. -- Backtrace: Application: Plasma for the Screensaver (plasma-overlay), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd5dc4ed7c0 (LWP 9305))] Thread 4 (Thread 0x7fd5c0de8700 (LWP 9306)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fd5d5ff4b27 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007fd5d5ff4b59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007fd5d0f9af8e in start_thread (arg=0x7fd5c0de8700) at pthread_create.c:311 #4 0x00007fd5d8733e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7fd52f767700 (LWP 9309)): #0 0x00007fd5d06c9359 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fd5d06c95e9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fd5d068a30e in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd5d8eac036 in QEventDispatcherGlib::processEvents (this=0x7fd5280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007fd5d8e7c38f in QEventLoop::processEvents (this=this@entry=0x7fd52f766d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007fd5d8e7c618 in QEventLoop::exec (this=this@entry=0x7fd52f766d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007fd5d8d7e410 in QThread::exec (this=this@entry=0x263c380) at thread/qthread.cpp:542 #7 0x00007fd5d8e5dedf in QInotifyFileSystemWatcherEngine::run (this=0x263c380) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007fd5d8d80bec in QThreadPrivate::start (arg=0x263c380) at thread/qthread_unix.cpp:338 #9 0x00007fd5d0f9af8e in start_thread (arg=0x7fd52f767700) at pthread_create.c:311 #10 0x00007fd5d8733e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7fd52d948700 (LWP 9320)): #0 0x00007fd5d87273cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007fd5d068a1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fd5d068a304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd5d8eac036 in QEventDispatcherGlib::processEvents (this=0x7fd5140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007fd5d8e7c38f in QEventLoop::processEvents (this=this@entry=0x7fd52d947d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007fd5d8e7c618 in QEventLoop::exec (this=this@entry=0x7fd52d947d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007fd5d8d7e410 in QThread::exec (this=this@entry=0x2f75170) at thread/qthread.cpp:542 #7 0x00007fd5d8e5dedf in QInotifyFileSystemWatcherEngine::run (this=0x2f75170) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007fd5d8d80bec in QThreadPrivate::start (arg=0x2f75170) at thread/qthread_unix.cpp:338 #9 0x00007fd5d0f9af8e in start_thread (arg=0x7fd52d948700) at pthread_create.c:311 #10 0x00007fd5d8733e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7fd5dc4ed7c0 (LWP 9305)): [KCrash Handler] #6 0x00007fd5d921e74b in QDBusAdaptorConnector::relaySlot (this=this@entry=0x7fd51c05e790, argv=argv@entry=0x7fff88cac4d0) at qdbusabstractadaptor.cpp:270 #7 0x00007fd5d921ed55 in QDBusAdaptorConnector::qt_metacall (this=0x7fd51c05e790, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff88cac4d0) at qdbusabstractadaptor.cpp:366 #8 0x00007fd5d8e922b3 in QMetaObject::activate (sender=sender@entry=0x7fd51c04efd0, m=m@entry=0x7fd5d91d5b40 <QObject::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff88cac4d0) at kernel/qobject.cpp:3558 #9 0x00007fd5d8e92b2f in QObject::destroyed (this=this@entry=0x7fd51c04efd0, _t1=_t1@entry=0x7fd51c04efd0) at .moc/release-shared/moc_qobject.cpp:149 #10 0x00007fd5d8e96a33 in QObject::~QObject (this=0x7fd51c04efd0, __in_chrg=<optimized out>) at kernel/qobject.cpp:843 #11 0x00007fd5d4f3f619 in KIO::Scheduler::~Scheduler (this=0x7fd51c04efd0, __in_chrg=<optimized out>) at ../../kio/kio/scheduler.cpp:791 #12 0x00007fd5d4f4b16b in KIO::SchedulerPrivate::~SchedulerPrivate (this=0x7fd51c025180, __in_chrg=<optimized out>) at ../../kio/kio/scheduler.cpp:667 #13 0x00007fd5d4f45da7 in destroy () at ../../kio/kio/scheduler.cpp:748 #14 0x00007fd5d8676121 in __run_exit_handlers (status=0, listp=0x7fd5d89fb6a8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:77 #15 0x00007fd5d86761a5 in __GI_exit (status=<optimized out>) at exit.c:99 #16 0x00007fd5d865beac in __libc_start_main (main=0x413a30 <main(int, char**)>, argc=1, ubp_av=0x7fff88cac718, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff88cac708) at libc-start.c:294 #17 0x0000000000413fd1 in _start () Possible duplicates by query: bug 316003, bug 315838. Reported using DrKonqi
*** Bug 316003 has been marked as a duplicate of this bug. ***
*** Bug 315838 has been marked as a duplicate of this bug. ***
Can you run plasma-desktop in valgrind and report back? kquitapp plasma-desktop; valgrind plasma-desktop; then reproduce the crash.
It's not within plasma-desktop; it's within plasma-overlay, the Plasma app that shows the widgets in screensavers. I don't know if it'd be possible to do that.
Here's a Fedora bug that appears to be the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=922975 Do the attachments on that bug (e.g. stack trace, log messages) help?
marking confirmed, have a bazillion downstream crash reports per comment #5
I just ran into this bug on a freshly installed system, using kernel-3.13.5-200.fc20.x86_64 and the latest KDE 4.12 updates from the Fedora 20 updates-testing repos. Had ABRT not popped up in the systray, I would never had known about it since it apparently occurred on one of my remote sessions over the weekend. Attaching ABRT diag files, although I'm not sure how much help they'll be. But, since I have an affected system, I'll be willing to help troubleshoot the issue. For reference, the system itself is an Intel Core i7 with the onboard Intel GPU.
Created attachment 85386 [details] Core Backtrace
Created attachment 85387 [details] dso_list
Created attachment 85388 [details] environment
Created attachment 85389 [details] memory maps
*** Bug 332064 has been marked as a duplicate of this bug. ***
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham