Bug 351555 - Kontact segfault on renaming an event
Summary: Kontact segfault on renaming an event
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-08-21 10:51 UTC by Tom Mittelstädt
Modified: 2018-02-01 09:44 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-08-21 10:51:29 UTC
Application: kontact (4.14.7)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 3.19.0-25-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
I was editing the title of an event (of a synced CalDAV calendar). On accepting the changes Kontact/KOrganzier segfaulted.
This happens quite often (but not always) since a few weeks.

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 0x7f0b321f7840 (LWP 24881))]

Thread 6 (Thread 0x7f0b1084f700 (LWP 24882)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f0b2ce9981d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f0b2ce99859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f0b295916aa in start_thread (arg=0x7f0b1084f700) at pthread_create.c:333
#4  0x00007f0b2f6d6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f0acff4c700 (LWP 24883)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f0b2cbda20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f0b2cec8fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f0b295916aa in start_thread (arg=0x7f0acff4c700) at pthread_create.c:333
#4  0x00007f0b2f6d6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f0abbfb2700 (LWP 24901)):
#0  0x00007f0b2f6cb8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f0b290abebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0b290abfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0b2fe5f87e in QEventDispatcherGlib::processEvents (this=0x7f0ab40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007f0b2fe2ed21 in QEventLoop::processEvents (this=this@entry=0x7f0abbfb1d90, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0b2fe2f085 in QEventLoop::exec (this=this@entry=0x7f0abbfb1d90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0b2fd22e89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007f0b2fd256ff in QThreadPrivate::start (arg=0x1608c80) at thread/qthread_unix.cpp:349
#8  0x00007f0b295916aa in start_thread (arg=0x7f0abbfb2700) at pthread_create.c:333
#9  0x00007f0b2f6d6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f0ab1e9b700 (LWP 24966)):
#0  0x00007f0b2fe5f288 in testAndSetOrdered (newValue=0, expectedValue=1, this=0x2a93f40) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:145
#1  testAndSetRelease (newValue=0, expectedValue=1, this=0x2a93f40) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:272
#2  unlockInline (this=0x2f17308) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:171
#3  unlock (this=<synthetic pointer>) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:121
#4  ~QMutexLocker (this=<synthetic pointer>, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:115
#5  canWaitLocked (this=0x2f172c0) at ../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:229
#6  postEventSourcePrepare (s=0x7f0aa80012e0, timeout=0x7f0ab1e9ab74) at kernel/qeventdispatcher_glib.cpp:279
#7  0x00007f0b290ab3fd in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f0b290abde8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f0b290abfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f0b2fe5f87e in QEventDispatcherGlib::processEvents (this=0x7f0aa80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#11 0x00007f0b2fe2ed21 in QEventLoop::processEvents (this=this@entry=0x7f0ab1e9ad40, flags=...) at kernel/qeventloop.cpp:149
#12 0x00007f0b2fe2f085 in QEventLoop::exec (this=this@entry=0x7f0ab1e9ad40, flags=...) at kernel/qeventloop.cpp:204
#13 0x00007f0b2fd22e89 in QThread::exec (this=this@entry=0x3681770) at thread/qthread.cpp:538
#14 0x00007f0b2fe0f493 in QInotifyFileSystemWatcherEngine::run (this=0x3681770) at io/qfilesystemwatcher_inotify.cpp:265
#15 0x00007f0b2fd256ff in QThreadPrivate::start (arg=0x3681770) at thread/qthread_unix.cpp:349
#16 0x00007f0b295916aa in start_thread (arg=0x7f0ab1e9b700) at pthread_create.c:333
#17 0x00007f0b2f6d6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0abb128700 (LWP 1447)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f0ac6de9a7a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f0ac6de9aa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f0b295916aa in start_thread (arg=0x7f0abb128700) at pthread_create.c:333
#4  0x00007f0b2f6d6eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0b321f7840 (LWP 24881)):
[KCrash Handler]
#6  0x00007f0b2e9dd290 in vtable for Akonadi::ItemPrivate () from /usr/lib/libakonadi-kde.so.4
#7  0x00007f0b308bbf80 in QApplication::x11ProcessEvent (this=0x7fff3aa63e90, event=event@entry=0x7fff3aa639c0) at kernel/qapplication_x11.cpp:3528
#8  0x00007f0b308e5ba2 in x11EventSourceDispatch (s=0x150d8f0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007f0b290abc3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f0b290abf20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f0b290abfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f0b2fe5f85e in QEventDispatcherGlib::processEvents (this=0x146a1b0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#13 0x00007f0b308e5c66 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f0b2fe2ed21 in QEventLoop::processEvents (this=this@entry=0x7fff3aa63da0, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007f0b2fe2f085 in QEventLoop::exec (this=this@entry=0x7fff3aa63da0, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007f0b2fe34b09 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#17 0x00007f0b3083bc1c in QApplication::exec () at kernel/qapplication.cpp:3828
#18 0x0000000000403509 in main (argc=1, argv=0x7fff3aa63fe8) at ../../../kontact/src/main.cpp:219

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:21:03 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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:44:16 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.