On Monday 22 November 2004 15:27, Johannes Meixner wrote:
Hello,
On Nov 22 14:42 Fergus Wilde wrote (shortened):
Kooka works ... as root ... But will not work as user.
USB scanner access for normal users should work well since 9.2, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html
Hi Johannes - thanks for the link. My scanner isn't working out of the box for regular users, certainly: the problem seems to be soluble by changing the ownership of the proc files: pc11:/home/fergus # ls -l /proc/bus/usb/001/* -rw-r--r-- 1 root root 43 2004-11-23 08:34 /proc/bus/usb/001/001 -rw-r--r-- 1 root root 50 2004-11-23 08:37 /proc/bus/usb/001/002 and after I do pc11:/home/fergus # chown fergus:users /proc/bus/usb/001/* I can then access the scanner via Kooka just fine. So something about the PAM / resmgr part of the setup isn't working right in the default install? Here's /var/log/messages while I start kooka as a user before modifying permissions of the above files: Nov 23 08:36:29 pc11 kooka: resmgr: server response code 502 Nov 23 08:36:29 pc11 last message repeated 8 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:29 pc11 last message repeated 2 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:29 pc11 last message repeated 3 times Nov 23 08:36:29 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 2 times Nov 23 08:36:30 pc11 kooka: resmgr: communication failure: Broken pipe Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 4 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 4 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:36:30 pc11 last message repeated 3 times Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 501 Nov 23 08:36:30 pc11 kooka: resmgr: server response code 500 Nov 23 08:37:06 pc11 kernel: usb 1-2: bulk timeout on ep1in Nov 23 08:37:06 pc11 kernel: usb 1-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 And it doesn't work. Here's me starting kooka once I have modified the ownership of proc/bus/usb/001/*: things start ok for me and I can scan, but it takes about a minute and resmgr still looks unhappy: Nov 23 08:58:48 pc11 kooka: resmgr: server response code 502 Nov 23 08:58:48 pc11 last message repeated 8 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 2 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 4 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:58:48 pc11 last message repeated 3 times Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 501 Nov 23 08:58:48 pc11 kooka: resmgr: server response code 500 Nov 23 08:59:01 pc11 /usr/sbin/cron[5869]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Nov 23 08:59:18 pc11 kernel: usb 1-2: bulk timeout on ep1in Nov 23 08:59:18 pc11 kernel: usb 1-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -110 Nov 23 08:59:18 pc11 kernel: ehci_hcd 0000:00:1d.7: qh dde71180 (#17) state 1 despite the 'failed' message, I can still work ... but would have to manually reset ownership of these files each time I boot, or set things up to modify them in boot.local, or somewhere ... presumably this isn't the safe or cool way to do it. Any other thoughts? For now I am going to implement Miquel Noguera's suggestion of doing this in /etc/fstab to see if it fixes the problem: usbfs /proc/bus/usb usbfs defaults,devmode=0666 0 0 But I imagine this isn't as secure as what you outline in your support article. I don't think I know enough about PAM or resmgr to fix that without help though. Cheers Fergus
Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/