Bugzilla – Bug 201917
Yast printer module does not print test page
Last modified: 2006-08-29 13:23:56 UTC
Installed printer HP laserjet 4L Yast printer installation module doesn´t print test page. In addition, after change the printer driver the system doesn't manage to print anymore. It is needed to restart the system, although this is likely due to my ignorance to reset CUPSD manually. Any way, this did not occur in 10.0, in which I could change printer drivers and print test pages without close Yast module.
Report in detail what you did in YaST and which (error)-messages are shown in YaST and provide the YaST log files ("y2log"), see http://en.opensuse.org/Bugs/YaST Please read http://en.opensuse.org/Submitting_Bug_Reports for some general guidelines how to provide useful information in a bug report. For example: Which driver(s) did you use? Provide the CUPS error_log file for exactly one failed attempt to print something, see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell ---------------------------------------------------------------------- If problems are encountered: 1. Set the "LogLevel debug" in /etc/cups/cupsd.conf. 2. Stop cupsd. 3. Move /var/log/cups/error_log* to another location (or delete it) in order to avoid having to search through gigantic log files. 4. Start cupsd. 5. Retry the action leading to the problem. 6. Now /var/log/cups/error_log* contains many messages that are useful for troubleshooting. ----------------------------------------------------------------------
Created attachment 97292 [details] Yast2 log files
Created attachment 97293 [details] cupsd error log file
I hope these are the right ones.
In the error_log from attachment #3 [details] there is only one error line (a line with leading "E") ----------------------------------------------------------------------------- E ... PID 5381 stopped with status 0! ----------------------------------------------------------------------------- and the matching process is ----------------------------------------------------------------------------- I ... Started backend /usr/lib/cups/backend/parallel (PID 5381) for job 149. ----------------------------------------------------------------------------- all other processes for this job exited with no errors. Note that when the backend process finishes with an error, the queue is stopped amd nust be manually re-enabled, see http://en.opensuse.org/SDB:CUPS_in_a_Nutshell "The Backends" There are some bug reports about problems with the parallel port in our Novell/Suse Bugzilla. A good report to start is bug #185135 See also the other bug reports which are mentioned there. Something is fishy with the parallel port stuff in the kernels since Suse Linux 10.0, see http://lists.suse.com/archive/suse-linux-e/2005-Nov/1206.html The current workaround is to experiment with various BIOS settings and explicite additional settings in /etc/modprobe.conf to find a setup, which actually works in a particular problematic case. I close this one as duplicate of bug #185135. *** This bug has been marked as a duplicate of bug 185135 ***
A typo in comment #5: I meant "attachment in comment #3" which is attachment #97293 [details] (attachment #3 [details] is from a totally other bug).
That's it. I only set parport to spp mode and it is all running fine again. Thank you!