Bug 146170 - Kontact crashes when clicking on item of summary component
Summary: Kontact crashes when clicking on item of summary component
Status: RESOLVED DUPLICATE of bug 129257
Alias: None
Product: kontact
Classification: Applications
Component: summary (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-30 19:44 UTC by Elias Probst
Modified: 2007-06-15 15:12 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 Elias Probst 2007-05-30 19:44:27 UTC
Version:           Kontact 1.2.5 (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc-Version 4.1.2 (Gentoo 4.1.2) CFLAGS="-ggdb -O2 -march=nocona -msse3 -pipe -fomit-frame-pointer -fvar-tracking"
OS:                Linux

This problem was already existent in 3.5.6 (don't know whether it happened in 3.5.5 and before too..).

How to reproduce the crash:

1. Open Kontact (Summary is default component)
2. Click on one of the items (used appointment for this backtrace) listed in the summary
3. Kontact crashes

This doesn't happen when the used component (KMail/Korganizer...) was already started.

It seems, the summary component doesn't check whether the used component was already loaded or not.

If needed, I could provide a valgrind memcheck logfile.

Regards, Elias P.

Backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242671440 (LWP 3308)]
[New Thread -1286325360 (LWP 3312)]
[New Thread -1277932656 (LWP 3311)]
[New Thread -1269539952 (LWP 3310)]
[New Thread -1261147248 (LWP 3309)]
[KCrash handler]
#6  0x6369682f in ?? ()
#7  0xb674afe5 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#8  0xb674baf9 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#9  0xb6dbb9c8 in KApplication::notify (this=0xbffe83c8, receiver=0x8e4f790, 
    event=0xbffe7cc0) at kapplication.cpp:550
#10 0xb67dc834 in QWidget::setFocus () from /usr/qt/3/lib/libqt-mt.so.3
#11 0xb674c440 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb6dbb9c8 in KApplication::notify (this=0xbffe83c8, receiver=0x8e4f790, 
    event=0xbffe8024) at kapplication.cpp:550
#13 0xb66eeca0 in QETWidget::translateMouseEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb66ee5e5 in QApplication::x11ProcessEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#15 0xb66fda5a in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb67609ad in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb6760852 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb674ab0b in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#19 0x08058f72 in main (argc=134632328, argv=0xbffe85d4) at main.cpp:163
#20 0xb5eff824 in __libc_start_main () from /lib/libc.so.6
#21 0x08058651 in _start ()
Comment 1 Bram Schoenmakers 2007-05-31 09:47:12 UTC
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports describes how to get the most out of it.

Although, could you be a bit more specific please about how you proceed. I did some clicking, but couldn't make it crash.
Comment 2 Thomas McGuire 2007-06-15 15:12:32 UTC

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