Scan does not work on either F-16 box -

[Michael Schwendt]

On Fri, 24 Feb 2012 18:07:02 -0500, BG (Bob) wrote:

> On 24/02/12 17:44, ny6p01 at gmail.com wrote:
> > On Fri, Feb 24, 2012 at 05:33:44AM -0500, Bob Goodwin wrote:
> >
> > There is a simple way to overcome this limitation. Find out what bus the
> > printer/scanner is on with lsusb. Then go into /dev/bus/usb and change the
> > permissions of the bus/device that you need access to.
> >
> > Terry

The device file path varies.

>         That's what I thought too.
> 
>         [bobg at box6 ~]$ lsusb
>         Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>         Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 001 Device 012: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
              ^^^        ^^^
>         Bus 002 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse
>         (4-button)
> 
>         So I tried changing permissions and then owner.
> 
>         [root at box6 usb]# ll
>         total 0
>         drwxrwxr-x. 2 bobg root 80 Feb 24 11:34 001
>         drwxr-xr-x. 2 root root 80 Feb 24 10:58 002
>         drwxr-xr-x. 2 root root 60 Feb 24 04:09 003
>         drwxr-xr-x. 2 root root 60 Feb 24 04:09 004
>         drwxr-xr-x. 2 root root 60 Feb 24 04:09 005

That's the wrong file. The device file would have been '012' in that
directory.

I've done a "yum groupinstall XFCE" here for a very brief test, but
when logging into XFCE (albeit from GDM), the user access ACL entry
on the device file is set automatically when plugging in the scanner.
So, that hasn't been enough to reproduce the problem.

Perhaps just the XFCE Spin is affected?

-- 
Fedora release 16 (Verne) - Linux 3.2.7-1.fc16.x86_64
loadavg: 0.22 0.38 0.30