Bug 139188

Summary: USB scanner genius vivid 4 not configured for resmgr access
Product: [openSUSE] SUSE LINUX 10.0 Reporter: carlos tonussi <crtonussi>
Component: HotplugAssignee: Johannes Meixner <jsmeix>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: lnussel, meissner
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: system log
yast2 log

Description carlos tonussi 2005-12-14 21:56:11 UTC
Hi,
After updating to 10 from 9.3, sane failed to recognize my usb scanner genius vivid 4. All was ok in 9.3 (but updating sane to 1.0.16). Exploring the problem I found in sane pages that in some kernels of 2.6 series the /proc/bus/usb/xxx device receives only root permissions. In fact, sane only detected my scanner when I was as root or after chmod the specific usb device with users permissions. I think this may not be a bug of 2.6 kernels since I had no trouble in SUSE 9.3. This is somewhat annoying since I have to change such permissions everytime any user need to use scanner. I found in sane documentation a script to do this job everytime scanner is plugged, but I don“t tried to get it working. I would like to know why SUSE 10 don't manage this issue like 9.3.

best regards!
Comment 1 Marcus Meissner 2005-12-15 17:18:13 UTC
we use resmgr to provide permissions.

as user, run "/sbin/resmgr list" to see if it gets
the correct resmgr entry.

Comment 2 Ludwig Nussel 2005-12-15 17:27:32 UTC
Johannes has written nice instructions for setting up scanners:
http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html

The driver for your scanner probably doesn't provide sufficient information so YaST can't configure resmgr automatically.

Please attach yast2 logs and the output of sane-find-scanner
Comment 3 carlos tonussi 2005-12-16 16:59:23 UTC
Created attachment 61098 [details]
system log
Comment 4 carlos tonussi 2005-12-16 17:00:29 UTC
Created attachment 61099 [details]
yast2 log
Comment 5 carlos tonussi 2005-12-16 17:02:14 UTC
Comment on attachment 61098 [details]
system log

This log registered the detection of usb scanner and a pendrive in its last entries
Comment 6 carlos tonussi 2005-12-16 17:09:25 UTC
crtonussi@localhost:~> sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x0458, product=0x2014, chip=GT-6816?) at libusb:002:002
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
---------------------
resmgr list

crtonussi@localhost:~> /sbin/resmgr list
r--- /dev/console
rw-- /dev/adsp
rw-- /dev/audio
rw-- /dev/dsp
rw-- /dev/mixer
rw-- /dev/snd/controlC0
rw-- /dev/snd/pcmC0D0c
rw-- /dev/snd/pcmC0D0p
rw-- /dev/snd/pcmC0D1p
rw-- /dev/snd/pcmC0D2c
rw-- /dev/snd/pcmC0D2p
rw-- /dev/snd/seq
rw-- /dev/snd/timer
rw-- /dev/input/event2
rw-- /dev/hdc
rw-- /dev/fd0

-------------------------------
Thanks for your help! I'll be reading the page suggested above...
Comment 7 carlos tonussi 2005-12-16 17:55:18 UTC
Ok! All I needed to know was in that page. Yast assigned an entry in the resmgr.conf allowing my scanner. I was not running yast for scanner configuration because in SUSE 9.3 I managed to get scanner working manually.
Thank you very much guys!
Comment 8 Ludwig Nussel 2005-12-16 18:07:38 UTC
good. so no bug :-)