Author Topic: Kmail crashes when asked to print  (Read 294 times)

Offline robinm

  • Full Member
  • ***
  • Posts: 143
Kmail crashes when asked to print
« on: November 19, 2010, 04:49:38 PM »
I have a strange problem with Kmail, if I try and print any emai, it brings up the print dialogue box OK but as soon as I click on print, kmail crashes. It brings up a crash handler box that says pid 7988 signal :11 segmentation fault.
I am running 2010, KDE 4.5.3 and am fully updated. Any advice on this one?
It is only affecting Kmail, the other modules with kontact appear to print fine, as does Konq and firefox.
« Last Edit: November 19, 2010, 04:59:15 PM by robinm »

Offline Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6375
  • I'm going South
Re: Kmail crashes when asked to print
« Reply #1 on: November 19, 2010, 04:59:30 PM »
I have a strange problem with Kmail, if I try and print any emai, it brings up the print dialogue box OK but as soon as I click on print, kmail crashes. It brings up a crash handler box that says pid 7988 signal :11 segmentation fault.
I am running 2010, KDE 4.5.3 and am fully updated. Any advice on this one?

You may be fully updated, but the kdepim4 packages are not. They are still lagging behind at version 4.4.5. I used kmail for over ten years, but after updating KDE to 4.5 I had to find another mail program. A bit ironic as the pim packages was one of the reasons I had stayed with KDE.
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D

Offline g2sws

  • Full Member
  • ***
  • Posts: 64
Re: Kmail crashes when asked to print
« Reply #2 on: November 20, 2010, 06:10:21 PM »
Try printing with a fixed font. I think I have been down this road.

Offline robinm

  • Full Member
  • ***
  • Posts: 143
Re: Kmail crashes when asked to print
« Reply #3 on: November 20, 2010, 06:46:00 PM »
Hey, thanks. That fixed it.