Hello, On Jul 30 09:35 James D. Parra wrote (shortened):
On a similar topic, if I have jobs stuck in the print queue, how can I force the jobs to be printed
I cannot guess why they are "stuck in the print queue" in your particular case. Perhaps http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends" which is a usual reason might help in your particular case too: ----------------------------------------------------------------- If the data transmission to the recipient fails (usually after several attempts by the backend), the backend will report an error to the print system (more precisely, to cupsd). The backend decides if and how many attempts make sense before it reports that the data transmission has failed. As further attempts would be futile, cupsd disables printing on the affected queue. After eliminating the cause of the problem, the system administrator must reenable printing with /usr/bin/enable (for CUPS 1.1 - i.e. up to Suse Linux 10.1) or with cupsenable (since CUPS 1.2 - i.e. since openSUSE 10.2). -----------------------------------------------------------------
or send the queued jobs to another printer?
Use /usr/sbin/lpmove as root, see "man lpmove". As normal user it might help to run it as /usr/sbin/lpmove -U root oldprinter-123 newprinter Regarding "-U root" compare "man cancel": ----------------------------------------------------------------- Administrators wishing to prevent unauthorized cancellation of jobs via the -u option should require authentication for Cancel-Jobs operations in cupsd.conf(5). ----------------------------------------------------------------- and note in particular "CUPS-Move-Job" at http://www.cups.org/documentation.php/doc-1.3/policies.html
When testing remote SMB access from Yast the printer is accessible, however the jobs are still stuck in the queue.
Have a look at http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share how you may debug it further and you may also have a look at https://bugzilla.novell.com/show_bug.cgi?id=503772#c5 and regarding the special case of percent-encoding which is required for special characters in the DeviceURI see the "By the way" section in https://bugzilla.novell.com/show_bug.cgi?id=512549#c1 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