Version: Unbekannt (using KDE 3.1.4) Installed from: (testing/unstable) Compiler: gcc version 3.3.2 20030908 (Debian prerelease) OS: Linux (i686) release 2.4.21-5-k7 When trying to print a scanned image (a4, 300dpi, color, jpeg, scanned with kooka) to a pdf file, kprinter crashes. Perhaps an automatic downscaling could solve this.
Can you provide a backtrace? One with debugging symbols would be preferred.
Does this problem still exist?
Am Donnerstag, 26. Februar 2004 08:39 schrieben Sie: > ------- Additional Comments From goffioul imec be 2004-02-26 08:39 ------- > Does this problem still exist? No. Now it produces a 0 Byte PDF, but does not crash anymore. I tried this with KDE 3.1.5 (3.2 is still not in Debian Sid). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAPeLNTCeCnCU9zTsRAhS9AKDrTHykTzuDORJQCIBrAmPibBL2hQCfQTEu VDdhIsFyCs34v8QrbdoRl/E= =dTc/ -----END PGP SIGNATURE-----
Basically, when printing to a PDF file, kdeprint does almost nothing: - the app generates PS print data - kdeprint calls "gs" to convert it to PDF - result is stored at wanted location What you can try is to print your scanned image from the app you're using to a PS file. Then try to convert this file to PDF using the command-line tool "ps2pdf" (this emulates what kdeprint is doing). Do you get the same result (0 byte file)?
Am Donnerstag, 26. Februar 2004 13:52 schrieben Sie: > nothing: - the app generates PS print data > - kdeprint calls "gs" to convert it to PDF > - result is stored at wanted location > What you can try is to print your scanned image from the app you're using > to a PS file. Then try to convert this file to PDF using the command-line > tool "ps2pdf" (this emulates what kdeprint is doing). Do you get the same > result (0 byte file)? Sorry, I didn't look carefully enough. The prinitng dialog was already closed, the file had a size of 0 byte. Now I checked with "lsof". It showed that the file was still open. And just 15 minutes later, the pdf was completely written. I think the problem is solved, just the user interaction is a little strange :) Thanks, Stefan Schwetschke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAPf+HTCeCnCU9zTsRAsBCAJ9fIQ4O3+5KQB5WLPjbwCYE0a2SswCfQCD6 +IqsaiR+IUF/DVW41XLsTas= =fMHn -----END PGP SIGNATURE-----
That's because the job viewer doesn't handle pseudo-printers (like printing to PDF), so there's no possibility for a user to see the print job status. Usually, this is not a problem because execution is very quick and the user doesn't notice anything. In your case, the PDF conversion is *very* long, but you don't have any mean to know the PDF conversion is still ongoing (except with "ps"). Let's turn this into a wishlist.
Closing old Resolved status bug.