[opensuse] Only root can use scanner on SuSE 10.2
I've done some searching around to find out why I can only use the scanner as root on a machine on which I've just installed SuSE 10.2 (i386). (Didn't have this problem under Fedora, though plenty of other problems that switching to SuSE solved.) I've found some older postings (latest is 10.0 vintage) with general advice about getting scanners configured. Some advise manual tweaking of settings in the /etc/sane.d files (which I've tried). Others say it's better to just bring up YaST and run the configuration from there (tried that, too). Neither worked. I can scan until the cows come home as root but a regular user account gets the dreaded "no devices found" error message. Amusingly, when I run xsane as a regular user and the "No devices available" dialog window pops up, there is a "Help" button; when I push it, I see "Possible reasons: ... the permissions for the device file do not allow you to use it - try as root"; then when I run xsane as root up pops "Warning. You try to run XSane as ROOT, that really is DANGEROUS!! Do not send any bug reports when you have any problem while running XSane as root: YOU ARE ALONE! ... [Cancel] ... [Continue at your own risk]." I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions. Can I get a clue, please? I'm perfectly prepared to take some razzing about how easy it should have been for me to find this information on my own, but I really did try some googling, just didn't pick the right magic combination of keywords. Bonus question (I know, asking two questions in one post lowers the chance of getting an answer to either one, but I'll risk it): any way to get Linux to respond to the buttons on the front of the scanner (Canon CanoScan LIDE30)? Many thanks! -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions. What you do is to add the user to the group. Check in /dev and get the name of the group for the device. Then edit /etc/group and add the names of the users that can use that device. For instance, if the group name is uucp
On Friday 08 June 2007 14:35, Bob Kline wrote: then modify the group uuscp in /etc/group to look like this: uucp:x:14:username1, username2, username3 -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
On Friday 08 June 2007 14:35, Bob Kline wrote:
I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions.
What you do is to add the user to the group. Check in /dev and get the name of the group for the device. Then edit /etc/group and add the names of the users that can use that device. For instance, if the group name is uucp then modify the group uuscp in /etc/group to look like this:
uucp:x:14:username1, username2, username3
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group? -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 08 June 2007 14:56, Bob Kline wrote:
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group? Is the scanner usb attached, and do the devices get built dynamically?
I suppose you could make a simple script that you could put into boot.local that could change the group with chgrp. Take a look through the sane docs and see if you can figure out how to modify the startups (device scripts) for that device so that you can control the group for the device. It seems strange to me that a device like a sane scanner would be root root. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
On Friday 08 June 2007 14:56, Bob Kline wrote:
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group?
Is the scanner usb attached,
Yes.
and do the devices get built dynamically?
Yes, but not at bootup time. They're created when root invokes (for example) xsane.
I suppose you could make a simple script that you could put into boot.local that could change the group with chgrp.
I'll give it a try, thanks.
Take a look through the sane docs and see if you can figure out how to modify the startups (device scripts) for that device so that you can control the group for the device.
I'll keep looking.
It seems strange to me that a device like a sane scanner would be root root.
Seems odd to me, too. At this stage of the evolution of Linux, users like myself who are not professional systems administrators have come to expect that things like scanners Just Work (as this one did under Fedora), so I must have done something incredibly clumsy when installing SuSE to have messed up YaST's ability to configure the scanner correctly (where "correctly" means "with permissions that allow normal user accounts to use the device"). Thanks again. I'll keep trying. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2007-06-08 at 16:49 -0400, Bob Kline wrote:
M Harris wrote:
On Friday 08 June 2007 14:56, Bob Kline wrote:
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group?
Is the scanner usb attached,
Yes.
and do the devices get built dynamically?
Yes, but not at bootup time. They're created when root invokes (for example) xsane.
Then don't have root invoke xsane, only invoke it as a user. I have used xsane for a long time and never had a problem starting it as a user. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kenneth Schneider wrote:
On Fri, 2007-06-08 at 16:49 -0400, Bob Kline wrote:
Yes, but not at bootup time. They're created when root invokes (for example) xsane.
Then don't have root invoke xsane, only invoke it as a user.
Well, I'm only invoking it as root because invoking as a normal user fails.
I have used xsane for a long time and never had a problem starting it as a user.
I'm very happy for you. I only wish I knew what I'm doing differently from you. By the way, I noticed that your answer was the only one that had a reply-to for the mailing list. Replying to all the others I had to adjust the address list by hand. Is the standard practice for this list to "reply to all"? Or is everyone hand-pruning as I am? -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-06-08 at 18:31 -0400, Bob Kline wrote:
By the way, I noticed that your answer was the only one that had a reply-to for the mailing list. Replying to all the others I had to adjust the address list by hand. Is the standard practice for this list to "reply to all"? Or is everyone hand-pruning as I am?
You are supossed to use a "good" mail program that has the "reply to list" key, like kmail, for instance. Others have to use some kind of hack, like replying to all and removing the direct answer, or use procmail+formail rule trick. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGaeK/tTMYHG2NR9URAlwxAKCSC27ziBJC8BIQL28IxquaXz3U4wCffHEz MAzcVrB2PJrmToK/RvYlYPc= =Ie4x -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-06-08 at 15:56 -0400, Bob Kline wrote: You haven't said what scanner is that, specially how is it connected. Or I have't noticed.
What you do is to add the user to the group. Check in /dev and get the name of the group for the device. Then edit /etc/group and add the names of the users that can use that device. For instance, if the group name is uucp then modify the group uuscp in /etc/group to look like this:
uucp:x:14:username1, username2, username3
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group?
Before going that road, try adding yourself to the root group and see if it works, because it might not. I remember investigating a similar problem in this list time ago, and in some special cases it wasn't a simple problem of device permissions, it is way deeper. Have a look here, for instance: http://lists.opensuse.org/opensuse/2005-03/msg01243.html http://en.opensuse.org/SDB%3AConfiguring_Scanners_from_SUSE_LINUX_9.2#libusb... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGabnetTMYHG2NR9URAsuTAJ0TqS+seCj+OWmHVqZuWKRZsD/IUgCfadfd /m0/wZmVjAefWPX8MTHWAX4= =pFro -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Friday 2007-06-08 at 15:56 -0400, Bob Kline wrote:
Thanks, that would be a perfect solution, except the group owner is set to root. What do I need to configure to get it to be some other group?
Before going that road, try adding yourself to the root group and see if it works, because it might not.
Indeed it does not.
I remember investigating a similar problem in this list time ago, and in some special cases it wasn't a simple problem of device permissions, it is way deeper.
Have a look here, for instance:
http://lists.opensuse.org/opensuse/2005-03/msg01243.html
http://en.opensuse.org/SDB%3AConfiguring_Scanners_from_SUSE_LINUX_9.2#libusb...
These lead me to advice on configuring /etc/resmgr.conf. I've been trying this approach, but without any success. I've added: add usb:any desktop allow desktop tty=/dev/tty[1-9]* || tty=tty[1-9]* || tty=:0 at the bottom of that file, restarted the resmgr daemon, logged out of the machine and back in as a regular user, and still no luck. Is it really expected that any mortal Linux user who wants the scanner to work will be willing to endure this much pain gladly? :-) I also found this: http://lists.alioth.debian.org/pipermail/sane-devel/2006-April/016464.html http://lists.alioth.debian.org/pipermail/sane-devel/2006-April/016468.html from a SuSE 10.0 user, who was experiencing the same symptoms, which he tracked down to a policy change introduced by SuSE in 10.0. I tried his technique of adding a file in /etc/resmgr.conf.d (plugging in the right values from my sane-find-scanner output), but though it worked for him, it didn't work on my machine. I saw the advice in that thread about looking in the YaST2 logs, but I saw nothing useful there. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-06-08 at 17:52 -0400, Bob Kline wrote:
Before going that road, try adding yourself to the root group and see if it works, because it might not.
Indeed it does not.
I thought so.
Have a look here, for instance:
http://lists.opensuse.org/opensuse/2005-03/msg01243.html
http://en.opensuse.org/SDB%3AConfiguring_Scanners_from_SUSE_LINUX_9.2#libusb...
These lead me to advice on configuring /etc/resmgr.conf. I've been trying this approach, but without any success. I've added:
add usb:any desktop allow desktop tty=/dev/tty[1-9]* || tty=tty[1-9]* || tty=:0
Yep, but you misslooked something. There are some scanners for which nothing will work, but being root. Nothing in the permissions you change for them work, because the driver simply needs direct access to the hardware, and is reserved to root. Or something like that. I don't know if that is your case, but that's why I asked what type of scanner you have and how is it connected. I think it is usb, isn't it? What I intended you to look at is this paragraph in one of the links: ] Alternatively you can use "saned" which is a service for scanning via ] network. On the server the saned is set up and launched via xinetd. On ] the client the "net" backend is used for scanning via network. See "man ] saned" and "man sane-net". By using the loopback network this can be ] used on the local host too. In this case server and client are the same ] machine "localhost". Some scanners (e.g. parallel port scanners) require ] root privileges. To access such a scanner as normal user on the local ] host you may set up the following: ] ] 1. Let the saned run as root (default in /etc/xinetd.d/sane-port) ] 2. Allow access from "localhost" in /etc/sane.d/saned.conf ] 3. Specify the server "localhost" in /etc/sane.d/net.conf ] 4. Activate the "net" backend in /etc/sane.d/dll.conf It is a roundabout way, certainly... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGaeMgtTMYHG2NR9URAkh5AJwMlq9nA8+0puG99ov8StUnEojDlwCfVQA4 kijUrdaDGtyvDvxP9GtlNZA= =kSx5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
Yep, but you misslooked something. There are some scanners for which nothing will work, but being root. Nothing in the permissions you change for them work, because the driver simply needs direct access to the hardware, and is reserved to root. Or something like that.
Well, as I mentioned earlier in the thread, this is the same hardware that worked fine under Fedora (without resorting to the saned approach you refer to below).
I don't know if that is your case, but that's why I asked what type of scanner you have and how is it connected. I think it is usb, isn't it?
Yes.
What I intended you to look at is this paragraph in one of the links:
] Alternatively you can use "saned" which is a service for scanning via ] network. ....
It is a roundabout way, certainly...
Yes, but it's beginning to look as if I don't have any other choice (short of going out and buying an iMac). Thanks for your suggestions. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-06-08 at 21:00 -0400, Bob Kline wrote:
Well, as I mentioned earlier in the thread, this is the same hardware that worked fine under Fedora (without resorting to the saned approach you refer to below).
Yes, very curious.
It is a roundabout way, certainly...
Yes, but it's beginning to look as if I don't have any other choice (short of going out and buying an iMac). Thanks for your suggestions.
Heed Mr. Marcus Meissner advice first (in this thread), he knows a lot about these things. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGanxmtTMYHG2NR9URAs6eAJ4mRX8XLTkfVxstBKup88X5YaC3OwCePRDR 4lLYS+Eq2GFcY/EHKFQveg8= =D7en -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
Heed Mr. Marcus Meissner advice first (in this thread), he knows a lot about these things.
Well, I'm heeding as well as I know how. In this case, his advice was a single sentence:
If you let it get autodetected and configured by YAST, then it the permissions should be set up correctly.
So I replied explaining that I thought that's what I had done, and I went on to describe exactly what I was doing, hoping someone would spot and point out to me whatever boneheaded mistake I had made. Here's my reply: Well, I thought I had done that (as indicated above), but perhaps what I did and "let it get autodetected and configured by YAST" aren't exactly the same things. I log into the machine as root, run yast2, click on Hardware, then Scanners, and I see it run through an unattended checklist ending with "Detecting USB and SCSI scanners" after which it shows a line with "plustek Canon N1240U/LiDE30 at plustek:libusb:007:002". If I click on Other ... Restart Detection I end up with the same display. If I click Other ... Test I hear the hardware make some noises and a bunch of tests are listed and all marked as OK. If I then log into the machine as a normal user and run xsane I end up with the "No devices available" message. Am I missing a step in YAST? Can anyone tell me where the gap is between what I am doing in YaST and what Mr. Meissner is advising me to do? Is there some other package on which all of this relies that everyone's assuming I have (but don't)? For example, earlier in the thread I pointed out the discrepancy between a FAQ document some other poster had directed me to and my configuration: I noted that the FAQ says that SANE "... comes with a hotplug script and related documentation ..." but I can't find any such script or documentation in any of the three packages installed on the machine which have "sane" in the package name. Perhaps Mr. Meissner will elaborate on his advice. I'm grateful for all of the suggestions offered so far, and I've tried diligently to try everything suggested and report back the results. I haven't given up yet. Thanks! -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-06-09 at 08:00 -0400, Bob Kline wrote:
Well, I'm heeding as well as I know how. In this case, his advice was a single sentence:
If you let it get autodetected and configured by YAST, then it the permissions should be set up correctly.
So I replied explaining that I thought that's what I had done, and I went on to describe exactly what I was doing, hoping someone would spot and point out to me whatever boneheaded mistake I had made. Here's my reply:
You should simply reply always to the list, which he scans (pun intended ;-) )
Well, I thought I had done that (as indicated above), but perhaps what I did and "let it get autodetected and configured by YAST" aren't exactly the same things. I log into the machine as root, run yast2, click on Hardware, then Scanners, and I see it run through an unattended checklist ending with "Detecting USB and SCSI scanners" after which it shows a line with "plustek Canon N1240U/LiDE30 at plustek:libusb:007:002". If I click on Other ...
Isn't that your scanner?
Restart Detection I end up with the same display.
Then your scanner is reporting itself that way. You can check with "usbview".
If I click Other ... Test I hear the hardware make some noises and a bunch of tests are listed and all marked as OK. If I then log
I assume you accepted yast proposal. :-?
into the machine as a normal user and run xsane I end up with the "No devices available" message. Am I missing a step in YAST?
Can anyone tell me where the gap is between what I am doing in YaST and what Mr. Meissner is advising me to do? Is there some other package on which all of this relies that everyone's assuming I have (but don't)? For example, earlier in the thread I pointed out the discrepancy between a FAQ document some other poster had directed me to and my configuration: I noted that the FAQ says that SANE "... comes with a hotplug script and related documentation ..." but I can't find any such script or documentation in any of the three packages installed on the machine which have "sane" in the package name.
Linux is a moving target, and things change, sometimes a lot. If that script does not exist, it means that things are done diferently, by SuSE, or nowdays. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGaprAtTMYHG2NR9URAg93AJ9QpQ/Y7J0QxyGRR0DxIWQ09wV0xACfZkDI nIboPKB/CWMqTgQAgtSUa4k= =qOoE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
You should simply reply always to the list, which he scans (pun intended ;-) )
Sorry, isn't that what I did?
Well, I thought I had done that (as indicated above), but perhaps what I did and "let it get autodetected and configured by YAST" aren't exactly the same things. I log into the machine as root, run yast2, click on Hardware, then Scanners, and I see it run through an unattended checklist ending with "Detecting USB and SCSI scanners" after which it shows a line with "plustek Canon N1240U/LiDE30 at plustek:libusb:007:002". If I click on Other ...
Isn't that your scanner?
Yes. I have no problems whatsoever with SuSE recognizing and using the scanner, as long as the operations are performed as root. This isn't a hardware detection problem.
If I click Other ... Test I hear the hardware make some noises and a bunch of tests are listed and all marked as OK. If I then log
I assume you accepted yast proposal. :-?
I clicked 'Finish' if that's what you mean. Still doesn't allow ordinary users to use (or even detect) the scanner.
Linux is a moving target, and things change, sometimes a lot. If that script does not exist, it means that things are done diferently, by SuSE, or nowdays.
I think I understand that. What I need is to find out what I need to do differently than what I have done, which is essentially: 1. Install SuSE 10.2 using the defaults for a workstation 2. Install the updates to packages modified since 10.2 was released 3. Run YaST to configure the scanner as described above Cheers, -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-06-09 at 09:30 -0400, Bob Kline wrote:
Carlos E. R. wrote:
You should simply reply always to the list, which he scans (pun intended ;-) )
Sorry, isn't that what I did?
Well, I thought I had done that (as indicated above), but perhaps what I did and "let it get autodetected and configured by YAST" aren't exactly the same things. I log into the machine as root, run yast2, click on Hardware, then Scanners, and I see it run through an unattended checklist ending with "Detecting USB and SCSI scanners" after which it shows a line with "plustek Canon N1240U/LiDE30 at plustek:libusb:007:002". If I click on Other ...
Why do you click on "other" when the detected scanner is shown? Highlight the detected scanner and click on next/finish whichever the choice is. By clicking on "other" you tell YaST that the detected scanner is _not_ correct and you will manually select the correct scanner. Or did I miss that the detected scanner is not the correct one? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kenneth Schneider wrote:
Why do you click on "other" when the detected scanner is shown?
Desperation. That's something I did only after the standard sequence (invoke YaST, select Hardware, click Scanner, watch it detect the scanner, click Edit, click Next, click Finish), left me unable to use the scanner as a normal user. I tried that sequence a couple of times, and then wondered if perhaps I had missed some step, so I started looking at things like the Other button.
Highlight the detected scanner and click on next/finish whichever the choice is. By clicking on "other" you tell YaST that the detected scanner is _not_ correct and you will manually select the correct scanner.
Actually, the instructions in the left panel of YaST say "if there are unexpected results, try Other and Restart Detection." Was I wrong to consider the inability to get to the scanner as a normal user as "unexpected results"?
Or did I miss that the detected scanner is not the correct one?
Once again, SuSE identifies the scanner perfectly. This is not a hardware detection problem. It's a permissions problem. I can scan as root. I can't scan as a normal user. I don't want the users of the machine to log on as root. I don't want them to ask me to log on as root every time they need something scanned. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-06-09 at 11:37 -0400, Bob Kline wrote:
Actually, the instructions in the left panel of YaST say "if there are unexpected results, try Other and Restart Detection." Was I wrong to consider the inability to get to the scanner as a normal user as "unexpected results"?
Rather the wrong scanner detected. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGatsftTMYHG2NR9URApCEAJ4o3QEqETJ6o+ahU244J/AzJGJJigCfY6GG mrB/Q+qKUjuGkukEsp13sDI= =4zcn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-06-09 at 09:30 -0400, Bob Kline wrote:
Carlos E. R. wrote:
You should simply reply always to the list, which he scans (pun intended ;-) )
Sorry, isn't that what I did?
No, I haven't seen your reply to him in this list.
plustek:libusb:007:002". If I click on Other ...
Isn't that your scanner?
Yes. I have no problems whatsoever with SuSE recognizing and using the scanner, as long as the operations are performed as root. This isn't a hardware detection problem.
Then, why do you click "other"?
I assume you accepted yast proposal. :-?
I clicked 'Finish' if that's what you mean. Still doesn't allow ordinary users to use (or even detect) the scanner.
Ok.
Linux is a moving target, and things change, sometimes a lot. If that script does not exist, it means that things are done diferently, by SuSE, or nowdays.
I think I understand that. What I need is to find out what I need to do differently than what I have done, which is essentially:
1. Install SuSE 10.2 using the defaults for a workstation 2. Install the updates to packages modified since 10.2 was released 3. Run YaST to configure the scanner as described above
Well, that's the way we all do it, except that we don't log in as root, as Rajko mentioned. Try as user starting yast (it will request your root password), remove the current scanner from the list, exit, enter, try again. Cross you fingers, touch wood, etc. Er... you default security settings, are they set to "easy" or "secure"? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGarbTtTMYHG2NR9URAjPbAKCNWwvO6GMvtqHOUDq0I96D8h7qmgCcDTKu YCsEQb7k8/mFn9nwaD56s1w= =GJmm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
No, I haven't seen your reply to him in this list.
My mistake. Got tripped up on the lack of a Reply-to header, which I've been working around manually, but I see that I missed one.
1. Install SuSE 10.2 using the defaults for a workstation 2. Install the updates to packages modified since 10.2 was released 3. Run YaST to configure the scanner as described above
Well, that's the way we all do it, except that we don't log in as root, as Rajko mentioned.
Is it documented anywhere that if I do that on SuSE, I'll end up trapped in this scanner hell?
Try as user starting yast (it will request your root password), remove the current scanner from the list, exit, enter, try again. Cross you fingers, touch wood, etc.
Thanks, I tried that. It didn't solve the problem.
Er... you default security settings, are they set to "easy" or "secure"?
They're left at the default of "easy". -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-06-09 at 16:59 -0400, Bob Kline wrote:
Well, that's the way we all do it, except that we don't log in as root, as Rajko mentioned.
Is it documented anywhere that if I do that on SuSE, I'll end up trapped in this scanner hell?
No, that's probably irrelevant. But it is usually a bad idea to log in as root, we try to avoid that.
Try as user starting yast (it will request your root password), remove the current scanner from the list, exit, enter, try again. Cross you fingers, touch wood, etc.
Thanks, I tried that. It didn't solve the problem.
Yep, I read your other answers. Sorry. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGay0UtTMYHG2NR9URAn6yAJ4i8uAeoq1Na9SHRIMB9h93ZXtfiACePMDX kCOTQhYzDiRMJDHu/h002hI= =Hrry -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 June 2007 07:00, Bob Kline wrote:
I log into the machine as root,
Bob, normal way is to log in as user, start YaST give root password and configure hardware. What is the difference? Taking that very few people have this kind of problem, and very few people log in GUI as root [1], this is probable scenario how the setup works. YaST setup is trying to configure equipment so that normal user can operate it. It can see your normal group called users and set all permissions as appropriate, but if you are logged in as root than it will be all set that only root can operate equipment. Why this is good solution? It makes possible to change normal user group to anything you want for any reason, and setup utility will still work. Even if you want to set some device to be operated only by root the setup will work without glitch, but normal users will be out. [1] To limit number of problems that can arise from buggy software, use of root account should be limited to well tested applications. If user is logged in as root than whole set of applications available in GUI is ran with root access rights and chance to make damage is much greater than with present solution ie. regular way to log as normal user and grant root access only to YaST and few tools. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
YaST setup is trying to configure equipment so that normal user can operate it. It can see your normal group called users and set all permissions as appropriate, but if you are logged in as root than it will be all set that only root can operate equipment.
OK, I tried the following steps: 1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner 13. selected the line for the scanner 14. clicked Edit 15. confirmed that the correct driver was selected 16. clicked Next 17. clicked Finish 18. closed YaST I still can't see the scanner as a normal user. Is this what you were recommending I do? Did I miss a step? -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 June 2007 10:49, Bob Kline wrote:
Rajko M. wrote:
YaST setup is trying to configure equipment so that normal user can operate it. It can see your normal group called users and set all permissions as appropriate, but if you are logged in as root than it will be all set that only root can operate equipment.
OK, I tried the following steps:
1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner 13. selected the line for the scanner 14. clicked Edit 15. confirmed that the correct driver was selected 16. clicked Next 17. clicked Finish 18. closed YaST
I still can't see the scanner as a normal user. Is this what you were recommending I do? Did I miss a step?
No. Tough, if I would have to troubleshoot configuration made while I was logged in as root user, I would probably try to remove scanner configuration logged in as root, remove sane package, than reboot [1] log in as user and configure scanner as you described. That will be complete reversal of procedure, but even than it is not sure that all old configuration files are removed. Sincerely as it is now it demands real troubleshooting, which would require somebody from YaST team or similar expertise. Have you checked your default permissions as Carlos suggested in /etc/sysconfig/security default is PERMISSION_SECURITY="easy local" [1] While many complain on rebooting as a solution it's a short and dirty way to get system in as clean state as possible. It doesn't help when configuration files are messed up, but it helps to get all services shut down and start again. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
Did I miss a step?
No. Tough, if I would have to troubleshoot configuration made while I was logged in as root user, I would probably try to remove scanner configuration logged in as root, remove sane package, than reboot [1] log in as user and configure scanner as you described. That will be complete reversal of procedure, but even than it is not sure that all old configuration files are removed.
OK, I went through all of those steps, just as you instructed (including the reboot), and I still cannot see the scanner as a normal user.
Have you checked your default permissions as Carlos suggested in /etc/sysconfig/security default is PERMISSION_SECURITY="easy local"
Yes, they're left at the defaults. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 June 2007 16:02, Bob Kline wrote:
Rajko M. wrote:
Did I miss a step?
No. Tough, if I would have to troubleshoot configuration made while I was logged in as root user, I would probably try to remove scanner configuration logged in as root, remove sane package, than reboot [1] log in as user and configure scanner as you described. That will be complete reversal of procedure, but even than it is not sure that all old configuration files are removed.
OK, I went through all of those steps, just as you instructed (including the reboot), and I still cannot see the scanner as a normal user.
Have you checked your default permissions as Carlos suggested in /etc/sysconfig/security default is PERMISSION_SECURITY="easy local"
Yes, they're left at the defaults.
OK. After long time, and your post, I decided to see how to install my very old parallel scanner and had the same problem as you. I was able to solve it changing access permissions on device file from 640 to 666, but it was lost after reboot, so I looked udev rules and changed them. For the usb devices look in /etc/udev/rules.d/50-udev-default.rules section # misc devices for line KERNEL=="usbscanner*", MODE="644" and change to KERNEL=="usbscanner*", MODE="666" or KERNEL=="usbscanner*", GROUP="scanner", MODE="666" First will allow anybody that has account on computer to use scanner, and second only to those that belong to group "scanner". That group you can add using YaST, and add all users that need access to scanner in that group. I would create group "scanner" first and than go and install scanner. My assumption, in another post, about device creation in this particular case seems to be wrong, but to know that I need someone to test that change is really working. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 10 June 2007 20:55, Rajko M. wrote:
KERNEL=="usbscanner*", GROUP="scanner", MODE="666"
Above will allow anybody to use scanner anyway. It should be: KERNEL=="usbscanner*", GROUP="scanner", MODE="660" -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Rajko M.
I was able to solve it changing access permissions on device file from 640 to 666, but it was lost after reboot, so I looked udev rules and changed them.
For the usb devices look in /etc/udev/rules.d/50-udev-default.rules section # misc devices for line KERNEL=="usbscanner*", MODE="644" and change to KERNEL=="usbscanner*", MODE="666" or KERNEL=="usbscanner*", GROUP="scanner", MODE="666"
10.1 x86_64 KERNEL=="usbscanner*", NAME="%k", MODE="644" and I have access as <user> /etc/sane.d/ -rw-r--r-- 1 root root 2732 2006-05-02 22:18 epkowa.conf -rw-r--r-- 1 root root 793 2006-07-24 12:15 epson.conf to both epkowa and epson 22:01 wahoo:~ > scanimage -L device epkowa:libusb:001:004' is a Epson Perfection 2400 flatbed scanner device epson:libusb:001:004' is a Epson GT-9300 flatbed scanner 22:01 wahoo:~ > l /dev/usbdev* crw-rw---- 1 root root 442, 11 2007-06-10 17:02 /dev/usbdev1.12_ep00 crw-rw---- 1 root root 442, 11 2007-06-10 17:02 /dev/usbdev1.12_ep02 crw-rw---- 1 root root 442, 11 2007-06-10 17:02 /dev/usbdev1.12_ep81 crw-rw---- 1 root root 442, 0 2007-06-03 12:59 /dev/usbdev1.1_ep00 crw-rw---- 1 root root 442, 0 2007-06-03 12:59 /dev/usbdev1.1_ep81 crw-rw---- 1 root root 442, 1 2007-06-03 12:59 /dev/usbdev1.2_ep00 crw-rw---- 1 root root 442, 1 2007-06-03 12:59 /dev/usbdev1.2_ep81 crw-rw---- 1 root root 442, 3 2007-06-03 12:59 /dev/usbdev1.4_ep00 crw-rw---- 1 root root 442, 3 2007-06-10 22:01 /dev/usbdev1.4_ep02 crw-rw---- 1 root root 442, 3 2007-06-10 22:01 /dev/usbdev1.4_ep81 crw-rw---- 1 root root 442, 4 2007-06-03 12:59 /dev/usbdev1.5_ep00 crw-rw---- 1 root root 442, 4 2007-06-03 12:59 /dev/usbdev1.5_ep81 crw-rw---- 1 root root 442, 4 2007-06-03 12:59 /dev/usbdev1.5_ep82 crw-rw---- 1 root root 442, 2048 2007-06-03 12:59 /dev/usbdev2.1_ep00 crw-rw---- 1 root root 442, 2048 2007-06-03 12:59 /dev/usbdev2.1_ep81 crw-rw---- 1 root root 442, 2049 2007-06-03 12:59 /dev/usbdev2.2_ep00 crw-rw---- 1 root root 442, 2049 2007-06-03 12:59 /dev/usbdev2.2_ep81 -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
For the usb devices look in /etc/udev/rules.d/50-udev-default.rules section # misc devices for line KERNEL=="usbscanner*", MODE="644" and change to KERNEL=="usbscanner*", MODE="666" or KERNEL=="usbscanner*", GROUP="scanner", MODE="666"
First will allow anybody that has account on computer to use scanner, and second only to those that belong to group "scanner". That group you can add using YaST, and add all users that need access to scanner in that group. I would create group "scanner" first and than go and install scanner.
Well, I was indeed able to get the devices created with whatever group/permissions I wanted using the technique you describe above (though it didn't work with usbscanner* -- I had to use the pattern usbdev* to match the device names in /dev) but that *still* didn't give normal users the ability to use the scanner. At this point I'm guessing it's something to do with resmgr -- perhaps YaST didn't create some file or another in resmgr's /etc conf files; I'll say it again: I'm not enough of a systems administrator to really know what I'm doing with this stuff. So I threw in the towel and turned on saned, allowing users to invoke scanning commands via the network. It works, which is the bottom line, I suppose, but it's discouraging that I wasn't able to get things working without going around the barn this way. Thanks to everyone for their valiant efforts to provide with me guidance. Cheers, -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Bob Kline
Well, I was indeed able to get the devices created with whatever group/permissions I wanted using the technique you describe above (though it didn't work with usbscanner* -- I had to use the pattern usbdev* to match the device names in /dev) but that *still* didn't give normal users the ability to use the scanner.
from "man sane-usb": QUICK START This is a short HOWTO-like section. For the full details, read the following sections. The goal of this section is to get the scanner detected by sane-find-scanner(1). Run sane-find-scanner. If it lists your scanner with the correct vendor and product ids, you are done. See section SANE ISSUES for details on how to go on. Sane-find-scanner doesn't list your scanner? Does it work as root? If yes, there is a permission issue. See the LIBUSB section for details. [...] LIBUSB SANE can only use libusb 0.1.6 or newer. It needs to be installed at build-time. Modern Linux dis‐ tributions and other operating systems come with libusb. Libusb can only access your scanner if it's not claimed by the kernel scanner driver. If you want to use libusb, unload the kernel driver (e.g. rmmod scanner under Linux) or disable the driver when compiling a new kernel. For Linux, your kernel needs support for the USB filesystem (usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs" because the name has changed. This filesystem must be mounted. That's done automatically at boot time, if /etc/fstab contains a line like this: [...] -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-06-09 at 11:49 -0400, Bob Kline wrote:
OK, I tried the following steps:
1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner 13. selected the line for the scanner 14. clicked Edit 15. confirmed that the correct driver was selected 16. clicked Next 17. clicked Finish 18. closed YaST
I still can't see the scanner as a normal user. Is this what you were recommending I do? Did I miss a step?
That's what we wanted you to do, yes... if it doesn't work, I'm out of ideas for the moment. I'd wait till Marcus comes back (Monday?) and let's see what he says. google your model, perhaps? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGatvWtTMYHG2NR9URAhG0AJ0bMVw2CA1mlJ/lXIO/UGSdBj7sowCgihUM CXjGTkaDByDwQrqyMBmwIIU= =W0Y3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, 2007-06-09 at 11:49 -0400, Bob Kline wrote:
Rajko M. wrote:
YaST setup is trying to configure equipment so that normal user can operate it. It can see your normal group called users and set all permissions as appropriate, but if you are logged in as root than it will be all set that only root can operate equipment.
OK, I tried the following steps:
1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner
At this point if the correct scanner is selected (I don't recall you mentioning the brand/model) just click on finish. And as it has been suggested by someone else check that you don't have the permissions set to strict in /etc/sysconfig/security. Also check /etc/sane.d/dll.conf and make sure you model is uncommented (remove the # character from the start of the line).
13. selected the line for the scanner 14. clicked Edit 15. confirmed that the correct driver was selected
This should show on the first screen that shows the scanner selected.
16. clicked Next 17. clicked Finish 18. closed YaST
I still can't see the scanner as a normal user. Is this what you were recommending I do? Did I miss a step?
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kenneth Schneider wrote:
On Sat, 2007-06-09 at 11:49 -0400, Bob Kline wrote:
1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner
At this point if the correct scanner is selected (I don't recall you mentioning the brand/model)
It's a Canon CanoScan LiDE30
just click on finish.
Actually, the instructions on the left say "To set up a new scanner, choose the scanner from the list of detected scanners and press *Edit*" which is why I did just that.
And as it has been suggested by someone else check that you don't have the permissions set to strict in /etc/sysconfig/security.
I don't.
Also check /etc/sane.d/dll.conf and make sure you model is uncommented (remove the # character from the start of the line).
Yes, checked that, too. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Ross used an electric tatoo kneadle on a coconut: Bob Kline wrote:
Kenneth Schneider wrote:
On Sat, 2007-06-09 at 11:49 -0400, Bob Kline wrote:
1. disconnected the scanner 2. logged on with my normal user account 3. started YaST 4. gave it the root password 5. invoked the scanner configuration screen 6. deleted the entry for the scanner and clicked Finish 7. shut down YaST 8. re-connected the scanner 9. started YaST again 10. gave it the root password 11. invoked the scanner screen again 12. YaST detected the scanner
At this point if the correct scanner is selected (I don't recall you mentioning the brand/model)
It's a Canon CanoScan LiDE30
just click on finish.
Actually, the instructions on the left say "To set up a new scanner, choose the scanner from the list of detected scanners and press *Edit*" which is why I did just that.
And as it has been suggested by someone else check that you don't have the permissions set to strict in /etc/sysconfig/security.
I don't.
Also check /etc/sane.d/dll.conf and make sure you model is uncommented (remove the # character from the start of the line).
Yes, checked that, too.
An off the wall IDEa ........... Did the scanner manufacturer issue any firmware updates, and did you get them ??? Iff the driver, etc. software assumes you have the by now old firmware update......... ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Ross wrote:
An off the wall IDEa ........... Did the scanner manufacturer issue any firmware updates, and did you get them ??? Iff the driver, etc. software assumes you have the by now old firmware update......... ;-)
I'll look into that if you really think missing firmware updates would be able to cause the inability of normal users to see the scanner. But remember, SuSE recognizes the scanner perfectly, and I can scan documents with it flawlessly, *as long as I am logged in as root*. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Kline wrote:
John Ross wrote:
An off the wall IDEa ........... Did the scanner manufacturer issue any firmware updates, and did you get them ??? Iff the driver, etc. software assumes you have the by now old firmware update......... ;-)
I'll look into that if you really think missing firmware updates would be able to cause the inability of normal users to see the scanner. But remember, SuSE recognizes the scanner perfectly, and I can scan documents with it flawlessly, *as long as I am logged in as root*.
I'm wrong then JRR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Saturday 09 June 2007 07:00, Bob Kline wrote:
I log into the machine as root,
Bob,
normal way is to log in as user, start YaST give root password and configure hardware.
What is the difference? Taking that very few people have this kind of problem, and very few people log in GUI as root [1], this is probable scenario how the setup works.
YaST setup is trying to configure equipment so that normal user can operate it. It can see your normal group called users and set all permissions as appropriate, but if you are logged in as root than it will be all set that only root can operate equipment.
Why this is good solution? It makes possible to change normal user group to anything you want for any reason, and setup utility will still work. Even if you want to set some device to be operated only by root the setup will work without glitch, but normal users will be out.
[1] To limit number of problems that can arise from buggy software, use of root account should be limited to well tested applications.
If user is logged in as root than whole set of applications available in GUI is ran with root access rights and chance to make damage is much greater than with present solution ie. regular way to log as normal user and grant root access only to YaST and few tools.
Rajko, can you certify this is the Yast working? I have never seen that documented. If true, it should be worth a wiki page by itself :-)) jdd -- http://www.dodin.net http://gourmandises.orangeblog.fr/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 June 2007 11:09, jdd wrote:
Rajko, can you certify this is the Yast working? I have never seen that documented.
Me neither. It was just a guess under presumption: "Taking that very few people have this kind of problem, and very few people log in GUI as root [1]", which is more fuzzy logic or in other words tapping in the dark ;-)
If true, it should be worth a wiki page by itself :-))
:-) Even if device setup doesn't work this way it will be worth to explain how it works. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Jun 9 08:00 Bob Kline wrote (shortened):
I log into the machine as root, run yast2, click on Hardware, then Scanners, and I see it run through an unattended checklist ending with "Detecting USB and SCSI scanners" after which it shows a line with "plustek Canon N1240U/LiDE30 at plustek:libusb:007:002". If I click on Other ... Restart Detection I end up with the same display. If I click Other ... Test I hear the hardware make some noises and a bunch of tests are listed and all marked as OK. If I then log into the machine as a normal user and run xsane I end up with the "No devices available" message. Am I missing a step in YAST?
No. It looks all well. Guess what: I have exactly such a Canon N1240U/LiDE30 here for testing and it always worked and works well for me, of course including "out-of-the-box" access as normal user. Therefore I cannot reproduce it and it is something very special why it doesn't work for you. All I can do is to provide some background information how the udev/HAL/resmgr machinery currently (for openSUSE 10.2) works: YaST sets scanner access permissions by calling /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which checks if the scanner is already listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi and if not it writes /etc/hal/fdi/policy/10osvendor/80-scanner.fdi to set up HAL to trigger resmgr to grant access for normal users. For some background information have a look at https://bugzilla.novell.com/show_bug.cgi?id=218393 in particular start at comment #19. Don't get confused by "sane-dev", it was used for SCSI scanners. You may check the following: Note the USB IDs for vendor and model in the "lsusb" output. E.g. my Canon LiDE 30 is listed this way: --------------------------------------------------------------------- Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 --------------------------------------------------------------------- Check if those USB IDs are in your /etc/hal/fdi/policy/10osvendor/70-scanner.fdi or at least in your /etc/hal/fdi/policy/10osvendor/80-scanner.fdi E.g. in my 70-scanner.fdi there is --------------------------------------------------------------------- <match key="info.category" string="usbraw"> <match key="@info.parent:usb_device.vendor_id" int="0x04a9"> <match key="@info.parent:usb_device.product_id" int="0x220e"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> --------------------------------------------------------------------- This way via udev and HAL the resmgr will be notified that this USB device is a scanner so that resmgr will set an appropriate ACL on its device file. Accordingly /usr/sbin/hal-resmgr --list shows my Canon LiDE 30 as ---------------------------------------------------------------------- UDI /org/freedesktop/Hal/devices/usb_device_4a9_220e_noserial_usbraw Device /dev/bus/usb/001/003 Class scanner ---------------------------------------------------------------------- and getfacl /dev/bus/usb/001/003 shows the actual ACL on the scanner's device file ---------------------------------------------------------------------- getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/003 # owner: root # group: root user::rw- user:jsmeix:rw- group::r-- mask::rw- other::r-- ---------------------------------------------------------------------- i.e. my normal user "jsmeix" has "rw" permissions. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johannes Meixner wrote:
All I can do is to provide some background information how the udev/HAL/resmgr machinery currently (for openSUSE 10.2) works:
YaST sets scanner access permissions by calling /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which checks if the scanner is already listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi and if not it writes /etc/hal/fdi/policy/10osvendor/80-scanner.fdi to set up HAL to trigger resmgr to grant access for normal users. For some background information have a look at https://bugzilla.novell.com/show_bug.cgi?id=218393 in particular start at comment #19. Don't get confused by "sane-dev", it was used for SCSI scanners.
Tried to follow this, though I don't pretend to understand all of it. I guess the part I really need to understand if I'm to make any further headway is the bit about how the script "sets scanner access permissions"; it's still muddy after looking at the .fdi files how the presence of my scanner in one of them will "trigger resmgr to grant access for normal users"; I don't see anything in the XML which seems related to specifying who gets to see what. Is there a HOWTO explaining how all of this stuff works for mortal users (rather than systems administrators)?
You may check the following:
Note the USB IDs for vendor and model in the "lsusb" output. E.g. my Canon LiDE 30 is listed this way: --------------------------------------------------------------------- Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 ---------------------------------------------------------------------
Right -- different bus and device numbers, of course, but the hardware ID is identical to yours.
Check if those USB IDs are in your /etc/hal/fdi/policy/10osvendor/70-scanner.fdi or at least in your /etc/hal/fdi/policy/10osvendor/80-scanner.fdi E.g. in my 70-scanner.fdi there is --------------------------------------------------------------------- <match key="info.category" string="usbraw"> <match key="@info.parent:usb_device.vendor_id" int="0x04a9"> <match key="@info.parent:usb_device.product_id" int="0x220e"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> ---------------------------------------------------------------------
OK, I've got that block in 70-scanner.fdi.
This way via udev and HAL the resmgr will be notified that this USB device is a scanner so that resmgr will set an appropriate ACL on its device file.
That's the part that doesn't work on my system. So perhaps the presence of my scanner in the .fdi file is necessary, but not sufficient.
Accordingly /usr/sbin/hal-resmgr --list shows my Canon LiDE 30 as ---------------------------------------------------------------------- UDI /org/freedesktop/Hal/devices/usb_device_4a9_220e_noserial_usbraw Device /dev/bus/usb/001/003 Class scanner ----------------------------------------------------------------------
That command's output is empty here.
and getfacl /dev/bus/usb/001/003 shows the actual ACL on the scanner's device file ---------------------------------------------------------------------- getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/003 # owner: root # group: root user::rw- user:jsmeix:rw- group::r-- mask::rw- other::r-- ---------------------------------------------------------------------- i.e. my normal user "jsmeix" has "rw" permissions.
$ getfacl /dev/bus/usb/007/001 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/007/001 # owner: root # group: users user::rw- group::r-- other::r-- Thanks for your assistance, Johannes. Never saw a shell script that parsed and wrote XML before. Very impressive. :-) -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Jun 13 16:55 Bob Kline wrote (shortened):
Johannes Meixner wrote:
You may check the following:
Note the USB IDs for vendor and model in the "lsusb" output. E.g. my Canon LiDE 30 is listed this way: --------------------------------------------------------------------- Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 ---------------------------------------------------------------------
Right -- different bus and device numbers, of course, but the hardware ID is identical to yours.
Check if those USB IDs are in your /etc/hal/fdi/policy/10osvendor/70-scanner.fdi or at least in your /etc/hal/fdi/policy/10osvendor/80-scanner.fdi E.g. in my 70-scanner.fdi there is --------------------------------------------------------------------- <match key="info.category" string="usbraw"> <match key="@info.parent:usb_device.vendor_id" int="0x04a9"> <match key="@info.parent:usb_device.product_id" int="0x220e"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> ---------------------------------------------------------------------
OK, I've got that block in 70-scanner.fdi.
This way via udev and HAL the resmgr will be notified that this USB device is a scanner so that resmgr will set an appropriate ACL on its device file.
That's the part that doesn't work on my system. So perhaps the presence of my scanner in the .fdi file is necessary, but not sufficient.
Accordingly /usr/sbin/hal-resmgr --list shows my Canon LiDE 30 as ---------------------------------------------------------------------- UDI /org/freedesktop/Hal/devices/usb_device_4a9_220e_noserial_usbraw Device /dev/bus/usb/001/003 Class scanner ----------------------------------------------------------------------
That command's output is empty here.
and getfacl /dev/bus/usb/001/003 shows the actual ACL on the scanner's device file ---------------------------------------------------------------------- getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/003 # owner: root # group: root user::rw- user:jsmeix:rw- group::r-- mask::rw- other::r-- ---------------------------------------------------------------------- i.e. my normal user "jsmeix" has "rw" permissions.
$ getfacl /dev/bus/usb/007/001 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/007/001 # owner: root # group: users user::rw- group::r-- other::r--
Now it is at least clear that the reason is something in the udev/HAL/resmgr machinery and - Thank God! - I am no expert here ;-) I assume you already tried a reboot with the scanner connected to the system? If I noticed correctly you can currently scan as normal user via running the saned (and the net backend) on your local host. Therefore there is currently no real loss of functionality. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johannes Meixner wrote:
I assume you already tried a reboot with the scanner connected to the system?
More than once. Did absolutely no good.
If I noticed correctly you can currently scan as normal user via running the saned (and the net backend) on your local host. Therefore there is currently no real loss of functionality.
True, though it makes me a little nervous when something's broken with no explanation. And I have to wonder how many users who aren't willing to hack obscure conf files just walk away from SuSE/Linux in despair.
Kind Regards Johannes Meixner
Thanks very much for your help and suggestions, Johannes. I eventually invoked the ultimate solution: I wiped the disk and re-installed SuSE from scratch. Felt a little like the old days with Windows, but it succeeded: scanning as a normal user worked out of the box. Only difference in the installations (that I'm aware of) was that I picked KDE instead of Gnome as the desktop. Hard to believe that's related, but who knows? One side benefit of the switch to KDE is that I was able to uninstall the beagle packages; under Gnome the dependencies were so intertwined with everything else that it just wasn't feasible to remove beagle. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Jun 14 08:43 Bob Kline wrote (shortened):
... it makes me a little nervous when something's broken with no explanation.
Welcome to the wonderful world of full automated USB device magic ;-)
... I wiped the disk and re-installed SuSE from scratch. Felt a little like the old days with Windows, but it succeeded: scanning as a normal user worked out of the box. Only difference in the installations (that I'm aware of) was that I picked KDE instead of Gnome as the desktop.
For me it worked and works regardless of which desktop I installed. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 08 June 2007 14:35, Bob Kline wrote:
Bonus question (I know, asking two questions in one post lowers the chance of getting an answer to either one, but I'll risk it): any way to get Linux to respond to the buttons on the front of the scanner (Canon CanoScan LIDE30)? I'm in a good mood...
... http://gentoo-wiki.com/Scanner_buttons_and_one-touch_scanning -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 08 June 2007 14:35, Bob Kline wrote:
I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions. I found your answer...
... check section 5.3 of this FAQ: http://www.xs4all.nl/~ljm/SANE-faq.html#46 -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
On Friday 08 June 2007 14:35, Bob Kline wrote:
I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions. I found your answer...
... check section 5.3 of this FAQ:
Thanks for your reply. I've looked at this FAQ. It says: [[[ start quote ]]] scanimage -L This will give you the name of the device. For example: [ljm@ronsard ~]$ scanimage -L device `umax:/dev/sgd' is a UMAX Astra 1220S flatbed scanner [ljm@ronsard ~]$ The /dev/sgd is the name of the device. [[[ end quote ]]] In my case, the output of scanimage -L is device `plustek:libusb:007:002' is a Canon N1240U/LiDE30 USB flatbed scanner which doesn't give me a name of a file but is using some other syntax. The answer to the FAQ goes on to talk about finding the lines in the file /etc/security/console.perms and commenting them out. There is no such file in my /etc/security directory. In fact, I've looked at every file that is in that directory, and almost none of the non-empty lines in any of the files are uncommented to start with, and I promise that none of the ones which aren't commented make any reference to the scanner. Then the FAQ talks about "users of the device filesystem" and "/etc/devfs/perms" which I assume doesn't apply to this installation of SuSE, as /etc/devfs doesn't exist. The FAQ ends with "For USB scanner, have a look at the USB-section." So I did. That section starts of by talking about using chmod on files in /proc/bus/usb. I don't have any files there, and that's not a durable solution anyway ("the permissions will be reset when the scanner is replugged or Linux is rebooted"). Then: "One solution to set permissions on-the-fly are the Linux hot-plug tools that should come with any current distribution. SANE itsself comes with a hotplug script and related documentation in the tools/hotplug/ directory. Please refer to the README in that directory for the details. You might also wish to browse through the documentation for the Plustek; it has quite a nice section on how to set-up your USB access. /usr/share/doc/sane-backends-*/plustek/Plustek-USB.txt" I don't see any evidence that the statement about SANE including hotplug tools is actually true: $ rpm -qa | grep -i sane xsane-0.991-32 sane-frontends-1.0.14-44 sane-1.0.18-34 $ rpm -ql sane | grep -i hotplug $ rpm -ql sane-fontends | grep -i hotplug $ rpm -ql xsane | grep -i hotplug $ man hotplug No manual entry for hotplug I'm **way** out of my systems administration here. :-( -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Kline wrote:
Thanks for your reply. I've looked at this FAQ. It says: ....
Sorry for the typos.
That section starts of by ....
Read: "That section starts off by ...."
I'm **way** out of my systems administration here. :-(
Read: "... out of my systems administration depth ...." Cheers, -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Jun 08, 2007 at 03:35:14PM -0400, Bob Kline wrote:
I've done some searching around to find out why I can only use the scanner as root on a machine on which I've just installed SuSE 10.2 (i386). (Didn't have this problem under Fedora, though plenty of other problems that switching to SuSE solved.)
I've found some older postings (latest is 10.0 vintage) with general advice about getting scanners configured. Some advise manual tweaking of settings in the /etc/sane.d files (which I've tried). Others say it's better to just bring up YaST and run the configuration from there (tried that, too). Neither worked. I can scan until the cows come home as root but a regular user account gets the dreaded "no devices found" error message. Amusingly, when I run xsane as a regular user and the "No devices available" dialog window pops up, there is a "Help" button; when I push it, I see "Possible reasons: ... the permissions for the device file do not allow you to use it - try as root"; then when I run xsane as root up pops "Warning. You try to run XSane as ROOT, that really is DANGEROUS!! Do not send any bug reports when you have any problem while running XSane as root: YOU ARE ALONE! ... [Cancel] ... [Continue at your own risk]."
I've tried chmod on the /dev files, but that doesn't stick. I'm not surprised: I assume that the device files are set up on the fly, but I don't know how to control the permissions.
Can I get a clue, please? I'm perfectly prepared to take some razzing about how easy it should have been for me to find this information on my own, but I really did try some googling, just didn't pick the right magic combination of keywords.
If you let it get autodetected and configured by YAST, then it the permissions should be set up correctly. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (10)
-
Bob Kline -
Carlos E. R. -
jdd -
Johannes Meixner -
John Ross -
Kenneth Schneider -
M Harris -
Marcus Meissner -
Patrick Shanahan -
Rajko M.