Bug 348656 - Kontact crashed on closing KOrganizer window
Summary: Kontact crashed on closing KOrganizer window
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-06-03 18:03 UTC by Tom Mittelstädt
Modified: 2018-02-01 09:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Mittelstädt 2015-06-03 18:03:55 UTC
Application: kontact (4.14.6)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.19.0-18-generic x86_64
Distribution: Ubuntu 15.04

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

Closing a child window crashes Kontact from time to time. __

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffa7c42b800 (LWP 22143))]

Thread 5 (Thread 0x7ffa5c715700 (LWP 22144)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffa770c281d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007ffa770c2859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007ffa737c06aa in start_thread (arg=0x7ffa5c715700) at pthread_create.c:333
#4  0x00007ffa79900eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7ffa1bdfa700 (LWP 22145)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffa76e0320d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007ffa770f1fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007ffa737c06aa in start_thread (arg=0x7ffa1bdfa700) at pthread_create.c:333
#4  0x00007ffa79900eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ffa082a9700 (LWP 22160)):
#0  0x00007ffa798f58dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffa732daebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffa732dafcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffa7a08982e in QEventDispatcherGlib::processEvents (this=0x7ffa000008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007ffa7a058cd1 in QEventLoop::processEvents (this=this@entry=0x7ffa082a8dd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffa7a059035 in QEventLoop::exec (this=this@entry=0x7ffa082a8dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffa79f4ce89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007ffa79f4f6ff in QThreadPrivate::start (arg=0xebc820) at thread/qthread_unix.cpp:349
#8  0x00007ffa737c06aa in start_thread (arg=0x7ffa082a9700) at pthread_create.c:333
#9  0x00007ffa79900eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7ff9fffff700 (LWP 22183)):
#0  0x00007ffa7331f7a4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ffa732da3f0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffa732dade8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffa732dafcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffa7a08982e in QEventDispatcherGlib::processEvents (this=0x7ff9f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x00007ffa7a058cd1 in QEventLoop::processEvents (this=this@entry=0x7ff9ffffed80, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007ffa7a059035 in QEventLoop::exec (this=this@entry=0x7ff9ffffed80, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007ffa79f4ce89 in QThread::exec (this=this@entry=0x1e5f9b0) at thread/qthread.cpp:538
#8  0x00007ffa7a039443 in QInotifyFileSystemWatcherEngine::run (this=0x1e5f9b0) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x00007ffa79f4f6ff in QThreadPrivate::start (arg=0x1e5f9b0) at thread/qthread_unix.cpp:349
#10 0x00007ffa737c06aa in start_thread (arg=0x7ff9fffff700) at pthread_create.c:333
#11 0x00007ffa79900eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ffa7c42b800 (LWP 22143)):
[KCrash Handler]
#6  0x0000000000000050 in ?? ()
#7  0x00007ffa7aae4f80 in QApplication::x11ProcessEvent (this=0x7ffd607eca10, event=event@entry=0x7ffd607ec540) at kernel/qapplication_x11.cpp:3528
#8  0x00007ffa7ab0eba2 in x11EventSourceDispatch (s=0xd766b0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007ffa732dac3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffa732daf20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffa732dafcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffa7a08980e in QEventDispatcherGlib::processEvents (this=0xd0c1b0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#13 0x00007ffa7ab0ec66 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007ffa7a058cd1 in QEventLoop::processEvents (this=this@entry=0x7ffd607ec920, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007ffa7a059035 in QEventLoop::exec (this=this@entry=0x7ffd607ec920, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007ffa7a05eab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#17 0x00007ffa7aa64c1c in QApplication::exec () at kernel/qapplication.cpp:3828
#18 0x0000000000403509 in main (argc=1, argv=0x7ffd607ecb68) at ../../../kontact/src/main.cpp:219

Possible duplicates by query: bug 348532, bug 347811, bug 347733, bug 347636, bug 347568.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 19:35:49 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:46:22 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.