Bug 116076 - Always the 2nd print failed/stopped. I Have to switch off/on ma printer.
Summary: Always the 2nd print failed/stopped. I Have to switch off/on ma printer.
Status: CLOSED NOT A BUG
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-10 16:48 UTC by Michael O. Schäfer
Modified: 2008-12-31 19:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael O. Schäfer 2005-11-10 16:48:52 UTC 
Version:            (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
OS:                Linux

Always the 2nd printing failed/stopped. The paper will be transported only a small part at the 2nd printing and stops. The printer job is lost.

I have to switch off/on my printer between each print job to suceed.
Comment 1 Cristian Tibirna 2005-11-15 13:56:02 UTC 
What printer?
What printer driver?
What printing system?
How do you print (from an application, from the command line etc.)?
What happens if you do the second print to a PS or PDF file?

I guess your printer is broken. What happens if your print from another computer/operating system?
Comment 2 Kurt Pfeifle 2007-01-09 15:13:04 UTC 
Michael,

please respond to the questions, or state if the problem is gone for you now.

If we don't hear back from you until Feb 1, 2007, we will close this bug report.
Comment 3 Michael O. Schäfer 2007-01-09 23:03:56 UTC 
Thanks for your enquiry.
I have had resolved the problem by s.u.s.e. support: Add a certain parameter at the command line to start linux system.
(It was a canon bj210 printer since s.u.s.e. 9.1)
Comment 4 Kurt Pfeifle 2007-01-09 23:29:27 UTC 
Thanks for your early response, Michael, 

so I can close that bug now.
Comment 5 John Layt 2008-12-31 19:19:54 UTC 
Closing old Resolved status bug.