Hi
I recently did a fresh install of slack 11.0 and I'm still ironing things
out. I hope this is the last request I have to make about the setup.
At present I can only use xsane as root. I had this problem under slack
10.2 until I changed permission on the correct /proc/bus/usb file. That
didn't work this time.
Also there is no /dev/usb/scanner file present, although I don't know if
there should be one or not. The only file there is /dev/usb/lp0.
Advice would be appreciated.
jwc

john connolly :
> Hi
> I recently did a fresh install of slack 11.0 and I'm still ironing things
> out. I hope this is the last request I have to make about the setup.
> At present I can only use xsane as root. I had this problem under slack
> 10.2 until I changed permission on the correct /proc/bus/usb file. That
> didn't work this time.
> Also there is no /dev/usb/scanner file present, although I don't know if
> there should be one or not. The only file there is /dev/usb/lp0.
> Advice would be appreciated.
> jwc

Which kernel are you using?

--
Q: Why does an elephant have 4 feet?
A: Because 8 inches isn't enough.

http://www.websterscafe.com

On Fri, 03 Nov 2006 20:40:35 +0000, Handover Phist wrote:

> john connolly :
>> Hi
>> I recently did a fresh install of slack 11.0 and I'm still ironing things
>> out. I hope this is the last request I have to make about the setup.
>> At present I can only use xsane as root. I had this problem under slack
>> 10.2 until I changed permission on the correct /proc/bus/usb file. That
>> didn't work this time.
>> Also there is no /dev/usb/scanner file present, although I don't know if
>> there should be one or not. The only file there is /dev/usb/lp0.
>> Advice would be appreciated.
>> jwc
>
> Which kernel are you using?

2.6.18

john connolly wrote:

> Hi
> I recently did a fresh install of slack 11.0 and I'm still ironing things
> out. I hope this is the last request I have to make about the setup.
> At present I can only use xsane as root. I had this problem under slack
> 10.2 until I changed permission on the correct /proc/bus/usb file. That
> didn't work this time.
> Also there is no /dev/usb/scanner file present, although I don't know if
> there should be one or not. The only file there is /dev/usb/lp0.
> Advice would be appreciated.
> jwc

Try to start xsane from a terminal. Tell us what error messages you get, it
any.

--
Old Man

"I could be wrong again
I remember once in August 1993
I was wrong, and I could be wrong again" - Paul Simon

On Fri, 03 Nov 2006 20:11:29 -0500, Old Man wrote:

> john connolly wrote:
>
>> Hi
>> I recently did a fresh install of slack 11.0 and I'm still ironing things
>> out. I hope this is the last request I have to make about the setup.
>> At present I can only use xsane as root. I had this problem under slack
>> 10.2 until I changed permission on the correct /proc/bus/usb file. That
>> didn't work this time.
>> Also there is no /dev/usb/scanner file present, although I don't know if
>> there should be one or not. The only file there is /dev/usb/lp0.
>> Advice would be appreciated.
>> jwc
>
> Try to start xsane from a terminal. Tell us what error messages you get, it
> any.

As a user I get the graphic that says something like "looking for devices"
Then the graphic that says "no devices available."

As root the first graphic is the same (after the warning about using it
as root), then the scanner itself is available.

john connolly wrote:

> As a user I get the graphic that says something like "looking for devices"
> Then the graphic that says "no devices available."
>
> As root the first graphic is the same (after the warning about using it
> as root), then the scanner itself is available.

Does your username belong to the scanner group? (etc/group)

--
Old Man

"I could be wrong again
I remember once in August 1993
I was wrong, and I could be wrong again" - Paul Simon

On Fri, 03 Nov 2006 21:13:58 -0500, Old Man wrote:

> john connolly wrote:
>
>> As a user I get the graphic that says something like "looking for devices"
>> Then the graphic that says "no devices available."
>>
>> As root the first graphic is the same (after the warning about using it
>> as root), then the scanner itself is available.
>
> Does your username belong to the scanner group? (etc/group)

I just now added it (scanner::93:jwc) but it didn't change anything.

john connolly wrote:

> On Fri, 03 Nov 2006 21:13:58 -0500, Old Man wrote:
>
>> john connolly wrote:
>>
>>> As a user I get the graphic that says something like "looking for
>>> devices" Then the graphic that says "no devices available."
>>>
>>> As root the first graphic is the same (after the warning about using it
>>> as root), then the scanner itself is available.
>>
>> Does your username belong to the scanner group? (etc/group)
>
> I just now added it (scanner::93:jwc) but it didn't change anything.

Did you log out and log back in after adding yourself to the group? Nothing
would change if you didn't do that.

The fact that root can use the scanner indicates that the device node does
exist. It should be a matter of identifying it and getting permission to
use it.

If you're using udev, the scanner device is created on the fly. And if you
do ls -l /dev/usb* you should get something like:

crw-rw---- 1 root root 189, 0 2006-10-29 02:13 /dev/usbdev1.1
crw-rw---- 1 root scanner 189, 10 2006-11-03 21:15 /dev/usbdev1.11
crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep00
crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep02
crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep81
crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep83
crw-rw---- 1 root root 442, 0 2006-10-29 02:13 /dev/usbdev1.1_ep00
crw-rw---- 1 root root 442, 0 2006-10-29 02:13 /dev/usbdev1.1_ep81
crw-rw---- 1 root root 189, 128 2006-10-29 02:13 /dev/usbdev2.1
<snip>

Notice that the second node belongs to the scanner group, with read/write
permissions. I think you should see something very similar - some node
that belongs to a group other than root.

If you're _not_ using udev, then I _think_ your scanner is going to
be /dev/usb/scanner0 (or /dev/usb/scanner1, etc). Match up your group
membership to it's ownership.

Don't forget to logout and login again.

--
Old Man

"I could be wrong again
I remember once in August 1993
I was wrong, and I could be wrong again" - Paul Simon

On Fri, 03 Nov 2006 22:27:48 -0500, Old Man wrote:

> john connolly wrote:
>
>> On Fri, 03 Nov 2006 21:13:58 -0500, Old Man wrote:
>>
>>> john connolly wrote:
>>>
>>>> As a user I get the graphic that says something like "looking for
>>>> devices" Then the graphic that says "no devices available."
>>>>
>>>> As root the first graphic is the same (after the warning about using it
>>>> as root), then the scanner itself is available.
>>>
>>> Does your username belong to the scanner group? (etc/group)
>>
>> I just now added it (scanner::93:jwc) but it didn't change anything.
>
> Did you log out and log back in after adding yourself to the group? Nothing
> would change if you didn't do that.
>
> The fact that root can use the scanner indicates that the device node does
> exist. It should be a matter of identifying it and getting permission to
> use it.
>
> If you're using udev, the scanner device is created on the fly. And if you
> do ls -l /dev/usb* you should get something like:
>
> crw-rw---- 1 root root 189, 0 2006-10-29 02:13 /dev/usbdev1.1
> crw-rw---- 1 root scanner 189, 10 2006-11-03 21:15 /dev/usbdev1.11
> crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep00
> crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep02
> crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep81
> crw-rw---- 1 root root 442, 10 2006-11-03 21:15 /dev/usbdev1.11_ep83
> crw-rw---- 1 root root 442, 0 2006-10-29 02:13 /dev/usbdev1.1_ep00
> crw-rw---- 1 root root 442, 0 2006-10-29 02:13 /dev/usbdev1.1_ep81
> crw-rw---- 1 root root 189, 128 2006-10-29 02:13 /dev/usbdev2.1
> <snip>
>
> Notice that the second node belongs to the scanner group, with read/write
> permissions. I think you should see something very similar - some node
> that belongs to a group other than root.
>
> If you're _not_ using udev, then I _think_ your scanner is going to
> be /dev/usb/scanner0 (or /dev/usb/scanner1, etc). Match up your group
> membership to it's ownership.
>
> Don't forget to logout and login again.

Ok, That finally did it! Much obliged.
The next post on my PAN list is my post about the trouble I'm having
printing graphics files. Why don't you have a go at that one too.
Thanks, jwc

john connolly wrote:

> Ok, That finally did it! Much obliged.

Good! Had my fingers crossed on that.

> The next post on my PAN list is my post about the trouble I'm having
> printing graphics files. Why don't you have a go at that one too.

I have been thinking about it. I'll put my ideas in that thread.

--
Old Man

"I could be wrong again
I remember once in August 1993
I was wrong, and I could be wrong again" - Paul Simon