Application: knotify4 (4.13.0) KDE Platform Version: 4.13.0 Qt Version: 4.8.6 Operating System: Linux 3.13.0-27-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: - What I was doing when the application crashed: I opened the lid of my sleeping notebook, logged in and then I saw the segfault crash. I can't tell whether the application crashed while going to sleep or while resuming. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb7564d37c0 (LWP 1795))] Thread 3 (Thread 0x7fb742b3d700 (LWP 1796)): #0 0x00007fb750acd62a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fb750acd9b9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fb750a8c0f6 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fb753df97be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007fb753dcb0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007fb753dcb3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007fb753cc7c5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007fb753dac823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fb753cca32f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fb750f6b182 in start_thread (arg=0x7fb742b3d700) at pthread_create.c:312 #10 0x00007fb75368030d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fb72affd700 (LWP 7525)): [KCrash Handler] #5 0x00007fb750aa697d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007fb750aa6c52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007fb750f6af82 in __nptl_deallocate_tsd () at pthread_create.c:158 #8 0x00007fb750f6b195 in start_thread (arg=0x7fb72affd700) at pthread_create.c:325 #9 0x00007fb75368030d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fb7564d37c0 (LWP 1795)): #0 0x00007fb7536716bd in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007fb750accc20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fb750a8bb14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fb750a8bf7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007fb750a8c0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007fb753df97be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007fb754adbbb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x00007fb753dcb0af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007fb753dcb3a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fb753dd0b79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x0000000000409a09 in ?? () #11 0x00007fb7535a6ec5 in __libc_start_main (main=0x4093f0, argc=1, argv=0x7fffc235fc58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffc235fc48) at libc-start.c:287 #12 0x0000000000409aea in _start () Possible duplicates by query: bug 334178, bug 329284, bug 325311. Reported using DrKonqi
If this is reproducible, please install debug symbols to get a better backtrace. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
I installed the debug files. But the issue did not occur again so far. If it does, I will provide more information.
I also had a segfault with Knotify, the following is mostly an automated bug report. Sorry if it is a different bug. Application: knotify4 (4.13.3) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-37-generic x86_64 Distribution: Ubuntu 14.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Knotify has automaticly decided this is the same bug. Sorry if it is totally different bug. I was playing Konquest when Knotify popped up and asked if I wanted to report this bug. I also had Chromium, Kcalc, Konsole & System monitor open but not visible. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4aa21437c0 (LWP 2416))] Thread 3 (Thread 0x7f4a8e781700 (LWP 2417)): #0 0x00007f4a9cbe87ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f4a88000a60) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7f4a88000a60) at pthread_mutex_unlock.c:310 #2 0x00007f4a9c7479c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f4a9c705680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f4a9c705f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f4a9c7060ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f4a9fa727be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007f4a9fa440af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f4a9fa443a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f4a9f940c5f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x00007f4a9fa25823 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x00007f4a9f94332f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x00007f4a9cbe5182 in start_thread (arg=0x7f4a8e781700) at pthread_create.c:312 #13 0x00007f4a9f2f8fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f4a577fe700 (LWP 11818)): [KCrash Handler] #5 0x00007f4a9c72097d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f4a9c720c52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007f4a9cbe4f82 in __nptl_deallocate_tsd () at pthread_create.c:158 #8 0x00007f4a9cbe5195 in start_thread (arg=0x7f4a577fe700) at pthread_create.c:325 #9 0x00007f4a9f2f8fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f4aa21437c0 (LWP 2416)): #0 0x00007f4a9f2ea36d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f4a9c746c20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f4a9c705b14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f4a9c705f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f4a9c7060ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f4a9fa727be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007f4aa0754bb6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x00007f4a9fa440af in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007f4a9fa443a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007f4a9fa49b79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x0000000000409a09 in ?? () #11 0x00007f4a9f21fec5 in __libc_start_main (main=0x4093f0, argc=1, argv=0x7fffb626b358, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb626b348) at libc-start.c:287 #12 0x0000000000409aea in _start () Possible duplicates by query: bug 337144, bug 334912, bug 334178, bug 329284. Report to https://bugs.kde.org/
This bug happened to me when I unplugged power to my notebook.
I believe this bug is related to report 334178 I got a crash reporter for the same when my irc client (quassel) tried to send a notification. Bug# 334178 talks about mail sending notifications.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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 mark the bug 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!
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!