Bad default error policy causes printing issues and BIG usability issues

[Chris Murphy]

On Mon, Aug 31, 2015 at 3:37 PM, Germano Massullo
<germano.massullo at gmail.com> wrote:
> Il 06/12/2014 19:29, valent.turkovic at gmail.com ha scritto:
>> Who is responsible for user experience of Fedora desktop? To whom
>> should I point this issue to?
> https://fedoraproject.org/wiki/QA
> you could also fill a bugreport against CUPS component in
> https://bugzilla.redhat.com/
> I agree with you. I migrated some offices to Fedora and sometimes I
> receive phone calls about printing troubles. When I go personally to
> check what is wrong I often saw a big CUPS queue and the printer in pause

Like I mentioned today in the bug report, I think there's more going
on here. Issue 1 is whether non-admins can create/delete/modify state
of printers (queues);

Issue 2 is more challenging, more information is needed on the various
failures that seem to be more common on Linux than on OS X, both of
which use CUPS. I don't know if there's usually enough information for
CUPS to put a job on hold, rather than the queue. Some logic would
need to be present or you get situations where jobs vanish because the
queue isn't on hold and the printer isn't receiving data for some
reason. There was a period on OS X where something similar happened,
and new jobs printed just silently built-up or just vanished; but this
behavior was replaced quite a long time ago when at print time the
user gets an information dialog that the print queue is currently
stopped, and asks if they want to add the job to the queue rather than
print (because printing is offline). At least that way the user gets
the notification that the print queue is stopped.



-- 
Chris Murphy