On 16/01/14 13:59, MichaelMichael Hennebry wrote:
On Thu, 16 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
On 16/01/14 11:52, Michael Hennebry wrote:
IIRC, no.
I had to modify udev rules.
I looked at that yesterday but don't see a way to fix the problem,
don't understand how to! I'm
On 16.01.2014 19:59, Michael Hennebry wrote:
> On Thu, 16 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
>
>> On 16/01/14 11:52, Michael Hennebry wrote:
>>>
>>> IIRC, no.
>>> I had to modify udev rules.
>>
>> I looked at that yesterday but don't see a way to fix the problem, don't
>> understa
On Thu, 16 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
On 16/01/14 11:52, Michael Hennebry wrote:
IIRC, no.
I had to modify udev rules.
I looked at that yesterday but don't see a way to fix the problem, don't
understand how to! I'm out of my range of abilities I guess?
Here is what
On 16/01/14 11:52, Michael Hennebry wrote:
IIRC, no.
I had to modify udev rules.
I looked at that yesterday but don't see a way to fix the problem, don't
understand how to! I'm out of my range of abilities I guess?
I've simply created a script to change the permissions when I need
xsane.
On Thu, 16 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
After reading through that it seemed simpler just to live with running
su xsane, but I did the following:
[bobg@box10 ~]$ ls -l /dev/bus/usb/`lsusb |grep Canon |cut -d: -f1 |tr "
" / |cut -d/ -f 2,4`
crw-rw-r--. 1 root root 189, 1
01/16/2014 05:32 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 16/01/14 06:38, Joachim Backes wrote:
See ifhttps://bugzilla.redhat.com/show_bug.cgi?id=1019760 can help you!
Joachim Backes
After reading through that it seemed simpler just to live with running
su xsane, but I did the follow
On 16/01/14 06:38, Joachim Backes wrote:
See ifhttps://bugzilla.redhat.com/show_bug.cgi?id=1019760 can help you!
Joachim Backes
After reading through that it seemed simpler just to live with running
su xsane, but I did the following:
[bobg@box10 ~]$ ls -l /dev/bus/usb/`lsusb |grep Canon |
On 01/16/2014 12:35 AM, Bob Goodwin - Zuni, Virginia, USA wrote:
>
>
> Xsane can only find the scanner as root.
>
> Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
>
> This is an F-20 64 bit xfce system. I can probably get by this way but
> it is inconvenient.
>
> What do I nee
On Thu, 16 Jan 2014, Michael Hennebry wrote:
On Wed, 15 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
Xsane can only find the scanner as root.
Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
This is an F-20 64 bit xfce system. I can probably get by this way but
it is inc
On Wed, 15 Jan 2014, Bob Goodwin - Zuni, Virginia, USA wrote:
Xsane can only find the scanner as root.
Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
This is an F-20 64 bit xfce system. I can probably get by this way but
it is inconvenient.
What do I need to change?
I had
>
>
> Xsane can only find the scanner as root.
>
> Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
>
> This is an F-20 64 bit xfce system. I can probably get by this way but
> it is inconvenient.
>
> What do I need to change?
>
> Bob
>
It is a udev problem. I had a similar
On Wed, Jan 15, 2014 at 06:35:26PM -0500, Bob Goodwin - Zuni, Virginia, USA
wrote:
>
>
> Xsane can only find the scanner as root.
>
> Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
>
> This is an F-20 64 bit xfce system. I can probably get by this way
> but it is inconvenient.
Xsane can only find the scanner as root.
Bus 001 Device 003: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
This is an F-20 64 bit xfce system. I can probably get by this way but
it is inconvenient.
What do I need to change?
Bob
--
http://www.qrz.com/db/w2bod
Box10 Fedora-20/64bit Linux
--
u
13 matches
Mail list logo