[Bug 337665] New: Printer out of paper disables printer, needs admin to fix
https://bugzilla.novell.com/show_bug.cgi?id=337665 Summary: Printer out of paper disables printer, needs admin to fix Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix@novell.com ReportedBy: com.opensuse@bucksch.org QAContact: jsmeix@novell.com Found By: Customer Reproduction: (typical day-to-day end-user scenario) 1. Put only 2 sheets of paper in your printer, or no paper at all 2. Print a document with 3 pages 3. When printer complains, refill paper 4. Press print again and again and again Actual result: When the printer is out of paper, CUPS automatically disables the printer. You can only reactivate it by going to the CUPS admin console, entering the admin (typically root) password, and enable the printer. Expected result: - When the printer has paper again, the printing of the current job resumes and new jobs are carries out as well. - Or, worse, but far better than now: Only cancel current job, but keep printer active. Importance: This is an extremely common end user scenario. Clueless newbies being out of paper happens all the time. I just had to remote assist my father because of that, and felt embarrassed for Linux. Of course he felt no need to tell me that he once was out of paper, because that's a completely normal and unproblematic situation for him - put paper in and all is well. And he's right: It's a complete non-issue on all other systems I used in the last decade. The first time that happened, it took me *hours* to figure out what happened. I did not imagine that such a simple, temporary problem would permanently disable a printer. You need an admin to recover from "out of paper". It may make sense for a big facility where the printer has its own admin (and that admin can reconfigure CUPS all he wants), but makes no sense at all in the normal desktop situation where you have an average users who doesn't know what "print jobs" are, much less the admin interfaces or root password. The average users are the majority and rely on the default settings, so the default needs to change. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337665#c1
Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=337665#c2
Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=337665#c4
--- Comment #4 from Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=337665#c5
Ben Bucksch
https://bugzilla.novell.com/show_bug.cgi?id=337665#c6
--- Comment #6 from Ben Bucksch
https://bugzilla.novell.com/show_bug.cgi?id=337665#c7
Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=337665#c8
Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=337665#c9
Ben Bucksch
Automated "Resume" (e.g. when in your casee it might re-appear at the USB after the "paper out") is often asked for on the CUPS mailing list but the answer is always the same:
In that case, the answer is always wrong. The fact that it's often asked should show you that there's something wrong with the software, not the users. As the original description states: Please change the default policy. Average users will just hit the print button again (as you can see from my error log, which accumulated 10 print jobs, because my father kept hitting "print" when nothing happened, which is a normal reaction). Default settings should be for average desktop users, not big sites with remote printers. Big sites can easily change settings, normal users can not, they don't even know the setting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337665#c10
Ben Bucksch
https://bugzilla.novell.com/show_bug.cgi?id=337665#c11
Johannes Meixner
https://bugzilla.novell.com/show_bug.cgi?id=337665#c12
--- Comment #12 from Ben Bucksch
But we must also have the server systems in mind.
Yes. See above: "Default settings should be for average desktop users ... big sites with remote printers can easily change settings" Dedicated print servers are far more rare than desktop systems, and the former have dedicated admins who can change settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337665#c13
Kurt Pfeifle
https://bugzilla.novell.com/show_bug.cgi?id=337665#c14
--- Comment #14 from Kurt Pfeifle
Oh, there's an even simpler situation: User forgets to power on the printer before he clicks "Print". This would also result in the above situation.
Dunno about Gnome's behaviour... but in KDE, if you hit "Print", you get the "kprinter" dialog. That dialog shows a red-ish icon indicating for each queue if is disabled. (I know, that doesn't count for printing from OOo, Firefox or Thunderbird. But it is an indication of the fact that not *all* printing related things are to be solved on the CUPS level only. *Some* of the problems are rooted in the fact that the overall integration of the CUPS desktop/end-user applications aren't well integrating with each other nor with CUPS. CUPS *knows* about disabled queues, and it *tells* you if you ask it. The thing is that the GUI apps need to ask it and tell the result to the user, somehow. It can't be all solved by CUPS on its own....) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=337665
User linux.news@bucksch.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=337665#c15
--- Comment #15 from Ben Bucksch
participants (1)
-
bugzilla_noreply@novell.com