Bug 202009 - Kontact crashed when marking a task as completed in the overview
Summary: Kontact crashed when marking a task as completed in the overview
Status: RESOLVED FIXED
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:
Depends on:
Blocks:
 
Reported: 2009-07-30 16:17 UTC by Dominik Steenken
Modified: 2009-11-16 15:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
complete backtrace (2.20 KB, text/plain)
2009-07-31 17:17 UTC, Dominik Steenken
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Steenken 2009-07-30 16:17:55 UTC
Application that crashed: kontact
Version of the application: 4.3.0 rc3
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I created a task, and then, after a while i right-clicked on the status display (0%) in the overview section and then clicked on 100%, since i was done. kontact crashed.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f18d86ca106 in QApplication::notify () from /usr/lib/libQtGui.so.4
#6  0x00007f18d9af971b in KApplication::notify () from /usr/lib/libkdeui.so.5
#7  0x00007f18d7b0775c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#8  0x00007f18d86c9328 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#9  0x00007f18d8732e19 in ?? () from /usr/lib/libQtGui.so.4
#10 0x00007f18d8731a88 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#11 0x00007f18d875a464 in ?? () from /usr/lib/libQtGui.so.4
#12 0x00007f18d123d20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007f18d12408e0 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007f18d1240a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007f18d7b30e6f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#16 0x00007f18d8759bef in ?? () from /usr/lib/libQtGui.so.4
#17 0x00007f18d7b06002 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#18 0x00007f18d7b063cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#19 0x00007f18d7b08694 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#20 0x0000000000404945 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-31 15:14:18 UTC
The backtrace is a bit generic. Looks like it could be a Qt4.5 bug.
Can you reproduce the crash at will all the times? 
Thanks
Comment 2 Dominik Steenken 2009-07-31 16:10:14 UTC
yes, this happens every time i try to change the completion status of a task in the overview section.
Comment 3 Dario Andres 2009-07-31 16:18:13 UTC
Can you install the "kdepim-dbg" and "libqt4-dbg" packages to get a complete backtrace? Thanks
Comment 4 Dominik Steenken 2009-07-31 17:17:02 UTC
Created attachment 35758 [details]
complete backtrace

here is the complete backtrace. Oddly, this actually only seems to happen when you try to change the completion status and the completion status was at 0% before
Comment 5 Dario Andres 2009-07-31 17:31:25 UTC
Pasting backtrace inline:
----

Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f3a80ae2106 in QApplication::notify (this=<value optimized out>, receiver=0x4952580, e=0x7fff8da62d60) at kernel/qapplication.cpp:3792
#6  0x00007f3a81f1171b in KApplication::notify (this=0x7fff8da63c70, receiver=0x4952580, event=0x7fff8da62d60) at /build/buildd/kde4libs-4.2.98a/kdeui/kernel/kapplication.cpp:302
#7  0x00007f3a7ff1f75c in QCoreApplication::notifyInternal (this=0x7fff8da63c70, receiver=0x4952580, event=0x7fff8da62d60) at kernel/qcoreapplication.cpp:602
#8  0x00007f3a80ae1328 in QApplicationPrivate::sendMouseEvent (receiver=0x4952580, event=0x7fff8da62d60, alienWidget=0x4952580, nativeWidget=0x22ec260, buttonDown=<value optimized out>, 
    lastMouseReceiver=@0x7f3a8153deb0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#9  0x00007f3a80b4ae19 in QETWidget::translateMouseEvent (this=0x22ec260, event=<value optimized out>) at kernel/qapplication_x11.cpp:4425
#10 0x00007f3a80b49a88 in QApplication::x11ProcessEvent (this=0x7fff8da63c70, event=0x7fff8da638a0) at kernel/qapplication_x11.cpp:3543
#11 0x00007f3a80b72464 in x11EventSourceDispatch (s=0xbaf800, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#12 0x00007f3a7965520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007f3a796588e0 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007f3a79658a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007f3a7ff48e6f in QEventDispatcherGlib::processEvents (this=0xb850a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#16 0x00007f3a80b71bef in QGuiEventDispatcherGlib::processEvents (this=0xb858a8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#17 0x00007f3a7ff1e002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -1918485616}) at kernel/qeventloop.cpp:149
#18 0x00007f3a7ff1e3cd in QEventLoop::exec (this=0x7fff8da63bd0, flags={i = -1918485536}) at kernel/qeventloop.cpp:200
#19 0x00007f3a7ff20694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#20 0x0000000000404945 in main (argc=1, argv=0x7fff8da64358) at /build/buildd/kdepim-4.2.98/kontact/src/main.cpp:218
Comment 6 Christophe Marin 2009-11-16 15:11:49 UTC
There's still nothing related to kontact or korganizer. Could you reproduce this crash with a recent KDE version (4.3.2 or 4.3.3) ?
Comment 7 Dominik Steenken 2009-11-16 15:22:10 UTC
Nope, it seems to work with 4.3.2