You are not logged in.
Pages: 1
I have an HP Desktop 3050A that was working fine via hplip for about a day. It hasn't worked since and I'm entirely at a loss as to why. It seems to be a CUPS and/or hplip issue, since I can scan with it perfectly fine. However, when I try to print, I get an error, and printer state flips to 'Stopped - /usr/lib/cups/backend/hp failed'.
I've tried removing and setting it up again, but I have the same issue, I've tried it with and without avahi daemon, reinstalling/restarting cupsd, reinstalling hplip, but nothing seems to help me.
-Something clever and witty-
Offline
Recently there was cups package update. Do you have the recent version (1.4.8-2) and are your system up to date? If yes, then try to downgrade the package.
Offline
I'd suggest you delete the printer from your config and re-add it as this has worked for me in the past, I'd also suggest trying each of the different drivers available for it (hp-cups and hpijs IIRC) to see which works best for you printer (I think hp-cups is the newer one they are working on but it can have some issues alongside its better feature set).
Offline
It doesn't seem to be the latest CUPS because I was having problems before I updated it, and I can't start cupsd at all if I downgrade it. I also deleted the printer and re-added it with each of the different drivers (one of the first things I did) but that doesn't help me either. It might be worth noting is that if I set up the printer via hp's tools it uses hpijs and not hp-cups. CUPS first complains that the printer isn't connected (and that the hp backend failed), then goes to what I mentioned before 'Stopped - /usr/lib/cups/backend/hp failed'.
I've been wrestling with this for maybe a week now and this is the first time I've ever run into a Linux problem that I wasn't able to solve on my own in the 5 years I've been with Linux, which makes this all the more frustrating. Never much liked dealing with CUPS.
-Something clever and witty-
Offline
Try removing cups and its config completely, then reinstalling it - as I've just remembered that was infact what I had to do when I had that problem.
IIRC what you need to do is;
#remove cups without keeping config and ignoring dependencies
pacman -Rddn cups
pacman -S cups
Then try adding it again.
Offline
Well, I gave that a shot but it didn't do me any good, still the same problem.
-Something clever and witty-
Offline
Are your user in lp and sys groups? You can also try accesing printer on root account for clarification it isn't any permission/access problem.
Offline
Have you checked through your /var/log/cups/error_log to see if anything interesting appears (perhaps post it here)? You may need to increase the logging level in cups to get usefull information IIRC.
Offline
AHA! I fixed it, I scrolled through /var/log/cups/error_log too fast the first time to see it, but it was a permissions issue (logging in as root didn't fix it). It said that libusb needed write access to something it did not have write access too, and everything just failed from there. All I did was change what it was looking at to allow write access from everyone and now it works.
I really hate my solution and there has to be a better way to do it...
EDIT: Well, it works so long as I check the log and change the permissions every time I plug in my printer, which is damned ugly.
Last edited by the_nate (2011-08-24 16:21:42)
-Something clever and witty-
Offline
Well have you looked at what the ownership/permissions on the path in question is initially?
Can you pehaps post a copy of the error message in question. cups seems to run as root by default so the question is whether the path is created without any write permissions or whether it runs another program as another user which then can't access the device.
Offline
I did, it's owned by root and root only has write permissions to it, but it can be read and executed globally. If I make it globally writeable, everything works just fine. Logging in as root (or not) makes no difference either way. Here's the error in question, everything after that tries, and fails to continue the printing job.
D [24/Aug/2011:12:02:59 -0400] [Job 106] libusb couldn't open USB device /dev/bus/usb/002/004: Permission denied.
D [24/Aug/2011:12:02:59 -0400] [Job 106] libusb requires write access to USB device nodes.
-Something clever and witty-
Offline
Take a look at https://wiki.archlinux.org/index.php/CU … ermissions maybe the info there can help.
Offline
Take a look at https://wiki.archlinux.org/index.php/CU … ermissions maybe the info there can help.
Hmm...unless I did that wrong, it didn't seem to work. Worth noting though is that my printer isn't mounted in group "lp" but group "scanner" despite everything (rule included).
-Something clever and witty-
Offline
Can you post output of lsusb and ls -l on the path of your current printer's usb device node.
By the looks of things the sane (scanner) udev rules are over-riding the hlip ones, this results in it ending up being owned root:scanner rather than root:lp.
Could you try chowning root:lp the usb device rather than just making it world-readable next time you need to print just to check that this is correct?
Offline
Can do, can do...
lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 064e:e201 Suyin Corp. Lenovo Integrated Webcam
Bus 002 Device 004: ID 03f0:a011 Hewlett-Packard
and ls -l...
crw-rw-r--+ 1 root scanner 189, 131 Aug 27 20:03 004
EDIT: I did chown it and that works perfectly. Now, I do want to ask if I made the udev rule correctly...I made the file /etc/udev/rules.d/10-usbprinter.rules (I followed the guide) with the contents
ATTR{idVendor}=="03f0", ATTR{idProduct}=="a011", MODE=:"0660", GROUP:="lp"
- I'm new to making udev rules (never had to before) so if that rule is wrong, I wouldn't really know.
Last edited by the_nate (2011-08-28 00:13:11)
-Something clever and witty-
Offline
I may be wrong, I'll have to check this later when I've got more time, but I think that higher numbered rules override those with lower numbers so you may want to try 99-usbprinter-rules.
Offline
MODE=:"0660", GROUP:="lp"
Remove those 2 colons. Especially the 1st one.
Offline
I'll do that. Also, do I need to reboot or otherwise restart udev when I make rules/changes to rules?
-Something clever and witty-
Offline
Pages: 1