Hardy: HP-Toolbox only works when used as root

Bug #209781 reported by Kivech
4
Affects Status Importance Assigned to Milestone
hplip (Debian)
New
Undecided
Unassigned
hplip (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: Hardy both in KDE and Gnome: hp-toolbox

When starting HP-Toolbox it gives an error saying that:
"ERROR: Device not found. Please check the connection and power-on device", while the HP device is shown in the left column.

The device is hooked up, powered on and fully functional.

If one, however, launches hp-toolbox as root:
sudo hp-toolbox

The tool works properly and can communicate with the HP device without a problem.

Clearly there is some sort of permission issue here that keeps the tool from communicating properly with the device when used in regular user mode.

hp-toolbox version 2.8.2
device manager version 11
Kubuntu Hardy x86_64 completely updated

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

Update:

I just tested this on Hardy Gnome:

When starting hp-toolbox from a console this message is displayed:

HP Linux Imaging and Printing System (ver. 2.8.2)
HP Device Manager ver. 11.0

Copyright (c) 2001-7 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

QSettings: failed to open file '/etc/qt3/qt_plugins_3.3rc'
error: Unable to communicate with device (code=12): hp:/usb/PSC_750?serial=HU193CT0C9WB
warning: Device not found
error: Unable to communicate with device (code=12): hp:/usb/PSC_750?serial=HU193CT0C9WB
warning: Device not found

When starting as root it works also perfectly.

Please fix this bug, since it looks to me like this way no one can use hp-toolbox the way it is supposed to, being a regular user.

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

Can someone please look at this tool? It affects all HP all-in-one users out there.

description: updated
description: updated
Revision history for this message
MIRV (davidmirv) wrote :

I can confirm this even in Hardy KDE4. Attention to this issue would be appreciated.

Thanks

Changed in hplip:
status: New → Confirmed
Revision history for this message
MIRV (davidmirv) wrote :

As a sidenote I found a fix to this issue by changing the permissions setting of the udev device node in /etc/udev/55-hpmud.rules from MODE=0660 to MODE=0666 . Although adding yourself to the lp and scanner groups should have worked, for some reason that solution failed.

Revision history for this message
Kivech (kivech-deactivatedaccount) wrote :

@MIRV: Exactly, I managed to solve the issue in the end, but by default obviously permission are not set properly. In the forums they mentioned it also, but so far I see no fix, even though it should be a simple one I would think.

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

Thanks for your report.

This is a duplicate of Bug #195782

https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/195782

Thanks for your efforts.

Aaron

Revision history for this message
MIRV (davidmirv) wrote :

Bug #195782 reports a fix has been released, However I'm running Hardy with all current updates and I had no fix as of yet.
Additionally, that report is based on scanner problems is it not?

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

The printing team is still working the fix for this, even though it's marked as released. The bug report was initially involving scanning devices, however the hal workaround that the team is working on figuring out also involves the toolbox not working correctly unless the user is part of the scanner group. So the solution is the same, and rather than having two bugs working on the same solution as the printing team is already working on it in the other bug it would be better to focus on the one that is already being resolved. If that make sense.

Thanks for your time.

Aaron

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.