Kontact crashes on printing Journal-Entries

Bug #277293 reported by Matthias Meyer
2
Affects Status Importance Assigned to Milestone
KDE PIM
Fix Released
High
kdepim (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kdepim

I wrote an entry in the Journal, saved it and clicked on the "print"-Icon in the right upper corner of the entry.
I clicked on "Print Day" and entered as Start and End-Date yesterday ( for which i wrote the entry), so to say 01.10.2008.
Then I clicked "Print" and selected Print to File: pdf.
Yet again, I clicked on Print and Kontact crashed.
This behaviour is always reproducable, no matter what the content of the Journal is, no matter which printer I choose. The only thing that seems to matter is, wether I choose "Print {Day, Week, Month..}" or "Print Incidence", "Print Incidence" works fine.

I straced Kontact and raised the crash, the interesting part:
WeaverThreadLogger: thread (ID: 1) suspended.
WeaverThreadLogger: thread (ID: 2) suspended.
WeaverThreadLogger: thread (ID: 3) suspended.
WeaverThreadLogger: thread (ID: 4) suspended.
QObject::connect: No such signal JournalEntry::configChanged()
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'CalPrinter')
*** KMail got signal 11 (Crashing)
KCrash: Application 'kontact' crashing...

I also attached the .kcrash-File.

muetze@kaeffchen:~$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04

System is up-to-date, Kontact was installed from repositories.
muetze@kaeffchen:~$ kontact --version
Qt: 3.3.8b
KDE: 3.5.9
Kontact: 1.2.9

muetze@kaeffchen:~$ apt-cache policy kontact
kontact:
  Installed: 4:3.5.9-0ubuntu3
  Candidate: 4:3.5.9-0ubuntu3
  Version table:
 *** 4:3.5.9-0ubuntu3 0
        500 http://de.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

If you need any more information, please let me know.
If this bug is fixed in a newer version, which is stable enough for everyday use, please also let me know.

Revision history for this message
Matthias Meyer (matthiasrhmeyer) wrote :
Revision history for this message
Harald Sitter (apachelogger) wrote :

Doesn't crash in KDE 4 anymore.

Changed in kdepim:
status: New → Fix Released
Revision history for this message
Matthias Meyer (matthiasrhmeyer) wrote :

Yes, it does.
I added
deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main
to my sources.list and installed KDE4 from there.

muetze@kaeffchen:~$ apt-cache policy kontact-kde4
kontact-kde4:
  Installed: 4:4.1.2-0ubuntu1~hardy1~ppa1
  Candidate: 4:4.1.2-0ubuntu1~hardy1~ppa1
  Version table:
 *** 4:4.1.2-0ubuntu1~hardy1~ppa1 0
        500 http://ppa.launchpad.net hardy/main Packages
        100 /var/lib/dpkg/status

muetze@kaeffchen:~$ kontact --version
Qt: 4.4.1
KDE: 4.1.2 (KDE 4.1.2)
Kontact: 1.3

in the next post, i will add the output of strace kontact ...

Revision history for this message
Matthias Meyer (matthiasrhmeyer) wrote :
Changed in kdepim:
status: Fix Released → New
Revision history for this message
Matthias Meyer (matthiasrhmeyer) wrote :

Still crashes in KDE4

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I was able to reproduce this crash in an updated intrepid using the steps provided in the original report. Backtrace attached

Changed in kdepim:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

This seems to be the same as or at least related to kde bug 160260. Link added

Changed in kdepim:
status: Unknown → Confirmed
Changed in kdepim:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix committed for KDE 4.2 beta2.

Changed in kdepim:
status: Confirmed → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The fix has since been released.

Changed in kdepim:
status: Fix Committed → 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.