Bug 334178

Summary: Knotify Crash on mail receipt
Product: [Unmaintained] kdelibs Reporter: David Pyke <kdebugs>
Component: knotifyAssignee: Olivier Goffart <ogoffart>
Status: RESOLVED WORKSFORME    
Severity: crash CC: cfeck, nightflier
Priority: NOR Keywords: drkonqi, triaged
Version First Reported In: 4.13.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description David Pyke 2014-05-01 13:31:35 UTC 
Application: knotify4 (4.13.0)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.14.1 x86_64
Distribution: Ubuntu 14.04 LTS

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

I was surfing the web with wine programs open (office) when I received one of a number of email recevied to my two accounts.  The notification showed the arrival of the mail and then the crash notification showed.

-- 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 0x7ff3ff4ca7c0 (LWP 3125))]

Thread 3 (Thread 0x7ff3eb7a1700 (LWP 3126)):
#0  0x00007ff3fc67ffbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ff3f9a99fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff3f9a9a0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff3fce067be in QEventDispatcherGlib::processEvents (this=0x7ff3e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007ff3fcdd80af in QEventLoop::processEvents (this=this@entry=0x7ff3eb7a0de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff3fcdd83a5 in QEventLoop::exec (this=this@entry=0x7ff3eb7a0de0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ff3fccd4c5f in QThread::exec (this=this@entry=0x1c6a6d0) at thread/qthread.cpp:537
#7  0x00007ff3fcdb9823 in QInotifyFileSystemWatcherEngine::run (this=0x1c6a6d0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ff3fccd732f in QThreadPrivate::start (arg=0x1c6a6d0) at thread/qthread_unix.cpp:349
#9  0x00007ff3f9f79182 in start_thread (arg=0x7ff3eb7a1700) at pthread_create.c:312
#10 0x00007ff3fc68d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7ff3d17fa700 (LWP 25248)):
[KCrash Handler]
#6  0x00007ff3f9ab497d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007ff3f9ab4c52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007ff3f9f78f82 in __nptl_deallocate_tsd () at pthread_create.c:158
#9  0x00007ff3f9f79195 in start_thread (arg=0x7ff3d17fa700) at pthread_create.c:325
#10 0x00007ff3fc68d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ff3ff4ca7c0 (LWP 3125)):
#0  0x00007ff3fc67e6bd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ff3f9adac20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff3f9a99b14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff3f9a99f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ff3f9a9a0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ff3fce067be in QEventDispatcherGlib::processEvents (this=0x1a85630, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x00007ff3fdae8bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x00007ff3fcdd80af in QEventLoop::processEvents (this=this@entry=0x7fffd9410c00, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007ff3fcdd83a5 in QEventLoop::exec (this=this@entry=0x7fffd9410c00, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007ff3fcdddb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#10 0x00007ff3fda4537c in QApplication::exec () at kernel/qapplication.cpp:3828
#11 0x0000000000409a09 in main (argc=1, argv=0x7fffd9410e58) at ../../knotify/main.cpp:74

Possible duplicates by query: bug 329284, bug 325311.

Reported using DrKonqi
Comment 1 Christoph Feck 2014-05-03 11:17:17 UTC 
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
Comment 2 David Pyke 2014-05-08 22:22:09 UTC 
I have tried but the bug reporter won't recognize the package as being installed.  Just tho make sure, what (k)ubuntu package should I be installing?
Comment 3 Roy Stefanussen 2014-05-31 11:20:34 UTC 
Created attachment 86927 [details]
New crash information added by DrKonqi

knotify4 (4.13.0) on KDE Platform 4.13.0 using Qt 4.8.6

- What I was doing when the application crashed:

Nothing. The computer sits idle overnight. No hibernation, no sleep. Only power saving enabled is screen off after 10 minutes. Notifications working as normal, showing emails received in Thunderbird.

-- Backtrace (Reduced):
#8  0x00007f28260f3f82 in __nptl_deallocate_tsd () at pthread_create.c:158
#9  0x00007f28260f4195 in start_thread (arg=0x7f27feffc700) at pthread_create.c:325
#10 0x00007f282880830d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Comment 4 Andrew Crouthamel 2018-09-25 03:30:51 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 5 Andrew Crouthamel 2018-10-27 02:48:28 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!