Printer no longer works after Suspend

Thanks for your bug report. What happens if you resume from suspend and restart cups via 'sudo /etc/init.d/cupsys restart'? Thanks in advance.

I assume that your printer is connected to the parallel port. If not, please tell.

It seems that the parallel port does not recover from the suspend. Can you run the command "lsmod | egrep 'lp|par|ppdev'", post the output here, suspend and resume, and then run the command again and post the output again?

If the kernel modules are still there after resuming, do

cat /proc/sys/dev/parport/parport*/autoprobe*
rmmod lp
rmmod ppdev
rmmod parport_pc
rmmod parport
modprobe lp
modprobe ppdev
cat /proc/sys/dev/parport/parport*/autoprobe*

Please post the output and error messages of all these commands here, and continue also if you get errors.

Can you print after running these commands?

Hi, sorry for the late reply. I've since upgraded to Feisty, and my printer still doesn't work after suspend; it also doesn't work after hibernate (since my computer hibernates better in Feisty).

I tried all of the above commands and still can't print. Things just sit in the print queue forever, and the printer doesn't budge. If I leave things in the print queue and restart the computer, they start printing immediately when Kubuntu starts up.

Attached is the output I get from the console.

I also have exactly the same problem on Edgy with 2.6.20-16 kernel.

I have found a workaround for this problem. This problem stems from another issue. USB devices fail to work after a hibernate. The workaround is as follows:

1. Cancel the print job that fails to print
2. Shutdown the printer
3. Remove and reinstall USB modules
~$ sudo rmmod usbhid xpad ehci_hcd ohci_hdc usbcore
ERROR: Module usbhid does not exist in /proc/modules
ERROR: Module xpad does not exist in /proc/modules
ERROR: Module ohci_hdc does not exist in /proc/modules
ERROR: Module usbcore is in use by ohci_hcd
~$ sudo modprobe usbcore usbhid xpad ehci_hcd ohci_hcd

4. Bring up the printer
5. Retry the print job

Same problem here. Parallel port printer HP LaserJet 1100

If I shut down cups, unload the modules (lp,ppdev,parport,parport_pc) and reload the modules, dmesg says 'lp: driver loaded but no devices found'

Kernel is 2.6.20-16-lowlatency

Works fine after reboot.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.