http://bugzilla.opensuse.org/show_bug.cgi?id=916781
--- Comment #23 from Anthony Lee
In your error_log_1print.txt in attachment#622879 [details] there is: ------------------------------------------------------------------------- $ grep PID error_log_1print.txt
I [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter /usr/lib/cups/filter/pdftops (PID 3304) I [11/Feb/2015:17:45:10 +0000] [Job 9] Started backend /usr/lib/cups/backend/parallel (PID 3305) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pdftops (PID 3306) D [11/Feb/2015:17:45:10 +0000] [Job 9] Started filter pstops (PID 3307) D [11/Feb/2015:17:45:11 +0000] [Job 9] PID 3306 (pdftops) exited with no errors. -------------------------------------------------------------------------
Only one preocess finished. The other ones, in particular /usr/lib/cups/backend/parallel seem to just hang because there are no error messages.
I guess /usr/lib/cups/backend/parallel endlessly hangs waiting to connect to the printer via the parallel port but that does somehow not work.
I guess while /usr/lib/cups/backend/parallel endlessly hangs there is "/dev/lp0: Device or resource busy".
Anthony Lee, ar root run
cancel -a
to stop and remove all pending/active print jobs, then reboot your system and retry the various echo -en "\rHello\r\f" >/dev/lp0 tests to directly access your printer.
I have to say I hate this feedback system. I ran a load of your scripts (which failed to make the printer print), recording results etc, then performed yast2 => Hardware Information, and extracted Printer stuff from file (now attached: evidence that printer is physically and logically attached at some level), but the attachment process blew away all my previous results. I'll try and copy them here: vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Long wait, nothing happens. Power printer down, then up, and try again: ^C vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. ^C vivaldi:/home/wendy # rmmod lp vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc vivaldi:/home/wendy # rmmod parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. ^C vivaldi:/home/wendy # rmmod lp vivaldi:/home/wendy # rmmod ppdev vivaldi:/home/wendy # rmmod parport_pc vivaldi:/home/wendy # rmmod parport vivaldi:/home/wendy # rm /dev/lp* vivaldi:/home/wendy # systemd-tmpfiles --create /usr/lib/tmpfiles.d/parallel-printer.conf vivaldi:/home/wendy # modprobe parport vivaldi:/home/wendy # modprobe parport_pc vivaldi:/home/wendy # modprobe ppdev vivaldi:/home/wendy # modprobe lp vivaldi:/home/wendy # echo -en "\rHello\r\f" >/dev/lp0 Same again. Sorry it's all taking so long. Please remember I'm just a guy who is trying to use this system. My LaserJet 5MP is in good condition, and gives a sharp clean print, even if it is a little slow, so I am not planning to junk it. Furthermore, it has always worked immediately from install by yast2, so I am no expert in this area --- and do need help. My previous SuSE install was 12.3, and before that 11.2 (I think), using the same physical hardware and daughterboard, and there was never any problem. I guess if you are partitioning off some (parallel) printers during installation, SuSE needs to make sure you have a foolproof way of bringing those printers in where necessary. -- You are receiving this mail because: You are on the CC list for the bug.