Hello,
the patch resolves the bug. So I reassign this bug to hplip.
CU
Jörg
--
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56
Jörg Frings-Fürst
D-54526 Niederkail
Threema-ID: SYR8SJXB
IRC: j_...@freenode.net, j_...@oftc.net
si
On 20/02/14 23:19, Mark Buda wrote:
reassign 730539 hplip
tags 730539 patch
thanks
The problem is that the "hp-config_usb_printer" command is taking too
long, and udevd kills the worker handling the device insertion, so it
never gets to the part of the udev rules that allow access by the
scanne
reassign 730539 hplip
tags 730539 patch
thanks
Lawrence Woodman writes:
>> Can you remove the scanner device, and reinsert it while running
>>
>> strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID
>>
>> where, of course, UDEVDPROCESSID is the pid of udevd, and send
>> /tmp/udev-strace.out. I hav
Lawrence Woodman writes:
>> strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID
>>
>> where, of course, UDEVDPROCESSID is the pid of udevd, and send
>> /tmp/udev-strace.out. I have three udevd's running on my system, though,
>> and I'm not sure why or which one does what...
>
> I only have the one
Lawrence Woodman writes:
> On 08/02/14 02:13, Mark Buda wrote:
>> Or, it *did* happen, but something else changed it. What version of the
>> "hal" package do you have installed?
> I'm using version: 0.5.14-8
Well now I am really confused. The ACLs on the USB device do not include
"group:scanner:r
On 08/02/14 02:13, Mark Buda wrote:
On 31/01/14 13:07, Mark Buda wrote:
The group id for the scanner device should be 'lp', but there should be
a read/write ACL entry for 'scanner', and there isn't. The "udevadm
test" output showed that it should have tried to make one, but
apparently that didn'
On 31/01/14 13:07, Mark Buda wrote:
> The group id for the scanner device should be 'lp', but there should be
> a read/write ACL entry for 'scanner', and there isn't. The "udevadm
> test" output showed that it should have tried to make one, but
> apparently that didn't happen for some reason.
Or,
On 31/01/14 13:07, Mark Buda wrote:
The group id for the scanner device should be 'lp', but there should be
a read/write ACL entry for 'scanner', and there isn't. The "udevadm
test" output showed that it should have tried to make one, but
apparently that didn't happen for some reason. Try running
Adding the bug back into the Cc: list.
Lawrence Woodman writes:
>
> Funnily enough I meant to include the stderr output but forgot. The full
> output is attached.
>
>> Also helpful would be the output of
>>
>> ls -lL /dev/bus/usb/002/005
>
> devname changed so:
> crw-rw-r-- 1 root lp 189, 133
Lawrence Woodman writes:
> I just did a scan as root, which worked perfectly.
Make sure the user you are scanning as is a member of the "scanner"
group. If that doesn't resolve it, please provide the output of this
command, run as root, with the scanner connected, so I can (hopefully)
figure out
On 23/01/14 21:22, John Paul Adrian Glaubitz wrote:
On 01/22/2014 05:57 PM, Lawrence Woodman wrote:
So as scanimage -L can see the scanner it looks like a user rights problem, but
I'm not sure
where to look to resolve that.
Ok, this is actually something. Can you try running a test scan as roo
On 01/22/2014 05:57 PM, Lawrence Woodman wrote:
> So as scanimage -L can see the scanner it looks like a user rights problem,
> but I'm not sure
> where to look to resolve that.
Ok, this is actually something. Can you try running a test scan as root?
Just run "xsane" or "scanimage" as root and tr
John Paul Adrian Glaubitz wrote:
I assume the scanner works properly in the same configuration on
Windows? Just to be sure it's not a hardware issue.
I don't have anything with Windows on to try, however I am confident that
it is a software issue as I was scanning some things one morning, then
On 01/21/2014 07:34 AM, Lawrence Woodman wrote:
> libsane-hpaio was already installed, so I tried removing it
> and reinstalling, but this made no difference: the scanner
> is still not being seen.
I assume the scanner works properly in the same configuration on
Windows? Just to be sure it's not
On 19/01/14 02:29, John Paul Adrian Glaubitz wrote:
tags 730539 +moreinfo
severity 730539 normal
thanks
You need to install the package "libsane-hpaio" which will
install the driver and add the necessary device information
as /etc/sane.d/dll.d/hplip.
libsane-hpaio was already installed, so I t
tags 730539 +moreinfo
severity 730539 normal
thanks
You need to install the package "libsane-hpaio" which will
install the driver and add the necessary device information
as /etc/sane.d/dll.d/hplip.
Please verify that this works and report back. If it does,
I'll be able to close this bug report.
Package: libsane
Version: 1.0.23-3
Severity: important
Dear Maintainer,
After updating from Jessie, I found that xsane would no longer see my HP
psc 750. While updating I noted that the hpaio line was dropped from
/etc/sane.d/dll.conf, so this may have something to do with it.
-- System Info
17 matches
Mail list logo
