Bug 329810 - Kontact crashes consistently when closed, never remembers calender colours
Summary: Kontact crashes consistently when closed, never remembers calender colours
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.12
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-01-10 14:09 UTC by Kirchkamp
Modified: 2017-01-07 22:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kirchkamp 2014-01-10 14:09:33 UTC
Application: kontact (4.12)
KDE Platform Version: 4.12.0
Qt Version: 4.8.4
Operating System: Linux 3.11.0-15-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
To reproduce this bug, just open Kontact and close it again. Kontact will always crash upon closing (and will, sadly, not remember calendar colours set in between).
This problem appeared a few days ago already with 4.11.3.
After upgrading to 4.12 the problem persists :-(

The crash can be reproduced every time.

-- 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 0x7f6e9dc277c0 (LWP 2347))]

Thread 5 (Thread 0x7f6e7eee3700 (LWP 2348)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f6e989fe1cd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f6e989fe209 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f6e95123f6e in start_thread (arg=0x7f6e7eee3700) at pthread_create.c:311
#4  0x00007f6e9b1999cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f6e3e5d0700 (LWP 2349)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f6e9873ebbd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f6e98a2da76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f6e95123f6e in start_thread (arg=0x7f6e3e5d0700) at pthread_create.c:311
#4  0x00007f6e9b1999cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f6e2d4fa700 (LWP 2354)):
#0  0x00007f6e94c8b0ed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f6e94c8b399 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6e94c4a7f0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6e94c4b565 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f6e94c4b7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f6e9b912a76 in QEventDispatcherGlib::processEvents (this=0x7f6e200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f6e9b8e45ef in QEventLoop::processEvents (this=this@entry=0x7f6e2d4f9db0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f6e9b8e48e5 in QEventLoop::exec (this=this@entry=0x7f6e2d4f9db0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f6e9b7e388f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9  0x00007f6e9b7e5f2f in QThreadPrivate::start (arg=0x1b2daf0) at thread/qthread_unix.cpp:338
#10 0x00007f6e95123f6e in start_thread (arg=0x7f6e2d4fa700) at pthread_create.c:311
#11 0x00007f6e9b1999cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f6e27781700 (LWP 2355)):
#0  0x00007f6e9b18cf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f6e94c4b6a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6e94c4b7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6e9b912a76 in QEventDispatcherGlib::processEvents (this=0x7f6e1c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f6e9b8e45ef in QEventLoop::processEvents (this=this@entry=0x7f6e27780d70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f6e9b8e48e5 in QEventLoop::exec (this=this@entry=0x7f6e27780d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f6e9b7e388f in QThread::exec (this=this@entry=0x600b110) at thread/qthread.cpp:542
#7  0x00007f6e9b8c5d13 in QInotifyFileSystemWatcherEngine::run (this=0x600b110) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f6e9b7e5f2f in QThreadPrivate::start (arg=0x600b110) at thread/qthread_unix.cpp:338
#9  0x00007f6e95123f6e in start_thread (arg=0x7f6e27781700) at pthread_create.c:311
#10 0x00007f6e9b1999cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f6e9dc277c0 (LWP 2347)):
[KCrash Handler]
#6  0x00007f6e9c742f64 in QAbstractScrollArea::horizontalScrollBar (this=0x2593510) at widgets/qabstractscrollarea.cpp:693
#7  0x00007f6e9cfb12a7 in restoreScrollBarState (this=0x2619f80) at ../../kdeui/itemviews/kviewstatesaver.cpp:64
#8  KViewStateSaver::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kviewstatesaver.moc:53
#9  0x00007f6e9b8fddce in QObject::event (this=0x26192c0, e=<optimized out>) at kernel/qobject.cpp:1194
#10 0x00007f6e9c2d6dfc in QApplicationPrivate::notify_helper (this=this@entry=0x18b0c80, receiver=receiver@entry=0x26192c0, e=e@entry=0x23622d0) at kernel/qapplication.cpp:4567
#11 0x00007f6e9c2dd470 in QApplication::notify (this=this@entry=0x7fffa4fabac0, receiver=receiver@entry=0x26192c0, e=e@entry=0x23622d0) at kernel/qapplication.cpp:4353
#12 0x00007f6e9cfe0c6a in KApplication::notify (this=0x7fffa4fabac0, receiver=0x26192c0, event=0x23622d0) at ../../kdeui/kernel/kapplication.cpp:311
#13 0x00007f6e9b8e58bd in QCoreApplication::notifyInternal (this=0x7fffa4fabac0, receiver=receiver@entry=0x26192c0, event=event@entry=0x23622d0) at kernel/qcoreapplication.cpp:946
#14 0x00007f6e9b8e8e1f in sendEvent (event=0x23622d0, receiver=0x26192c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x18701d0) at kernel/qcoreapplication.cpp:1570
#16 0x00007f6e9b8e92c3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#17 0x00007f6e9b913073 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#18 postEventSourceDispatch (s=0x189e390) at kernel/qeventdispatcher_glib.cpp:279
#19 0x00007f6e94c4b3b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f6e94c4b708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f6e94c4b7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f6e9b912a55 in QEventDispatcherGlib::processEvents (this=0x189e210, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x00007f6e9c3789d6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007f6e9b8e45ef in QEventLoop::processEvents (this=this@entry=0x7fffa4fab9c0, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f6e9b8e48e5 in QEventLoop::exec (this=this@entry=0x7fffa4fab9c0, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007f6e9b8e9e5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#27 0x00007f6e9c2d534c in QApplication::exec () at kernel/qapplication.cpp:3828
#28 0x0000000000403660 in main (argc=1, argv=0x7fffa4fabc08) at ../../../kontact/src/main.cpp:219

The reporter indicates this bug may be a duplicate of or related to bug 328755.

Possible duplicates by query: bug 329304, bug 328755.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 19:34:09 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:12:18 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.