[Bug 553147] New: Configuring printer in Yast2 fails to start CUPs server daemon
http://bugzilla.novell.com/show_bug.cgi?id=553147 Summary: Configuring printer in Yast2 fails to start CUPs server daemon Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marc@marcchamberlin.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.15) Gecko/2009102100 SUSE/3.0.15-0.1 Firefox/3.0.15 I have gone through the process of configuring a printer, and was at a loss as to why it was always failing. Apparently upon completion, YaST's printer configuration tool fails to start up the CUPS server daemon. I discovered this by doing an rccups status immediately after using the YaST printer setup tool and discovered the CUPs daemon was NOT running. I then immediately started the cups server with rccups start and it would start running. This shows that while the printer configuration process works fine, and does not generate any configuration errors, that the CUPs daemon was not started properly, nor apparently is the CUPS daemon even tested to insure that it is up and running by YaST's printer setup tool. THIS IS A SERIOUS FLAW! The user cannot use the CUP's web setup if the CUP's server is not up an running. The only other GUI that is capable of guiding a user through the process of setting up a printer is via YaST2. And if YaST2 fails then the user will be left in the dark without any understanding of why a printer is not working! I KNOW! TOOK ME HOURS AND HOURS TO TRACK THIS DOWN! Reproducible: Always Steps to Reproduce: 1. Set up a cupsd.conf with an error that prevents the CUPS daemon from running 2. Use YaST2 to configure a printer (an corrects the previous error) 3. Do an rccups status to determine if CUPs server is running. Actual Results: CUPs server is not started nor tested properly to determine if it was successfully configured and started. Expected Results: I expect the CUPs server to be started automatically, and tested, upon completion of the printer setup in YaST2 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553147
zhu rensheng
http://bugzilla.novell.com/show_bug.cgi?id=553147
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553147#c1
Johannes Meixner
http://bugzilla.novell.com/show_bug.cgi?id=553147
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553147#c2
Johannes Meixner
http://bugzilla.novell.com/show_bug.cgi?id=553147
User marc@marcchamberlin.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553147#c3
--- Comment #3 from Marc Chamberlin
Do you really mean: "Steps to Reproduce: 1. Set up a cupsd.conf with an error that prevents the CUPS daemon from running"?
If you really mean this, it would make the bug report invalid.
No, that step is probably not necessary. I added it just to simulate the sort of problem I was having. The point was to try and use YaST's printer setup process to correct the artificially introduced error, and see if the ability to print to a printer would work, AFTER completing the setting up of the printer via YaST. But because the YaST printer setup does not start the CUP's server daemon, and reports everything was a success, the user is left wondering why he/she cannot print something, after completing the printer setup steps. THIS is the point of this bug report! Not that there was an error in my CUP's configuration file, that I wanted to have "magically healed", but that YaST did NOT properly guide me to a solution for getting the printing subsystem up and running. Instead it mislead me and gave no indication about whether the CUPs server was actually running or not. It implied that everything was OK in fact! And as I eventually found out that was NOT the case. The CUPs server was not restarted by YaST, and therefore not running, and therefore I became confused as to why not! If there was a problem then I should have been given a very plain warning that it had failed, and possibly an explanation as to why.. But in fact, there was NO failure of misconfiguration, YaST simply is not even trying to start the CUPs server apparently, or testing it! Therefore the setup of a printer is incomplete and this will confuse users! Because I could not print, after using YaST, my assumption was that I must be configuring things wrong, or some other kind of problem existed. (Man I spent hours trying to guess what was wrong! Chasing things like possible authorization problems, wondering if the firewall was screwed up.. etc) In order to print, the CUPS server must be started, and why should a user have to KNOW that this step must be done manually and separately? I sure didn't, YaST sure as heck did not tell me, so I assumed YaST was attempting to start the CUPs server and would report any problems if any were encountered! Most other YaST routines that configure some server DO in fact attempt to restart their associated server. Any user is going to make this same assumption, that once done configuring a printer in YaST, that one should be able to IMMEDIATELY start printing! Therefore the CUP's server should have been restarted, as part of the printer setup process, in order to allow a user to print.
Instead of only long and verbose complaints you should have better provided here also the hard facts which you provided in you mail on opensuse@opensuse.org which I found there by pure luck in http://lists.opensuse.org/opensuse/2009-11/msg00258.html
What you found was some of my early attempts at trying to figure out what was wrong, before I eventually came to realize that YaST was misleading me. There may indeed be other errors that need to be address, with crashes and/or misconfigured CUPs files... I am not yet ready to address those or submit a bug report against them yet.. My "long and verbose complaint" here was to try and provide enough information to differentiate between problems caused by a misconfiguration of a printer, and problems cause by a tool that is incorrectly doing the job expected of it, i.e. guiding the user to a complete and acceptable solution. Let me study the crash issue further, and if I can replicate it, I will submit a separate bug report. But again, let me repeat, the crash is NOT the point of this bug report. The incorrect behavior of the YaST printer setup tool is. IT IS FAILING TO AUTOMATICALLY RESTART THE CUPS SERVER DAEMON UPON COMPLETION OF THE SETUP PROCESS. I don't believe the YaST printer setup is even trying to restart the CUPS Server daemon, since I can do so immediately, and without any problems, manually, after I have completed the YaST printer setup process. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=553147
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553147#c4
--- Comment #4 from Johannes Meixner
http://bugzilla.novell.com/show_bug.cgi?id=553147#c5
Michal Zugec
participants (1)
-
bugzilla_noreply＠novell.com