Bugzilla – Bug 334166
cups-autoconfig makes queues with hp:/... URI disabled after reboot
Last modified: 2008-02-20 07:28:13 UTC
HPLIP will not work correctly with openSUSE 10.3 HPLIP will install correctly and print properly. However after reboot, PRINT CONTROL is automatically set to STOPPED. It must be manually restarted using: kdesu hp-toolbox This is a problem MANY people are having. For example: http://suseforums.net/index.php?showtopic=39661 http://www.suseforums.net/index.php?showtopic=39395&hl=hplip Changing "lp" setting makes NO difference. Switching to USB mode from HPLIP backend is NOT an acceptable work around.
I cannot reproduce it (it works for me and my printers).
Johannes, try it using KDE 3.5 and an HP ALL-IN-ONE Printer like the 5510. It will not work for any user. Please read the forum links that I provided in the original bug report. It worked with openSUSE 10.2 but will NOT work with 10.3 without manually starting the printer after each cold boot.
Here is the manual fix: In /etc/cups-autoconfig.conf set DisablePrintersOnRemoval=no and restart cups, then the printer is not stopped the next time you start your machine. Also, to have control over Hp-toolbox in user mode, add yourself to "sys" group. (But this issue should really be automated in openSUSE 10.3 configuration.)
Please add /var/log/cups-autoconfig.log as mime type "text/plain" attachment to this bug so that we could better understand what the real cause of the problem is.
Created attachment 179526 [details] 2 lines written immediately after booting my computer This is looking as if the printer is detected twice and therefore disconnected between the first and the second detection. Might the reason be that hplip is taking over the connection?
Quoting bug#332750 comment#4 : Considering these printers/scanners are probably among the most used in Linux, I increase severity a bit :-)
*** Bug 337127 has been marked as a duplicate of this bug. ***
*** Bug 344220 has been marked as a duplicate of this bug. ***
I had this problem: my HP F4180 would become "stopped" immediately after I turned it off. It remained stopped even after turning it back on. The only way to start it again required manual intervention with cupsenable or localhost:631. Setting in /etc/cups-autoconfig.conf DisablePrintersOnRemoval=no resolved the problem. The printer does not become "stopped" after being turned off. This is a bug with a major consequence and yet it has an easy solution. The consequence is that it destroys printing for anyone not being a sysadmin. You have to know about how CUPS works. This cannot be expected of a normal user, for such a basic task as printing something. Having this bug go unfixed for >1 month is not cool.
This has been fixed, but we're gathering a group of updates that we can release together. These should be released soon.
*** Bug 350559 has been marked as a duplicate of this bug. ***