Does anyone know how to do this? What happens is, I've gone through the YAST configuration of the scanner, and its there ok. In fact, its there twice, once with the epkowa driver and once with the xsane driver.
Start up xsane as an ordinary user and it is not found. Same applies to kooka and to iscan. In a terminal or not, makes no odds.
Start up xsane, or the others, as root, from a terminal, disregarding the dire warnings, they all see the scanner and everything works perfectly. They offer a choice between the scanner with the two drivers, as you would expect.
Check /etc/resmgr in accordance with Suse instructions, and the relevant line of the form
add usb vendor=xxxx,device=yyyy
is there as its supposed to be and the numbers are correct. As you would expect, given that it works for root.
Do /usr/sbin/lsusb as root, and its there. Do it as an ordinary user, and its not. It invites you to set permissions, without explaining how.
So somehow, although YAST is supposed to set all the permissions right, it hasn't, and one has to set them manually. But where is the scanner to set its permissions, and what should they be set to? Or should I be finding the binaries of xsane and kooka and setting them to suid?
Several hours now and counting.... Oh well, its how we learn.
Regards,
Peter
On Mon, Jan 02, 2006 at 11:19:13PM +0000, Peter wrote:
Does anyone know how to do this? What happens is, I've gone through the YAST configuration of the scanner, and its there ok. In fact, its there twice, once with the epkowa driver and once with the xsane driver.
No idea how SuSE works wrt to scanners, but have you added yourself to the group "scanner"? I'm sure it is all there in Yast somewhere, maybe a SuSE user could enlighten us?
Thanks Adam
On 02-Jan-06 Adam Bower wrote:
On Mon, Jan 02, 2006 at 11:19:13PM +0000, Peter wrote:
Does anyone know how to do this? What happens is, I've gone through the YAST configuration of the scanner, and its there ok. In fact, its there twice, once with the epkowa driver and once with the xsane driver.
No idea how SuSE works wrt to scanners, but have you added yourself to the group "scanner"? I'm sure it is all there in Yast somewhere, maybe a SuSE user could enlighten us?
Thanks Adam
I've been using xsane on SuSE 7,2 (those were days when YaST did not deal with scanner configuration!). While xsane is user.group = root.root, the permissions are -rwxr-xr-x and it works fine when run by ted!
As I recall, xsane was simply installed, and there it was.
Maybe this doesn't help woith recent SuSE (which seems to have been getting a bit weird in later versions); but I hope it does!
Best wishes, Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 03-Jan-06 Time: 00:36:27 ------------------------------ XFMail ------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ted Harding Ted.Harding@nessie.mcc.ac.uk wrote:
On 02-Jan-06 Adam Bower wrote:
On Mon, Jan 02, 2006 at 11:19:13PM +0000, Peter wrote:
Does anyone know how to do this? What happens is, I've gone through the YAST configuration of the scanner, and its there ok. In fact, its there twice, once with the epkowa driver and once with the xsane driver.
No idea how SuSE works wrt to scanners, but have you added yourself to the group "scanner"? I'm sure it is all there in Yast somewhere, maybe a SuSE user could enlighten us?
Thanks Adam
I've been using xsane on SuSE 7,2 (those were days when YaST did not deal with scanner configuration!). While xsane is user.group = root.root, the permissions are -rwxr-xr-x and it works fine when run by ted!
xsane, or the scanner device? We're more interested in the permissions on the device node!
As I recall, xsane was simply installed, and there it was.
that happens...
Maybe this doesn't help woith recent SuSE (which seems to have been getting a bit weird in later versions); but I hope it does!
Define 'bit weird'. Do you mean that they've finally got round to not making it very very easy to hose your system?
Cheers, - -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno@sommitrealweird.co.uk
On Tuesday 03 January 2006 08:21, Brett Parker wrote:
Ted Harding Ted.Harding@nessie.mcc.ac.uk wrote:
On 02-Jan-06 Adam Bower wrote:
On Mon, Jan 02, 2006 at 11:19:13PM +0000, Peter wrote:
Does anyone know how to do this? What happens is, I've gone through the YAST configuration of the scanner, and its there ok. In fact, its there twice, once with the epkowa driver and once with the xsane driver.
No idea how SuSE works wrt to scanners, but have you added yourself to the group "scanner"? I'm sure it is all there in Yast somewhere, maybe a SuSE user could enlighten us?
Thanks Adam
I've been using xsane on SuSE 7,2 (those were days when YaST did not deal with scanner configuration!). While xsane is user.group = root.root, the permissions are -rwxr-xr-x and it works fine when run by ted!
xsane, or the scanner device? We're more interested in the permissions on the device node!
As I recall, xsane was simply installed, and there it was.
that happens...
Maybe this doesn't help woith recent SuSE (which seems to have been getting a bit weird in later versions); but I hope it does!
Define 'bit weird'. Do you mean that they've finally got round to not making it very very easy to hose your system?
Cheers,
Hi I have the same problem with the printer in Suse 10.0, it is an all in one CX5400, all was O.K. until the update, scanner is OK for "nick" with printer I have to go into print manager as root to print. There is a "printer setup wizard" which asks for a password neither my password or root password works Regards - Nick Daniels I have run all Suse's since 7.0 and have never found this before.
-
Adam Bower -
Brett Parker -
Nick Daniels -
Peter -
Ted.Harding＠nessie.mcc.ac.uk