Kontact hangs/crashes after running for some time

[LarsIvarIgesund]

Binary package hint: kdepim

This bug has been a problem for me for a long time, I think maybe since I upgraded to KDE 4.1.2 (in Hardy? or maybe with Intrepid). I have reported it upstream, will connect the reports.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb7fc8430:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kontact
Package: kontact 4:4.2.2-0ubuntu1
ProcCmdline: /usr/bin/kontact
ProcEnviron:
 LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en_GB:en
 LANG=nn_NO.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdepim
Stacktrace: #0 0xb7fc8430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kontact crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libical0: installed version 0.43-2ubuntu1~intrepid1~ppa1, latest version: 0.43-2
libgtk2.0-common: installed version 2.16.0-1ubuntu3, latest version: 2.16.0-1ubuntu4
libc6: installed version 2.9-4ubuntu5, latest version: 2.9-4ubuntu6
libgtk2.0-0: installed version 2.16.0-1ubuntu3, latest version: 2.16.0-1ubuntu4

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[LarsIvarIgesund (larsivar)]

If you have problems getting a stack trace, use the one I have posted in the bugs.kde.org report.

If I don't have an up-to-date system (jaunty), then you must tell me why since I check for updates at least twice a day to get rid of the rather obnoxious intel graphics driver issues.

[LarsIvarIgesund (larsivar)]

I don't know what's up with Apport, but today the KDE Crash handler decided to take action and I got a new stack trace for you.

It appears to be slightly different from the earlier ones, but it still involves the systray stuff. When that is said, it may not be the real reason since it appears to hang long before it crash (which can be forced by clicking one of the systray icons).

Program: Kontakt (kontact). Signal: SIGSEGV.
[Current thread is 0 (LWP 24380)]

Thread 2 (Thread 0xab3ffb90 (LWP 24704)):
#0 0xb8037430 in __kernel_vsyscall ()
#1 0xb598b7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb5c5f380 in QProcessManager::run (this=0x9b6ed30) at io/qprocess_unix.cpp:305
#3 0xb5b8d96e in QThreadPrivate::start (arg=0x9b6ed30) at thread/qthread_unix.cpp:189
#4 0xb51844ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb599349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb489e700 (LWP 24380)):
[KCrash Handler]
#6 0xb56ece17 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7 0xb61e25be in qt_x11_getX11InfoForWindow (xinfo=0xee11ecc, a=@0xbf95237c) at kernel/qwidget_x11.cpp:387
#8 0xb61e9dde in QWidgetPrivate::create_sys (this=0xee11dd8, window=130617268, initializeWindow=true, destroyOldWindow=true) at kernel/qwidget_x11.cpp:532
#9 0xb61abeac in QWidget::create (this=0xddceb10, window=130617268, initializeWindow=80, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1259
#10 0xb68035fc in QSystemTrayIconSys::addToTray (this=0xddceb10) at util/qsystemtrayicon_x11.cpp:236
#11 0xb6803918 in QSystemTrayIconSys (this=0xddceb10, q=0xa8cfcc8) at util/qsystemtrayicon_x11.cpp:198
#12 0xb6803a83 in QSystemTrayIconPrivate::install_sys (this=0xa8cfd18) at util/qsystemtrayicon_x11.cpp:336
#13 0xb67edc4a in QSystemTrayIcon::setVisible (this=0xa8cfcc8, visible=true) at util/qsystemtrayicon.cpp:275
#14 0xb0e35df6 in KMSystemTray::updateNewMessages (this=0xa8cfcc8) at /usr/include/qt4/QtGui/qsystemtrayicon.h:108
#15 0xb0e396e3 in KMSystemTray::qt_metacall (this=0xa8cfcc8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf9528e8) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmsystemtray.moc:79
#16 0xb5c97ca8 in QMetaObject::activate (sender=0xa8d13e0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#17 0xb5c98932 in QMetaObject::activate (sender=0xa8d13e0, m=0xb5d74904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#18 0xb5cd3717 in QTimer::timeout (this=0xa8d13e0) at .moc/release-shared/moc_qtimer.cpp:128
#19 0xb5c9d6fe in QTimer::timerEvent (this=0xa8d13e0, e=0xbf952d6c) at kernel/qtimer.cpp:261
#20 0xb5c9215f in QObject::event (this=0xa8d13e0, e=0xbf952d6c) at kernel/qobject.cpp:1082
#21 0xb6152f2c in QApplicationPrivate::notify_helper (this=0x9b578e0, receiver=0xa8d13e0, e=0xbf952d6c) at kernel/qapplication.cpp:4084
#22 0xb615b22e in QApplication::notify (this=0xbf953018, receiver=0xa8d13e0, e=0xbf952d6c) at kernel/qapplication.cpp:3631
#23 0xb6d7794d in KApplication::notify (this=0xbf953018, receiver=0xa8d13e0, event=0xbf952d6c) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#24 0xb5c81a3b in QCoreApplication::notifyInte...

[LarsIvarIgesund (larsivar)]

As noted in https://bugs.kde.org/show_bug.cgi?id=175289 I do not think KDE bug 190572 is the same as this one. I will update the reference here when I get around to reporting the new trace as a new KDE bug.

[LarsIvarIgesund (larsivar)]

I believe KDE bug 190572 doesn't match with this LP report.

[Harald Sitter (apachelogger)]

Closing in favor of KDE bug report, please refer there for updates. Thanks.