Mailinglist Archive: opensuse-bugs (9648 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=337794#c25


Johannes Meixner <jsmeix@xxxxxxxxxx> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                                        |NEEDINFO
      Info Provider|                                                
|silviu_marin-caea@xxxxxxxxxx




--- Comment #25 from Johannes Meixner <jsmeix@xxxxxxxxxx>  2007-11-29 01:15:53 
MST ---
I assume we see multiple different reasons here
why a queue becomes disabled/stopped.

In particular what is described in comment #24
(becomes disabled even if there is no active printing job)
indicates that in this case it is not the CUPS backend
which gives up with exit code 1 (CUPS_BACKEND_FAILED),
because when there is no active printing job there is
no backend running.

In this case it seems another obscure magic tool disables it
and then "cups-autoconfig" is suspicious because this tool
is known to cause bad consequences, see bug #334166.

Since openSUSE 10.3 we have the new RPM "cups-autoconfig"
which contains a utility for auto-configuring USB printers
which is triggered by udev/HAL device events.
Note that this tool neither comes from the CUPS authors
nor is the RPM a sub-package of the cups RPM.
> From the CUPS's point of view it is a "third-party" tool.
It was introduced by our "Desktop" team/department to make
printing more convenient in particular for "Desktop" users.

By default it disables/enables print queues when udev/HAL
events appear that a USB printer is disconnected/connected.
Its /etc/cups-autoconfig.conf contains by default:
--------------------------------------------------------------
[CUPS]
ConfigureNewPrinters=yes
DisablePrintersOnRemoval=yes
DefaultCUPSPolicy=relaxed
Debug=yes
--------------------------------------------------------------
It is triggered via
/usr/share/hal/fdi/policy/10osvendor/10-cups-autoconfig.fdi
which runs /usr/lib/cups-autoconfig/cups-autoconfig
which does the actual stuff, see
/usr/lib/cups-autoconfig/cups-autoconfig --help
(you must run even '--help' as root, otherwise you get errors)
Debugging output is in /var/log/cups-autoconfig.log

Perhaps in the particular case which is described in comment #24
cups-autoconfig disables the queeu but fails to re-enable it
if the printer was re-connected?

If you don't like what cups-autoconfig does (i.e. if you prefer
that you control the print queues and not whatever automatism),
uninstall the cups-autoconfig package and reboot (or restart HAL)
to make HAL aware of its changed config files, see
https://bugzilla.novell.com/show_bug.cgi?id=218393#c28

For some background information, see
http://code.google.com/p/cups-autoconfig/

Silviu Marin-Caea,
please report, if it helpy in your particular case when
cups-autoconfig is disabled or removed (to be on the safe side
do a reboot after you disabled or removed cups-autoconfig).


-- 
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.