Bug 344220 - Printer status: stopped. Does not automatically retry talking to the printer after it becomes online.
Summary: Printer status: stopped. Does not automatically retry talking to the printer...
Status: RESOLVED DUPLICATE of bug 334166
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Usability (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-27 07:49 UTC by Silviu Marin-Caea
Modified: 2007-11-29 09:39 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Silviu Marin-Caea 2007-11-27 07:49:15 UTC
This is a copy & paste of a message I wrote to the CUPS bugs forum.  It 
concerns usability.  If your opinion differs, you might move the bug to printing.

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
Comment 1 Johannes Meixner 2007-11-27 09:59:40 UTC

*** This bug has been marked as a duplicate of bug 337794 ***
Comment 2 Johannes Meixner 2007-11-29 09:39:18 UTC
See
https://bugzilla.novell.com/show_bug.cgi?id=337794#c27
Comment 3 Johannes Meixner 2007-11-29 09:39:53 UTC

*** This bug has been marked as a duplicate of bug 334166 ***