Hi, currently default error policy for printers in Fedora is "Stop printer" on any error which is a really bad default. I have run across this issue LOTS of times with regular Fedora desktop users who don't get why has their printer stopped working, there is no UI queue to warn users, there is no easy way to "Start printer" with one click after it has been stopped. It is just a big mess.
Even worse, previous versions of Gnome control panel (if I remember correctly) had option to change default error policy, now that option is removed and you can get to it only by installing system-config-printers tool, something regular users have no idea about even exists, and it is not installed by default.
There are too many examples which are simple user errors but result in priner going offline (stopped) and this is really bad, because after any small error users can't print any more.
For example: user trying to print while he/she is not at home so his/hers printer is not available, user trying to print but has forgot to connect usb priner cable, user trying to print but haven't turned it on, user printing to wifi printer but while connected to different wifi network...
Any of these actions is simple uses error but results in permanently disabling of priner (Stops printer) and users can't print even when they resolve issue that was stopping them from accessing the printer.
Now Fedora is what is stopping them from printing.
Who is responsible for user experience of Fedora desktop? To whom should I point this issue to?
On 12/06/2014 10:29 AM, valent.turkovic@gmail.com wrote:
Any of these actions is simple uses error but results in permanently disabling of priner (Stops printer) and users can't print even when they resolve issue that was stopping them from accessing the printer.
Yes, I've run into this a lot. The worst part of it is that if the user isn't an admin, they can't fix the printer even if they knew where to find the setting.
On Sun, Dec 7, 2014 at 6:56 AM, Samuel Sieb samuel@sieb.net wrote:
On 12/06/2014 10:29 AM, valent.turkovic@gmail.com wrote:
Any of these actions is simple uses error but results in permanently disabling of priner (Stops printer) and users can't print even when they resolve issue that was stopping them from accessing the printer.
Yes, I've run into this a lot. The worst part of it is that if the user
isn't an admin, they can't fix the printer even if they knew where to find the setting.
Jup, same thing here, I have admin level account and still need to "unlock" printer panel in order to turn printer back on :( Let's continue discussion here: https://bugzilla.redhat.com/show_bug.cgi?id=1171418
On 15 December 2014 at 10:03, valent.turkovic@gmail.com < valent.turkovic@gmail.com> wrote:
On Sun, Dec 7, 2014 at 6:56 AM, Samuel Sieb samuel@sieb.net wrote:
On 12/06/2014 10:29 AM, valent.turkovic@gmail.com wrote:
Any of these actions is simple uses error but results in permanently disabling of priner (Stops printer) and users can't print even when they resolve issue that was stopping them from accessing the printer.
Yes, I've run into this a lot. The worst part of it is that if the user
isn't an admin, they can't fix the printer even if they knew where to find the setting.
Jup, same thing here, I have admin level account and still need to "unlock" printer panel in order to turn printer back on :( Let's continue discussion here: https://bugzilla.redhat.com/show_bug.cgi?id=1171418
Hi dear Fedora developers, I'm again being really frustrated by this default policy on Fedora 22. Still nothing changed.
I swear Windows 95 had better printing usability than latest Fedora. Will this agony ever end? :)
Il 06/12/2014 19:29, valent.turkovic@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
On Mon, Aug 31, 2015 at 3:37 PM, Germano Massullo germano.massullo@gmail.com wrote:
Il 06/12/2014 19:29, valent.turkovic@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.
devel@lists.stg.fedoraproject.org