Bug 103898 - When printing pdf documents the printer seems to become unresponsive.
Summary: When printing pdf documents the printer seems to become unresponsive.
Status: CLOSED NOT A BUG
Alias: None
Product: kdeprint
Classification: Applications
Component: kjobviewer (show other bugs)
Version: 0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-14 18:40 UTC by Robert R. Morris
Modified: 2008-12-31 18:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert R. Morris 2005-04-14 18:40:00 UTC
Version:           0.1 (using KDE 3.3.0, SuSE)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-24.13-default

I am using an HP 930C presently,  Most of the time the printer works just fine.   But on occasions when trying to print pdf documents the printer becomes totally unresponsive even though when I view the Printer Queue I clearly have jobs queued up to print.  Once this occurs, I can only resume printing by rebooting the host machine.   This seems to restore the printer connection.  I am in the process at this time trying to repeat this entire cycle to see whether I can repeat the problem in a reliable fashion.
Comment 1 Michael Goffioul 2005-04-15 08:46:46 UTC
Can you specify which physical device becomes unresponsive: the computer or the printer? Does it also happen when you try to print your PDF with "lpr" utility? I you print from a PDF viewer app, does it happen with any such app (kpdf, acroread using "kprinter" as print command)?

Michael.
Comment 2 Cristian Tibirna 2005-09-27 07:27:35 UTC
Please answer to comment #1. Also, please specify how is the printer connected to the computer (Parallel, USB, TCP, other?)
Comment 3 Chris Howells 2006-05-30 02:33:05 UTC
no answer to question-> closing

If you still have the problem and wish to answer please re-open.
Comment 4 John Layt 2008-12-31 18:29:19 UTC
Closing old Resolved status bug.