Bugzilla – Bug 309933
hplip can't talk to printer
Last modified: 2008-07-10 12:37:38 UTC
hp-toolbox finds the printer, but cannot talk to it. This was working fine with previous versions of hplip. Bus 004 Device 006: ID 03f0:5511 Hewlett-Packard
Up to 1.7.4a is working fine.
Many thanks for the descriptive report ;-) It works well for my HP printers and all-in-one devices => WORKSFORME. By the way: See http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.0708141120210.25428%40nelson.suse.de and http://sourceforge.net/mailarchive/message.php?msg_name=Pine.LNX.4.64.0707040850200.22081%40nelson.suse.de
This is obviously a completely different bug.
I just installed 10.3-RC1 and I have a HP PSC 500 connected with the parallel port. I have configured the printer within YAST, and print correctly. But hp-toolbox don't detect the dipositive (Printer-Scaner) in the "Parallel Port". I find it manually at "/etc/lp0", but also don't detect it. In the installation of the RC1 only install HPLIP and HPIJS. I have installed hp-officeJet-0.91-171.i586.rpm, for installing it within "ptal-init setup", and it detect my printer-scanner, and it is configure. After, I run hp-toolbox and don't detect the dipositive (Printer-Scaner) in the "Parallel Port". I find it manually at "/etc/lp0", but also don't detect it. Sorry for my english (I need to improve it). Thanks and best regards from Spain. Manel León.
I still do not understand exactly what you mean. Again it looks like a permission problem. Since HPLIP version 2.7.6 the device I/O is no longer done by a daemon process which runs as root (therefore there have been no permission problems with HPLIP version before 2.7.6 but on the other hand no permission restrictions could be set with HPLIP version before 2.7.6). The out-of-the-box settings are sufficient for plain printing and for scanning with a all-in-one USB device. See the URLs in comment #2 how you can set permissions manually if the out-of-the-box settings are not sufficient. E.g. you could add those users who need read/write device access (e.g. for scanning with a parallel-port device and/or for device-status for a plain printer) to the group "lp".
It is definitely not a permission problem since the printer is correctly identified.
Created attachment 176022 [details] Screen for my explanation See in the orther of the screen shoots (1-2-3...7). The first screen shoot, is the screen with the printer HP PSC 500 configured in YAST, in the parallel port. The second screen shoot to the seventh, I try to configure the HP PSC 500 into hp-toolbox. Thanks for your quick responses. Best regards. Manel León.
Similar problem with my HP Deskjet 6540. If I setup as hplip it is not detected in hp-toolbox and doesn't print too. It prints if setup as ordinary USB printer but hp-toolbox doesn't work for it if setup as USB printer. This worked in openSuSE 10.2. Will there please be a patch available?!
Same problem here with photosmart 7760, hp-toolbox works only for root. Forn normal user device is not found with error code=12 hp-check output: Checking proper HPLIP I/O setup (USB I/O only)... error: udev "usb_device" access mode is INCORRECT: 0644 (it must be 066x) Checking for permissions of USB attached printers... HP Device 0xb402 at 002:005: warning: Device URI: (Makeuri FAILED) Device node: /dev/bus/usb/002/005 Mode: 0664 UID: 0 (root) GID: 7 (lp) Device group and mode appear correct. Is user 'dan' a member of the 'lp' group? warning: NO (HPLIP USB I/O users must be member of 'lp' group) note: This may not be a problem if this user will not be printing using HPLIP USB I/O. Sounds like a permission problem.. Works well under opensuse 10.2 Bye
I'm having the same problem and to me also it sounds like a permission problem. Because, It asks for my password and will not accept it.
HP PSC 2350 series has the same issue. Moreover it always result to be "paused" after a reboot. Moving to final.
The 'always result to be "paused" after a reboot' issue is bug #334166.
I suspect bug#309933 and bug#309933 are related if not duplicates.
Quoting bug#332750 comment#4 : Considering these printers/scanners are probably among the most used in Linux, I increase severity a bit :-)
I have detected my problem. In the web of project HPLIP, in the installer explanation (http://hplip.sourceforge.net/install/install/index.html), I have seen the NOTE and WARNING: "In automatic mode parallel support is NOT enabled". My print device HP PSC 500 is connected on parallel port, and not support USB. How can activate parallel support on the installation with YAST of HPLIP and HPLIP-HPIJS? Best regards. Manel León.
(In reply to comment #14 from Jarl Friis) > I suspect bug#309933 and bug#309933 are related if not duplicates. > I ment bug#309933 and bug#332750 maybe related.
Will there be a fix soon?
I know it is a permission issue. Becuase, It blocks the printer when I go to the printer manager. So, I have to go into yast and delete it and reconfigure everytime.
I am having trouble as well. I have a customer with an Officejet 5610 printer. I have tried different versions of hplip, both compiled manually and installed from package management. The printer is set up successfully in both YaST and hpsetup but it will only allow you to print if you used hpsetup. However if you reboot the system, it is no longer possible to print. Instead, you have to go into the cups web interface and click on "Start Printer" as cups will decide the printer is stopped when the job you try to print fails to communicate with the printer. Restarting cups does NOT help. You have to manually stop and then start the printer through the web interface.
Comment #20 ("if you reboot ... the printer is stopped") looks like bug #334166, see also https://bugzilla.novell.com/show_bug.cgi?id=337794#c25
I assume it works for HPLIP in openSUSE 11.0 and therefore I like to close this one which is for 10.3. There will be no update package for openSUSE 10.3 because I still cannot reproduce what goes on on your particular systems and therefore I can only close it with WONTFIX for 10.3. If there are issues for openSUSE 11.0, please file new bug reports with an exact description how to reproduce it so that I have a better chance to understand what goes on on your particular systems. Please note that different issues should be reported as separated bug reports to avoid that multiple different issues get mixed up in one single confusing report. See http://en.opensuse.org/Bug_Reporting_FAQ