From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Description of problem: I updated to system-config-printer-0.6.116.1-1.i386.rpm from system-config-printer-0.6.116.1 and 1. After editing a printer and trying to "apply," Printtool comes up with the message "Failed to write queues" 2. Cups is stopped and cannot be restarted: #/etc/init.d/cups start Starting cups: cupsd: Child exited with status 98! [FAILED] Reverting to system-config-printer-0.6.116.1.i386.rpm fixes the problem. I am running Kernel 2.6.10-1.741_FC3. Version-Release number of selected component (if applicable): system-config-printer-0.6.116.1-1.i386.rpm How reproducible: Always Steps to Reproduce: 1. rpm -Uvh system-config-printer-0.6.116.1-1.i386.rpm 2. system-config-printer 3. Edit a queue and try to "Apply" Actual Results: "Failed to write queues" cups is dead The messages log lists, as expected: Feb 1 09:20:44 hardy cups: cupsd shutdown succeeded Feb 1 09:20:47 hardy cupsd: cupsd: Child exited with status 98! Feb 1 09:20:47 hardy cups: cupsd startup failed Feb 1 09:23:09 hardy cups: cupsd shutdown failed Feb 1 09:23:10 hardy cups: cupsd shutdown failed Feb 1 09:23:11 hardy cupsd: cupsd: Child exited with status 98! Feb 1 09:23:11 hardy cups: cupsd startup failed Feb 1 09:23:40 hardy cupsd: cupsd: Child exited with status 98! Feb 1 09:23:40 hardy cups: cupsd startup failed Feb 1 09:25:21 hardy cups: cupsd shutdown failed Feb 1 09:25:22 hardy cups: cupsd shutdown failed Feb 1 09:25:23 hardy cupsd: cupsd: Child exited with status 98! Feb 1 09:25:23 hardy cups: cupsd startup failed Expected Results: cups to work with the new settings Additional info: rpm --force -Uvh system-config-printer-0.6.116-1.i386.rpm system-config-printer-gui-0.6.116-1.i386.rpm brings things back to normal!
Forgot to mention: the cups version is cups-1.1.22-0.rc1.8.4
Please attach the output of 'printconf-tui --Xexport', making sure to replace any passwords for remote queues with '***'. Thanks.
I will need to reinstall the buggy version for this, when I have some free time.
Created attachment 110553 [details] The output of printconf-tui --Xexport for the buggy version
Created attachment 110554 [details] Diffs between ther outpu of buggy version, and the previous version
Thanks. Now can you please set the LogLevel in /etc/cups/cupsd.conf to 'debug2', and then cause the error to happen using system-config-printer. Then attach the relevant bit of /var/log/cups/error_log (if you truncate it first with '>/var/log/cups/error_log' on the shell command line it will only contain the relevant bits). Thanks.
Created attachment 110559 [details] tail of /var/locgcups/error_log
Please attach /etc/cups/cupsd.conf.
Created attachment 110560 [details] cupsd.conf modified with debug2
I tried to replace cupsd.con (as sent) with cupsd.conf.rpmnew -- same result.
I just reinstalled the working system-config-printer and noticed that the permissions on /etc/cups/cupsd.conf differ: In the nonworking version: -rw------- 1 lp sys 21429 Feb 2 10:08 cupsd.conf In the working version -rw-r----- 1 root sys 20799 Feb 2 10:11 cupsd.conf Could this be the cause of the failure?
No, it's not to do with that. The bug is actually present in the original system-config-printer as well, but luck prevents it from showing up. Thank you very much for reporting this.
I am surprised no one else reported this. I had a hard time (trying various cupsd.conf files) to get a cups version which works!
It's quite a specific configuration that causes it: you have to have one printer shared by "eth0", and another shared by a particular IP address available via that interface -- and they have to be processed in a particular order. What changed in the update was the order that some of the queues are processed. An update to fix this is coming soon, but I need to investigate another bug report first.
Also affects RHEL3.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2006-0073.html