Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash

Bug #1956533 reported by Michael Hohmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any).

As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly.

In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly.

So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper.

What you also need:
1) Ubuntu 20.04.3 LTS
2) I don'd know. Sorry.
3) When printing to /dev/lp0, a page should come out of the printer.
4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything).

If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1956533/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Paul White (paulw2u) wrote :

According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Printing the package that this bug report should initially be reported against is 'cups'.

tags: added: focal
affects: ubuntu → cups (Ubuntu)
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Moving to the kernel.

A already the command 'echo "Test" > /dev/lp0' causes the crash, it is not caused by CUPS, but by the implementation of /dev/lp0 which is the kernel.

affects: cups (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1956533

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.