Printer status: stopped. This is murder.
This is a copy & paste of a message I wrote to the CUPS bugs forum. It concerns usability. http://www.cups.org:80/newsgroups.php?gcups.bugs+v:6146 ==== This is a case where a small bad design decision destroys all the good that CUPS does. The situation couldn't be more ordinary: a USB printer (HP F4180). If this printer is turned off when the computer is on, it will enter the stopped/paused state and remain so forever. To the average user this means exactly: LINUX PRINTING DOES NOT WORK. It's as simple and clear as that. To get it to print again, the user should give the cupsenable command or use the web interface. Do you expect mom and pop to know about "cupsenable" and "http://localhost:631"? Really. Guys, you brought linux printing forward from the middle ages. Don't leave it in the 1980s, please, we need it in the present. Whatever might be the reason cups doesn't retry printing, is it worth sacrificing usability so brutally? openSUSE 10.3, cups-1.2.12 Thank you -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
On Tuesday 27 November 2007 09:18:43 am Silviu Marin-Caea wrote:
This is a copy & paste of a message I wrote to the CUPS bugs forum. It concerns usability.
Filed as an usability bug. https://bugzilla.novell.com/show_bug.cgi?id=344220 -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Is it really necessary that every user on the computer is shown the "configure new hardware" dialog, for the same piece of hardware? Even more importantly, even if another user already configured that hardware? Take the printer example: it's enough to be set up once, by one user. The other users should be able to use it right away. Why confuse them with the "new hardware" dialog? Filed as usability bug. https://bugzilla.novell.com/show_bug.cgi?id=344221 -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Hello, On Nov 27 09:18 Silviu Marin-Caea wrote (shortened):
LINUX PRINTING DOES NOT WORK.
When you shout, you likely get ignored and first of all be always aware that you don't talk to idiots here. Furthermore read this before you post: http://en.opensuse.org/OpenSUSE_mailing_list_netiquette If you need even more instructions read them: http://www.catb.org/~esr/faqs/smart-questions.html Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
On Tuesday 27 November 2007 12:05:38 pm Johannes Meixner wrote:
Hello,
On Nov 27 09:18 Silviu Marin-Caea wrote (shortened):
LINUX PRINTING DOES NOT WORK.
When you shout, you likely get ignored and first of all be always aware that you don't talk to idiots here.
Furthermore read this before you post: http://en.opensuse.org/OpenSUSE_mailing_list_netiquette
If you need even more instructions read them: http://www.catb.org/~esr/faqs/smart-questions.html
While shouting is definitely not the best vehicle for any idea, I was tempted to do it because I feel intensely that this default is so wrong for the most of the people and it just hurts SUSE for no good reason. And I'm fresh off after wasting a couple of hours on such a trivial task: getting stuff to print. For the rest of the list: this can be resolved by replacing ErrorPolicy stop-printer with ErrorPolicy retry-job in /etc/cups/printers.conf -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
participants (3)
-
Johannes Meixner -
Silviu Marin-Caea -
Silviu Marin-Caea