Bug 175289

I should mention that this continues to happen, primarly after kontact running for some time (typically overnight).

To be more exact about what happens;

Kontact turns black (or I suppose white, but I have a dark theme), there are no widgets whatsoever inside the main kontact window. If the window is up (not minimized), it turns black as I click on something. At this point nothing more happens until I click the cross to end the application. Still nothing happens, but if I then click one of the systray icons (either mail or akregator), it crashes with the stack trace shown above.

This still happens in KDE 4.2 - the stack trace being:

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

Thread 2 (Thread 0xafc82b90 (LWP 12047)):
#0  0xb80fa430 in __kernel_vsyscall ()
#1  0xb5b70df1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5e3f150 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb5d6f6ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb54a650f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5b78a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4c216c0 (LWP 11623)):
[KCrash Handler]
#6  0xb63bf661 in QImage::scanLine () from /usr/lib/libQtGui.so.4
#7  0xb639c640 in QWidgetPrivate::setWindowIcon_sys () from /usr/lib/libQtGui.so.4
#8  0xb636749b in QWidget::create () from /usr/lib/libQtGui.so.4
#9  0xb63632f3 in QWidgetPrivate::createWinId () from /usr/lib/libQtGui.so.4
#10 0xb6367a49 in QWidget::winId () from /usr/lib/libQtGui.so.4
#11 0xb68fa2f1 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb68fa778 in ?? () from /usr/lib/libQtGui.so.4
#13 0xb68fa8e3 in ?? () from /usr/lib/libQtGui.so.4
#14 0xb68e601a in QSystemTrayIcon::setVisible () from /usr/lib/libQtGui.so.4
#15 0xb12a42a1 in KMSystemTray::updateNewMessages (this=0x8eee408) at /usr/include/qt4/QtGui/qsystemtrayicon.h:104
#16 0xb12a7983 in KMSystemTray::qt_metacall (this=0x8eee408, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf8fb858) at /build/buildd/kdepim-4.2.0/obj-i486-linux-gnu/kmail/kmsystemtray.moc:78
#17 0xb5e74a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb5e757e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb5eaf7a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#20 0xb5e7b40e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#21 0xb5e6f53f in QObject::event () from /usr/lib/libQtCore.so.4
#22 0xb63118ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#23 0xb631972e in QApplication::notify () from /usr/lib/libQtGui.so.4
#24 0xb6e2afed in KApplication::notify (this=0xbf8fbf98, receiver=0x8eeffa8, event=0xbf8fbcec) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#25 0xb5e5fe61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#26 0xb5e8dd81 in ?? () from /usr/lib/libQtCore.so.4
#27 0xb5e8a520 in ?? () from /usr/lib/libQtCore.so.4
#28 0xb51386f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb513bda3 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb513bf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb5e8a478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb63abea5 in ?? () from /usr/lib/libQtGui.so.4
#33 0xb5e5e52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#34 0xb5e5e6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#35 0xb5e60da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#36 0xb6311767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#37 0x0804c072 in main (argc=1, argv=0xbf8fc294) at /build/buildd/kdepim-4.2.0/kontact/src/main.cpp:218

And still with KDE 4.2.1

Now got apport bug report at LaunchPad using 4.2.2 - see https://bugs.launchpad.net/kdepim/+bug/358672 .

Getting extremely annoying.

This should be fixed when using Qt4.5.x+. Can you check it ? Thanks

I have 4.5.0-0ubuntu4 installed (Kubuntu Jaunty) - should that work?

In any case, I still have this issue, although I haven't checked lately if the back trace is the same.

Please check if the first lines of the backtraces you are getting are something like:
"#6  0xb6f6c6a1 in QImage::scanLine () from /usr/lib/libQtGui.so.4
#7  0xb6f49680 in QWidgetPrivate::setWindowIcon_sys ()
   from /usr/lib/libQtGui.so.4
"
(it contains "QImage::scanLine" and "QWidgetPrivate::setWindowIcon_sys")
Thanks

I have a new crash, and it crash at the same time, but the trace seems to be different:

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

Thread 2 (Thread 0xab9feb90 (LWP 30383)):
#0  0xb8068430 in __kernel_vsyscall ()
#1  0xb59bd7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5c91380 in QProcessManager::run (this=0x92d4388) at io/qprocess_unix.cpp:305
#3  0xb5bbf96e in QThreadPrivate::start (arg=0x92d4388) at thread/qthread_unix.cpp:189
#4  0xb51b64ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb59c549e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb48d0700 (LWP 30362)):
[KCrash Handler]
#6  0xb571ee17 in XVisualIDFromVisual () from /usr/lib/libX11.so.6
#7  0xb621452e in qt_x11_getX11InfoForWindow (xinfo=0xc84a6e4, a=@0xbff850fc) at kernel/qwidget_x11.cpp:387
#8  0xb621bd4e in QWidgetPrivate::create_sys (this=0xc84a5f0, window=133697871, initializeWindow=true, destroyOldWindow=true) at kernel/qwidget_x11.cpp:532
#9  0xb61dde1c in QWidget::create (this=0xcc6b500, window=133697871, initializeWindow=88, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1259
#10 0xb683520c in QSystemTrayIconSys::addToTray (this=0xcc6b500) at util/qsystemtrayicon_x11.cpp:236
#11 0xb6835528 in QSystemTrayIconSys (this=0xcc6b500, q=0xa014f00) at util/qsystemtrayicon_x11.cpp:198
#12 0xb6835693 in QSystemTrayIconPrivate::install_sys (this=0xa014f50) at util/qsystemtrayicon_x11.cpp:336
#13 0xb681f85a in QSystemTrayIcon::setVisible (this=0xa014f00, visible=true) at util/qsystemtrayicon.cpp:275
#14 0xb0e66df6 in KMSystemTray::updateNewMessages (this=0xa014f00) at /usr/include/qt4/QtGui/qsystemtrayicon.h:108
#15 0xb0e6a6e3 in KMSystemTray::qt_metacall (this=0xa014f00, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbff85668) at /build/buildd/kdepim-4.2.2/obj-i486-linux-gnu/kmail/kmsystemtray.moc:79
#16 0xb5cc9ca8 in QMetaObject::activate (sender=0xa016648, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#17 0xb5cca932 in QMetaObject::activate (sender=0xa016648, m=0xb5da6904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#18 0xb5d05717 in QTimer::timeout (this=0xa016648) at .moc/release-shared/moc_qtimer.cpp:128
#19 0xb5ccf6fe in QTimer::timerEvent (this=0xa016648, e=0xbff85aec) at kernel/qtimer.cpp:261
#20 0xb5cc415f in QObject::event (this=0xa016648, e=0xbff85aec) at kernel/qobject.cpp:1082
#21 0xb6184e9c in QApplicationPrivate::notify_helper (this=0x92cec08, receiver=0xa016648, e=0xbff85aec) at kernel/qapplication.cpp:4084
#22 0xb618d19e in QApplication::notify (this=0xbff85d98, receiver=0xa016648, e=0xbff85aec) at kernel/qapplication.cpp:3631
#23 0xb6da894d in KApplication::notify (this=0xbff85d98, receiver=0xa016648, event=0xbff85aec) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#24 0xb5cb3a3b in QCoreApplication::notifyInternal (this=0xbff85d98, receiver=0xa016648, event=0xbff85aec) at kernel/qcoreapplication.cpp:602
#25 0xb5ce2d71 in QTimerInfoList::activateTimers (this=0x92d4234) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 0xb5cdf4e0 in timerSourceDispatch (source=0x92d4200) at kernel/qeventdispatcher_glib.cpp:164
#27 0xb4d86b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0xb4d8a0eb in ?? () from /usr/lib/libglib-2.0.so.0
#29 0xb4d8a268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0xb5cdf438 in QEventDispatcherGlib::processEvents (this=0x92b0238, flags={i = -1074242456}) at kernel/qeventdispatcher_glib.cpp:323
#31 0xb6226365 in QGuiEventDispatcherGlib::processEvents (this=0x92b0238, flags={i = -1074242408}) at kernel/qguieventdispatcher_glib.cpp:202
#32 0xb5cb206a in QEventLoop::processEvents (this=0xbff85d10, flags={i = -1074242344}) at kernel/qeventloop.cpp:149
#33 0xb5cb24aa in QEventLoop::exec (this=0xbff85d10, flags={i = -1074242280}) at kernel/qeventloop.cpp:200
#34 0xb5cb4959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#35 0xb6184d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#36 0x0804c072 in main (argc=1, argv=0xbff86094) at /build/buildd/kdepim-4.2.2/kontact/src/main.cpp:218

This new backtrace looks related to bug 190572

Well, first - it happens in exact the same way as with the previous trace; that is, when kontact has been running a while (seems shorter now than before though), it no longer properly responds and the systray icons goes invisible. Clicking on the invisible systray icon makes kontact crash which in general is very similar to how it was before.

Also, I have not noticed plasma crashing.

I think the bug is more related to Qt than Kontact/Plasma(in the case of the bug report I mentioned).

If this bug appears to be fixed, and I'm now seeing the symptoms of a different one, please do what is necessary to close this one. As long as my issue is fixed eventually, I'll be happy :)

Just to keep bugzilla clean:

- As the original reported crash is no longer there, I'm going to close this as WORKSFORME (but I'm assumming this was an "UPSTREAM" from the very beginning)

@Lars Ivar Igesund: please file a new bug report about the new crash you are getting and then tell me the bug number so I can track it.

Thanks!

I have reported bug 193134 for the new trace.

*** This bug has been marked as a duplicate of bug 193134 ***