I don't print much, so have no idea when this started other than I've done some package installations and some updates since. It used to work fine, and I don't remember doing anything that should have had anything to do with printing. Every time I try to print, the job goes into that print queue, and never comes out. I look in KJobViewer, and even after changing the priority to 100 and selecting "move to printer", it just sits there. I have only one printer, a PS LaserJet 4 on ethernet, the only one shown by YaST2. SeaMonkey thinks there's also a CUPS printer, which is what it defaults to. KPdf defaults to the LaserJet, but its jobs get stuck in queue too, e.g. at 223kb and 0 pages. How do I get print jobs to go directly to the only printer instead of stuck in queue? OS/2 prints to this printer with no delay. -- "Respect everyone." I Peter 2:17 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Felix Miata wrote:
I don't print much, so have no idea when this started other than I've done some package installations and some updates since. It used to work fine, and I don't remember doing anything that should have had anything to do with printing.
Every time I try to print, the job goes into that print queue, and never comes out. I look in KJobViewer, and even after changing the priority to 100 and selecting "move to printer", it just sits there. I have only one printer, a PS LaserJet 4 on ethernet, the only one shown by YaST2. SeaMonkey thinks there's also a CUPS printer, which is what it defaults to. KPdf defaults to the LaserJet, but its jobs get stuck in queue too, e.g. at 223kb and 0 pages. How do I get print jobs to go directly to the only printer instead of stuck in queue? OS/2 prints to this printer with no delay.
What is lpstat reporting? I had a similar problem and found that jobs were going to a queue which for some reason had become disabled. Use lpadmin to re-enable the queue if this is the case. (I dont trust GUI components to report accurately on printing status). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGgiLaasN0sSnLmgIRAsX8AKCTksbzLDcOREk9iAPdm5V/UuKh1wCggQdm uS7XC6a9HMPbuvLRpT/EkqY= =VACg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007/06/27 09:42 (GMT+0100) G T Smith apparently typed:
Felix Miata wrote:
I don't print much, so have no idea when this started other than I've done some package installations and some updates since. It used to work fine, and I don't remember doing anything that should have had anything to do with printing.
Every time I try to print, the job goes into that print queue, and never comes out. I look in KJobViewer, and even after changing the priority to 100 and selecting "move to printer", it just sits there. I have only one printer, a PS LaserJet 4 on ethernet, the only one shown by YaST2. SeaMonkey thinks there's also a CUPS printer, which is what it defaults to. KPdf defaults to the LaserJet, but its jobs get stuck in queue too, e.g. at 223kb and 0 pages. How do I get print jobs to go directly to the only printer instead of stuck in queue? OS/2 prints to this printer with no delay.
What is lpstat reporting? I had a similar problem and found that jobs were going to a queue which for some reason had become disabled. Use lpadmin to re-enable the queue if this is the case.
That was it. Thanks to all who replied. # lpstat -p printer normal disabled since Thu Jun 7 23:25:22 2007 - /usr/lib/cups/backend/socket failed # lpadmin -p normal -E # lpstat -p printer normal now printing normal-42. enabled since Wed Jun 27 08:15:51 2007 Connected to 192.168.0.4... -- "Respect everyone." I Peter 2:17 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 27 June 2007 12:14, Felix Miata wrote:
I don't print much, so have no idea when this started other than I've done some package installations and some updates since. It used to work fine, and I don't remember doing anything that should have had anything to do with printing.
Every time I try to print, the job goes into that print queue, and never comes out. I look in KJobViewer, and even after changing the priority to 100 and selecting "move to printer", it just sits there. I have only one printer, a PS LaserJet 4 on ethernet, the only one shown by YaST2. SeaMonkey thinks there's also a CUPS printer, which is what it defaults to. KPdf defaults to the LaserJet, but its jobs get stuck in queue too, e.g. at 223kb and 0 pages. How do I get print jobs to go directly to the only printer instead of stuck in queue? OS/2 prints to this printer with no delay. --
Hello Felix, Sometimes if for some reason the printing fail such as you forget to turn on the printer first, etc, Suse will "disable" the printer. There are 2 ways to fix it. Delete the printer from Yast and add it again, or "Re-enable" the printer using Cups (quicker way). To enable: 1. lppasswd -a root 2. Open Firefox to http://localhost:631 3. Klik on start button in Cups's GUI. 4. Or from CLI: cupsenable printername HTH, -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 4:03pm up 8:29, 2.6.18.2-34-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
On Wed June 27 2007 03:04, Fajar Priyanto wrote:
Hello Felix, Sometimes if for some reason the printing fail such as you forget to turn on the printer first, etc, Suse will "disable" the printer. There are 2 ways to fix it. Delete the printer from Yast and add it again, or "Re-enable" the printer using Cups (quicker way).
To enable: 1. lppasswd -a root 2. Open Firefox to http://localhost:631 3. Klik on start button in Cups's GUI. 4. Or from CLI: cupsenable printername
You can do the same with KDE Print Manager ((KMenu / Utilities / Printing / Printing Manager). Click on Administrator Mode and enter the root password. Right-click at a printer to see a tonne of options, including Enable, Restart (or the opposite toggle). The icon will also tell you with an X if a printer queue is stopped. -- Carlos FL Who is General Failure, and why is he reading my disk? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Jun 27 16:04 Fajar Priyanto wrote (shortened):
Sometimes if for some reason the printing fail such as you forget to turn on the printer first, etc, Suse will "disable" the printer.
No, no, no, it is not "Suse" which disables the queue. It is CUPS. It is done intentionally to avoid loosing print jobs. It is described for example in http://en.opensuse.org/SDB:CUPS_in_a_Nutshell see "The Backends". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 27 June 2007 03:04, Fajar Priyanto wrote:
Sometimes if for some reason the printing fail such as you forget to turn on the printer first, etc, Suse will "disable" the printer.
I would like to add that if you add the line: ErrorPolicy retry-job to /etc/cups/printers.conf and: JobRetryInterval 30 (or such) to /etc/cups/cupsd.conf many nuisance stops/restarts will be avoided. reference: http://localhost:631/help/ref-printers-conf.html?TOPIC=References&QUERY=#ErrorPolicy ErrorPolicy Examples <Printer name> ... ErrorPolicy cancel-job </Printer> Description The ErrorPolicy directive defines the policy that is used when a backend is unable to send a print job to the printer. The lpadmin(8) command sets the current error policy: /usr/sbin/lpadmin -p printername -o printer-error-policy=stop-printer The following values are supported: * cancel-job - Cancel the job and proceed with the next job in the queue * retry-job - Retry the job after waiting for N seconds; the cupsd.conf JobRetryInterval directive controls the value of N * stop-printer - Stop the printer and keep the job for future printing; this is the default value This directive must appear inside a Printer or DefaultPrinter section. HTH, -- Jim Barnes -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. -Lazarus Long -- Linux 2.6.15-28-386 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata wrote:
I don't print much, so have no idea when this started other than I've done some package installations and some updates since. It used to work fine, and I don't remember doing anything that should have had anything to do with printing.
Every time I try to print, the job goes into that print queue, and never comes out. I look in KJobViewer, and even after changing the priority to 100 and selecting "move to printer", it just sits there. I have only one printer, a PS LaserJet 4 on ethernet, the only one shown by YaST2. SeaMonkey thinks there's also a CUPS printer, which is what it defaults to. KPdf defaults to the LaserJet, but its jobs get stuck in queue too, e.g. at 223kb and 0 pages. How do I get print jobs to go directly to the only printer instead of stuck in queue? OS/2 prints to this printer with no delay.
I had one particular network printer at the office that was simply not printing from my 10.2 system, and the desktop print monitor kjobviewer showed nothing amiss - however when I went into the kde control center and drilled down on the printer, it was shown to be in a disabled state. I'm not sure how or when that happened, probably when the printer was off line. I was able to put it back into the enabled state from there, and printing has been fine. That may or may not be your problem, just a sanity check Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Carlos F Lange -
Fajar Priyanto -
Felix Miata -
G T Smith -
jim barnes -
Johannes Meixner -
Sloan