Bug#490981: marked as done (KMail crashes when printing to CUPS network printer)
Your message dated Sun, 19 Apr 2009 16:34:28 +0200
with message-id <200904191634.28761.debian@pusling.com>
and subject line KMail crashes when printing to CUPS network printer
has caused the Debian Bug report #490981,
regarding KMail crashes when printing to CUPS network printer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
490981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490981
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: KMail 1.9.9 (and Kontact 1.2.9 also, which integrates KMail)
Version: 4:3.5.9-4 is how KPackage reports it; 1.9.9 is how the software reports it.
When I click [Print], KMail crashes after opening a print dialog which never actually prints. I can print in other applications (KDE and otherwise) just fine. This is with CUPS 1.3.7-7 on KDE 3.5.9. Backtrace attached below.
Debian: Lenny/Testing
Linux: 2.6.24-1-686
LibC: libc-2.7.so
Dell Dimension 3000, 2.8GHz, 768 RAM
Backtrace -- not sure if these are ever usable:
## ## START ## ##
(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5fad6c0 (LWP 2954)]
[New Thread 0xb35d0b90 (LWP 2997)]
[New Thread 0xb3dd1b90 (LWP 2996)]
[New Thread 0xb45d2b90 (LWP 2995)]
[New Thread 0xb4dd3b90 (LWP 2994)]
(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)
(no debugging symbols found)
[KCrash handler]
#6 0xb7b38266 in ?? () from /usr/lib/libkhtml.so.4
#7 0x0907d978 in ?? ()
#8 0x00000000 in ?? ()
## ## END ## ##
--- End Message ---
--- Begin Message ---
Reporter says it now works. THanks.
Closing the bug.
/Sune
--
Do you know how can I send the cache?
You neither can ever telnet on the driver, nor must debug a coaxial SMTP
controller over a pin on the hardware, this way from ICQ XP you either should
open the USB ISA software, or never have to digit on the tool for receiving a
parallel front-side bus on the jumper to a jumper.
--- End Message ---
Reply to: