kontact crashes when the link to to-do is clicked in summary view after starting

Bug #92229 reported by falconblue
8
Affects Status Importance Assigned to Milestone
KDE PIM
Fix Released
High
kdepim (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47757948029168 (LWP 5925)]
[New Thread 1107310912 (LWP 5929)]
[New Thread 1098918208 (LWP 5928)]
[New Thread 1090525504 (LWP 5927)]
[New Thread 1082132800 (LWP 5926)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x0000000000000000 in ?? ()
#6 0x00002b6f7c6abab6 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#7 0x00002b6f7c6ae32a in QApplication::notify () from /usr/lib/libqt-mt.so.3
#8 0x00002b6f7bdbe7a8 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#9 0x00002b6f7c63dea0 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#10 0x00002b6f7c74911b in QWidget::setFocus () from /usr/lib/libqt-mt.so.3
#11 0x00002b6f7c6adb33 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#12 0x00002b6f7bdbe7a8 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#13 0x00002b6f7c63df12 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b6f7c63cb1c in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002b6f7c63ace8 in QApplication::x11ProcessEvent ()
   from /usr/lib/libqt-mt.so.3
#16 0x00002b6f7c651746 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#17 0x00002b6f7c6c4feb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#18 0x00002b6f7c6c4df3 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#19 0x00002b6f7c6ad57c in QApplication::exec () from /usr/lib/libqt-mt.so.3
#20 0x000000000041dc12 in ?? ()
#21 0x00002b6f7b8aa8e4 in __libc_start_main () from /lib/libc.so.6
#22 0x0000000000415a19 in ?? ()
#23 0x00007fff30f26ec8 in ?? ()
#24 0x0000000000000000 in ?? ()

ProblemType: Bug
Architecture: amd64
Date: Wed Mar 14 21:45:01 2007
DistroRelease: Ubuntu 7.04
Uname: Linux foon-desktop 2.6.20-10-generic #2 SMP Sun Mar 11 19:49:03 UTC 2007 x86_64 GNU/Linux

Revision history for this message
Rich Johnson (nixternal) wrote :

I am unable to confirm this. I have about 25 links in Summary view right now to mail boxes and I can click each one.

Feisty up-to-date

Changed in kdepim:
status: Unconfirmed → Needs Info
Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

I can confirm and reproduce this bug!

The backtrace given by the kde-crashmanager is almost the same as the one above. It is attached.

It is important that you start Kontact with the summary as first view. And the first thing you should do is clicking on a link (it is not important if it is a link to kmail or korganizer) in the summary view. Than Kontact crashes every time.

When you first change the view to korganizer or kmail and then go back to the summary view the links behave like expected and Kontact doesn`t crash.

Changed in kdepim:
status: Needs Info → Confirmed
Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

Changing my last post.

It IS a difference between clicking on tasks or e-mails/mailboxes in the summary view.
When you click on a task, just after Kontact started, it crashes every time.
When you click on a mailbox, it crashes just about one out of twenty times.

Revision history for this message
Rich Johnson (nixternal) wrote :
Download full text (3.6 KiB)

Emanuel, I can confirm this using your directions. Thanks for the clarification.
Kubuntu 7.04
KDE 3.5.7

-----------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243257136 (LWP 7973)]
[New Thread -1287668848 (LWP 7981)]
[New Thread -1279276144 (LWP 7980)]
[New Thread -1270883440 (LWP 7979)]
[New Thread -1262490736 (LWP 7978)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xffffffc4 in ?? ()
#7 0xb6eeca60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#8 0xb6eef42a in QApplication::notify () from /usr/lib/libqt-mt.so.3
#9 0xb7628c32 in KApplication::notify () from /usr/lib/libkdecore.so.4
#10 0xb6e7f1e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#11 0xb6f90e27 in QWidget::setFocus () from /usr/lib/libqt-mt.so.3
#12 0xb6eeeb28 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#13 0xb7628c32 in KApplication::notify () from /usr/lib/libkdecore.so.4
#14 0xb6e7f25d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#15 0xb6e7dec2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#16 0xb6e7bfac in QAppli...

Read more...

Changed in kdepim:
status: Unknown → Confirmed
Revision history for this message
David Miller (djmdave) wrote :

I can also confirm this. In my summary view i've got local and remote calendar appointments and some todos and inbox folder, all of which cause kontact to crash when either right-clicking or left-clicking them.

I can also confirm that switching to one of kontacts components such as mail or calendar, and then switching back to the summary view, allows you to left/right click on items without kontact crashing.

I'm download/installing kdepim-dbg at the moment, and will provide as much information as i can.

Im using kubuntu gutsy with kontact at version 1.2.4 (enterprise 0.20070907.709405).

Revision history for this message
David Miller (djmdave) wrote :

Well, kdepim-dbg install quicker than i thought :)

Attached is the backtrace after i loaded kontact and left-clicked on an upcoming appointment in summary view.

Revision history for this message
David Miller (djmdave) wrote :

bug appears to be fixed.

kontact no longer crashes when a summary-view item is clicked.

using kontact version: 4:3.5.7enterprise20070926-0ubuntu2

Revision history for this message
AllesMeins (spam-startrekarchiv) wrote :

I'm afraid I can't confirm the fix. I'm using the same version on gutsy amd64 and kontact still crashes, when performing the steps mentioned above. KDE Crash Report is attached.

Changed in kdepim:
status: Confirmed → Fix Released
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

There has been no activity in this report for almost a year. The upstream report is marked fixed. Is this still an issue for anyone or can this be closed now?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Assuming fixed. Please reopen if this is still an issue with KDE 4.2 or later.

Changed in kdepim:
status: Confirmed → Fix Released
Changed in kdepim:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.