Re: Scanner rights messed up: please help!
On Thursday 24 August 2006 19:10, Christof Hurschler shared this with us all:
>--> No one responded to my last post, so I'll try it again. A previously
> working scanner is no longer accessible for the group "scanner". It works
> under root. Something seems to have changed in a recent dist-upgrade. -->
>--> The device is listed as:
>-->
>--> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
>--> D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
>--> P: Vendor=04b8 ProdID=0109 Rev= 1.07
>--> S: Manufacturer=EPSON
>--> S: Product=Expression1640XL
>--> C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA
>--> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>--> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>--> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>-->
>--> but ls -la /proc/bus/usb/001
>--> total 0
>--> dr-xr-xr-x 2 root root 0 2006-08-24 11:35 .
>--> drwxr-xr-x 6 root root 0 2006-08-24 11:35 ..
>--> -rw-r--r-- 1 root root 43 2006-08-24 11:35 001
>--> -rw-r--r-- 1 root root 50 2006-08-24 09:36 002
>-->
>--> where 001:002 used to be root:scanner, allowing scanning by users in
> that group. Not any more. -->
>--> I don't know where the rights for this device are beging set, can
> someone suggest a way to solve this problem? I did find someting about
> setting rights in the documentation for usblib, but have never had to
> intervene in this regard before. And am not sure if that is the problem
> anyway. -->
>--> This is the second or thrid time that dist-upgrade has broken my system
> because of a rights problem. First cups, more recently automounting in
> KDE, and now the scanner problem. I really like debian, but when printing
> or scanning or access to a usb stick suddenly stops working my debian
> system becomes useless to me. -->
>--> Chris
I was going to respond to your last post, but didn't really have anything much
to suggest.
1. a reboot
2. reinforcing that the user is added to the scanner group.
In sarge I had to modprobe scanner, but it seems to be found by your system,
so that's probably not required.
I also couldn't get Cups working and finally found this:-
https://launchpad.net/distros/ubuntu/+source/cupsys/+bug/55283
Worked a treat. Strangely n another Acer lappy I set up, there was no trouble?
I think it's just testing, so it is to be expected?
I had an update to my etch, lose my ppp provider file and that had to be
reconfigured, and then it couldn't find the /dev/ttyUSB0 but a reboot made it
all come together again without any problems. It's not windows, but it is
testing, so unusual tactics might need to be applied, just while things are
in flux.
HTH
Charlie
--
Registered Linux User:- 329524
+++++++++++++++++++++++++++++++++++
You know about a person who deeply interests you more than you can be told. A
look, a gesture, an act, which to everybody else is insignificant tells you
more about that one than words can. .............................Henry David
Thoreau
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Linux Debian Etch
Reply to: