Hello, I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC, SANE cannot find my HP scanner. I tried the same using X11 from a Mac and it didn't work either. However, if I login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Any takers? I've had problems with VNC in two machines so far.
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Anybody? I'm still searching for an answer on this issue. Still unresolved. EJ
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Anybody? I'm still searching for an answer on this issue. Still unresolved. EJ
No suggestions?
redhatdude@bellsouth.net wrote:
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Anybody? I'm still searching for an answer on this issue. Still unresolved. EJ
No suggestions?
When going in remotely, are you logging in as root or as a "normal" user? That may have something to do with it. In the past, some SANE backends didn't run if you weren't root. I thought that was fixed, but it's a possibility.
I have a Canon LIDE at home and it works fine as me or as root. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "Do you suffer from long-term memory loss?" "I don't remember" - - -- Chumbawumba, "Amnesia" (TubThumping) - ----------------------------------------------------------------------
redhatdude@bellsouth.net wrote:
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can
open
SANE and scan without any problems. If I, however, do this remotely through
VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if
I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Anybody? I'm still searching for an answer on this issue. Still unresolved. EJ
No suggestions?
When going in remotely, are you logging in as root or as a "normal" user? That may have something to do with it. In the past, some SANE backends didn't run if you weren't root. I thought that was fixed, but it's a possibility.
I have a Canon LIDE at home and it works fine as me or as root.
When I log in as a normal user I can't use the scanner, SANE won't find it. If I log in as root, yes, SANE finds the scanner and allows me to scan. However, I don't want to give root access to people who want to scan.
This is probably ConsoleKit/PolicyKit in action. When you log in sat at the machine, you're a console user with physical access to the machine, and so you get permissions to access the hardware. When logging in remotely the permissions don't get set to allow you to access connected hardware. I suggest having a read about ConsoleKit/PolicyKit and working out what policy you need to change to get the permissions you want when logging in via VNC.
Jonathan.
I'm lost there Jonathan. Where do I start?
On Tue, Dec 2, 2008 at 2:44 PM, redhatdude@bellsouth.net wrote:
I'm lost there Jonathan. Where do I start?
Assuming you are running a gnome desktop....there is authorizations dialog in the system->preferences->system menu.
you should be able to adjust the authorizations for device access... including scanners.
-jef
2008/12/2 Jeff Spaleta jspaleta@gmail.com:
On Tue, Dec 2, 2008 at 2:44 PM, redhatdude@bellsouth.net wrote:
I'm lost there Jonathan. Where do I start?
Assuming you are running a gnome desktop....there is authorizations dialog in the system->preferences->system menu.
you should be able to adjust the authorizations for device access... including scanners.
In fact... as jeff says system->preferences->system->Authorisations
Then in the left hand pane, scroll down until you see "device-access". As a sub-item of that entry you'll see "Directly access scanners". Select that. In the right hand pane you'll see (amongst other things) "Implicit authorisations" ... click the Edit button. Hopefully it is self explanatory from then on...
On Tue, Dec 2, 2008 at 2:44 PM, redhatdude@bellsouth.net wrote:
I'm lost there Jonathan. Where do I start?
Assuming you are running a gnome desktop....there is authorizations dialog in the system->preferences->system menu.
you should be able to adjust the authorizations for device access... including scanners.
In fact... as jeff says system->preferences->system->Authorisations
Then in the left hand pane, scroll down until you see "device-access". As a sub-item of that entry you'll see "Directly access scanners". Select that. In the right hand pane you'll see (amongst other things) "Implicit authorisations" ... click the Edit button. Hopefully it is self explanatory from then on...
Bingo. Thank you so much. Is it possible to grant these authorizations remotely through the terminal? EJ
2008/12/3 redhatdude@bellsouth.net:
On Tue, Dec 2, 2008 at 2:44 PM, redhatdude@bellsouth.net wrote:
I'm lost there Jonathan. Where do I start?
Assuming you are running a gnome desktop....there is authorizations dialog in the system->preferences->system menu.
you should be able to adjust the authorizations for device access... including scanners.
In fact... as jeff says system->preferences->system->Authorisations
Then in the left hand pane, scroll down until you see "device-access". As a sub-item of that entry you'll see "Directly access scanners". Select that. In the right hand pane you'll see (amongst other things) "Implicit authorisations" ... click the Edit button. Hopefully it is self explanatory from then on...
Bingo. Thank you so much. Is it possible to grant these authorizations remotely through the terminal? EJ
Have never done it myself - seems to involve editing an XML file, so you'd need to do a bit of reading to find the syntax. Have a look at:
redhatdude@bellsouth.net wrote:
When I log in as a normal user I can't use the scanner, SANE won't find it. If I log in as root, yes, SANE finds the scanner and allows me to scan. However, I don't want to give root access to people who want to scan.
I wounder if you have a scanner that is not listed in /etc/udev/rules.d/60-libsane.rules. If so, the scanner symlink would not be created, and the console user would not be given permission to use the device.
Mikkel
2008/12/1 redhatdude@bellsouth.net:
Hello,
I got a F9 machine that I access through VNC. If I'm at the machine, I can open SANE and scan without any problems. If I, however, do this remotely through VNC,
SANE cannot find my HP scanner.
I tried the same using X11 from a Mac and it didn't work either. However, if I
login as root and launch SANE, it works, if finds the scanner and scans. Any idea how to solve this issue? Thanks, EJ
Anybody? I'm still searching for an answer on this issue. Still unresolved. EJ
This is probably ConsoleKit/PolicyKit in action. When you log in sat at the machine, you're a console user with physical access to the machine, and so you get permissions to access the hardware. When logging in remotely the permissions don't get set to allow you to access connected hardware. I suggest having a read about ConsoleKit/PolicyKit and working out what policy you need to change to get the permissions you want when logging in via VNC.
Jonathan.