Argh, spoke too soon. After adding saned to lp group, I was able to
select the scanner in simple-scan, but it didn't actually work.
Unable to get open device: Error during device I/O
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I have just experienced this bug in Xubuntu 11.10.
I used getfacl and found out that the scanner was assigned to root:lp.
So adding saned to the lp group fixed the problem.
How can I flag this bug for Xubuntu devs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
This 'bug' is a direct result from
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/188552 sane
does not have udev rules in place to give the device proper permissions
when plugged in, resulting in the root:root ownership. If you put in a
proper udev rule this problem goes away.
--
s
** Changed in: sane-backends (Ubuntu Hardy)
Status: Triaged => Won't Fix
** Changed in: sane-backends (Ubuntu)
Importance: Undecided => Medium
** Changed in: sane-backends (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
saned cannot access the scanner in Hardy
https://b
On Fri, Sep 11, 2009 at 4:04 PM, Jamie Strandboge
wrote:
> I had a similar issue, but did not resort to running saned as root.
> Instead, I did:
> $ sane-find-scanner
> ...
> found USB scanner (vendor=0x03f0 [HP], product=0x2a12 [Officejet J4500
> series]) at libusb:005:002
> ...
>
> Then I check
I had a similar issue, but did not resort to running saned as root. Instead, I
did:
$ sane-find-scanner
...
found USB scanner (vendor=0x03f0 [HP], product=0x2a12 [Officejet J4500 series])
at libusb:005:002
...
Then I checked the permissions of the libusb:005:002 device:
$ getfacl /dev/bus/usb/00
I'm pretty sure that I had already done that. Anyway, like I said in my
previous posts I've already switced to Debian where everything is working
perfectly. So I'm not switching back to Ubuntu at this point. Allowing a bug
in the distribution to remain unfixed for well over a year that disables
you
I ran into a fix for this by accident while I was looking at a
permissions problem with hp-levels.
Add saned to the group lp, that should fix the problem.
--
saned cannot access the scanner in Hardy
https://bugs.launchpad.net/bugs/229343
You received this bug notification because you are a membe
** Also affects: sane-backends (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: sane-backends (Ubuntu Hardy)
Status: New => Triaged
** Changed in: sane-backends (Ubuntu Hardy)
Importance: Undecided => High
--
saned cannot access the scanner in Hardy
https://bu
Creating the policy file didn't work for me, however Vanessa's solution
posted on 2008-09-05 (running saned as root) did solve the problem. I'm
also using xinetd to start saned.
Regards
---
Distributor ID: Ubuntu
Description:Ubuntu 8.04.3 LTS
Release:8.04
Codename: hardy
--
s
Chances that it might be fixed in karmic too with the latest debian
imports, we'll see.. Great to know anyway.
--
saned cannot access the scanner in Hardy
https://bugs.launchpad.net/bugs/229343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I realize this not the place to discuss this and I hope no one thinks it
is too rude, but I just wanted to let anyone know that may be interested
that because of this bug I installed Debian 5.0 and everything is
working perfectly ... printer & scanner. No more scanner freezes and
editing permission
I'm not sure what the 'why' is, but I share my printer and scanner via a
network as well.
Unfortunately, the workaround shown by Vanessa Ezekowitz is not
available for 8.04, which is the LTS version supported for 5 years and
what I would have liked to continue to use. A printer and scanner are
som
Uhm could that have something to do with the fact that I share both
printer and scanner via network? I simply noticed that as soon as lp did
not have any permissions anymore, all printing tasks would not complete
anymore (the workarround of Vanessa Ezekowitz works well anyway). As for
the bug itsel
Just wanted to point out that using the workaround
sudo chown root:saned /dev/bus/usb/001/002 && sudo chmod g+rw
/dev/bus/usb/001/002
did not break printing for me on Ubuntu 8.04 with my multifunction HP
Deskjet F4280 like Sandro Mani is stating. Though I have noticed that
after certain updates t
Just wanted to point out that the workaround
sudo chown root:saned /dev/bus/usb/001/002 && sudo chmod g+rw
/dev/bus/usb/001/002
is potentially dangerous for multifunction devices as it will make
scanning work, but will brake printing, as the node needs to have
gid=lp.
--
saned cannot access the
I've since upgraded our boxes here to Jaunty, and this issue has again
reared its head. The solution for me was to follow the HowTo at
https://help.ubuntu.com/community/ScanningHowTo , and then change the
RUN_AS_USER line in /etc/default/saned such that saned runs as "root".
Doesn't jive well with
THANK YOU!!
I'd been looking for solutions and trying different configuration
settings for hours, kept thinking I was doing something wrong in the
configuration.
Changing the permissions on the scanner fixed it! Oddly enough I
installed Debian 5.0 on this machine a few weeks ago and it setup the
I can confirm this solution works. Without this fix, sharing a scanner
over network with saned simply does not work, and this problem is not
easy to debug. No HowTo I could find had any reference to this issue.
I finally tracked down this bug report after a few hours of fiddling
around. I hope the
Indeed polkit-auth won't work, since the saned daemon is not tied to a
ConsoleKit session (which the auto-ACL magic relies on). Your hal FDI
solution sounds like the most appropriate approach, thanks for this.
** Changed in: sane-backends (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
jhansonxi: It is not a duplicate. bug #180794 denies access to the
current user; This bug denies access to user 'saned'. The fixed released
for that bug does not fix this one.
I can confirm Paul Worrall's changes to the file
/usr/share/hal/fdi/policy/10osvendor/20-acl-management.fdi fixes the
prob
same thing happening on my boxes here, also running Hardy. Another
solution, though somewhat less secure (but OK for me since the scanner's
only accessible to my LAN) is to just tell xinetd to run saned as root.
On my box then, /etc/xinetd.d/saned reads:
service saned
{
socket_type = stream
serve
Might be another duplicate of bug #180794
--
saned cannot access the scanner in Hardy
https://bugs.launchpad.net/bugs/229343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
I have to manually set permissions to the scanner device to be able to
allow remote users to use the scanner.
sudo chown root:saned /dev/bus/usb/001/002 && sudo chmod g+rw
/dev/bus/usb/001/002
you need to replace the 001/002 with your own devices address, you can
find this by issues
scanimage -L
** Changed in: sane-backends (Ubuntu)
Sourcepackagename: None => sane-backends
--
saned cannot access the scanner in Hardy
https://bugs.launchpad.net/bugs/229343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I subsequently tried removing the above HAL policy file and using:
polkit-auth --user saned --grant org.freedesktop.hal.device-
access.scanner
instead, but this did not work.
--
saned cannot access the scanner in Hardy
https://bugs.launchpad.net/bugs/229343
You received this bug notification be
I needed to make a small change to the file so that acls get
reconfigured at start up, otherwise saned doesn't get access to the
scanner until someone logs in to the PC the scanner's connected to (thus
invoking hal-acl-tool --reconfigure).
** Attachment added: "HAL policy file, V2"
http://launc
saned is started by inetd with user name "saned" so, hacking the file
"/usr/share/hal/fdi/policy/10osvendor/20-acl-management.fdi" I created
the attached file in "/etc/hal/fdi/policy/20-acl-management.fdi" which
ensures that user "saned" always has access to the scanner. This seems
to resolve the
28 matches
Mail list logo
