Description of problem:
A printer created by HAL stops working if it is turned off / on
(e.g. hotplugging does not work). A reboot is required to get the
printer working again. If I create the printer manually and choose
not use HAL (from the device list), hotplugging works.
Version-Release number of selected component (if applicable):
The latest FC6 with up to date patches from yum.
At least in my case always.
Steps to Reproduce:
Plug in a new USB printer (in my case Lexmark E234) and let HAL add the printer.
Print a test page - everyting ok at this point. Unplug the printer (or turn
it off) and plug it in again. Try to print - cups gets stuck on this.
Enabling the queue does not help. Rebooting the machine helps. Restarting
cups does not help either.
Printing gets stuck.
Printing should obviously work.
Linux XXXX 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686 i686 i386
On Macbook Pro (intel).
Do you still see this? If so, what does 'rpm -q hal-cups-utils' say?
My Dad still gets this problem with his FC6 and a USB Epson C46 printer.
'rpm -q hal-cups-utils' gives:-
What does 'lpstat -s' say? If you disconnect the printer, remove the queue,
then connect the printer again, do you see the same symptoms?
The indicated version of hal-cups-utils now avoids using the HAL CUPS backend
when it can.
With Fedora 8 (up to date with yum) plugging in a new USB printer does not work.
I have the following version of hal/cups package: hal-cups-utils-0.6.13-2.fc8.
When I go to (graphical) printer configuration, I can see that HAL added the
following device for the printer:
Printing test page (or anything else) fails.
If I change the device URI to:
the printer starts working immediately. (This was one of the choices in change
So %20 (hex?) is ascii for space and HAL used underscore _ there. That's the
only difference I can see...
I haven't tried rebooting and seeing if everything still work.
oh - and of course - hp -> usb
Just checked. Not an issue with space & underscore.
What does 'rpm -q udev' say? If you have 116, try the test update:
Yes, this solved my problem. Thanks!
*** This bug has been marked as a duplicate of 424331 ***