[Bug 223875] New: scanning only working for root (yast/sane/kooka/SuSEconfig)
https://bugzilla.novell.com/show_bug.cgi?id=223875 Summary: scanning only working for root (yast/sane/kooka/SuSEconfig) Product: openSUSE 10.2 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sinderbox+novell@gmail.com QAContact: jsrain@novell.com This bug exists for several weeks at least. Reinstalled my scanner with latest yast Normaluser> 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 kernel SCSI driver for your SCSI adapter. [chopped] root> 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. found SCSI processor "EPSON SCANNER GT-7000 1.14" at /dev/sg2 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read the backend's manpage. [chopped] ls -l /dev/sg2 crw-r----- 1 root disk 21, 2 Nov 27 15:14 /dev/sg2 ======================================= Of course, if I do the following the problem is solved: chmod 660 /dev/sg2 chgrp dialout /dev/sg2 crw-rw---- 1 root dialout 21, 2 Nov 27 15:14 /dev/sg2 Normaluser> 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. found SCSI processor "EPSON SCANNER GT-7000 1.14" at /dev/sg2 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read the backend's manpage. [chopped] --------------------- I guess SUSE 10.2 cannot be released without a working scanning system. Set the severity to blocker. I wonder, no one has encountered this problem before? Every time I upgrade to the latest beta, my scanner permissions are overwritten with non working ones (by SuSEconfig I presumed). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Major Status|NEW |NEEDINFO Info Provider| |sinderbox+novell@gmail.com ------- Comment #1 from mhorvath@novell.com 2006-11-27 12:14 MST ------- Please attach your yast log files and output of the 'hwinfo --scanner' (as root, while your scanner is connected). http://en.opensuse.org/Bugs/YaST Thank you -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #2 from sinderbox+novell@gmail.com 2006-11-27 14:11 MST ------- # hwinfo --scanner 23: SCSI 401.0: 10c04 Scanner [Created at scsi.1546] UDI: /org/freedesktop/Hal/devices/pci_9004_5078_scsi_device_lun0_scsi_generic Unique ID: olmp.NBRjDO9kTJ5 Parent ID: hH_P.WsvlrmNH3M8 SysFS ID: /class/scsi_generic/sg2 SysFS BusID: 4:0:1:0 Hardware Class: scanner Model: "EPSON SCANNER GT-7000" Vendor: "EPSON" Device: "SCANNER GT-7000" Revision: "1.14" Driver: "aic7xxx" Driver Modules: "aic7xxx" Device File: /dev/sg2 Device Number: char 21:2 Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #20 (SCSI storage controller) I will attach y2logs, however it will probably not help since after removing my scanner with yast and installing it again, the permissions for /dev/sg2 remain as I artificially set them. # ls -l /dev/sg2 crw-rw---- 1 root dialout 21, 2 Nov 27 15:14 /dev/sg2 after a massive system upgrades it returns to crw------- 1 root disk ,,,, so I cannot be certain which package resets the permissions. Probably sane. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #3 from sinderbox+novell@gmail.com 2006-11-27 14:12 MST ------- Created an attachment (id=107099) --> (https://bugzilla.novell.com/attachment.cgi?id=107099&action=view) yast logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|meissner@novell.com | AssignedTo|bnc-team- |jsmeix@novell.com |screening@forge.provo.novell| |.com | Status|NEEDINFO |NEW Info Provider|sinderbox+novell@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sinderbox+novell@gmail.com ------- Comment #4 from jsmeix@novell.com 2006-11-29 01:37 MST ------- 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, see bug #218393 for background information. Regarding YaST, attach /etc/hal/fdi/policy/10osvendor/80-scanner.fdi as mime type "text plain" to this bug. Regarding HAL, do as root lshal >/tmp/lshal.out and attach /tmp/lshal.out as mime type "text plain" to this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #5 from jsmeix@novell.com 2006-11-29 01:57 MST ------- Additionally change in /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions the line #set -x to set -x and run it as follows (type it on one single command line) ------------------------------------------------------------------------------- /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions \ 'epkowa:/dev/sg2;unknown;' &>/tmp/test_and_set_scanner_access_permissions.out ------------------------------------------------------------------------------- and attach /tmp/test_and_set_scanner_access_permissions.out as mime type "text plain" to this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #6 from jsmeix@novell.com 2006-11-29 02:15 MST ------- Created an attachment (id=107339) --> (https://bugzilla.novell.com/attachment.cgi?id=107339&action=view) /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions I have an idea what might cause the problem. Therefore here a new version of /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which might solve the problem. Please test this one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #7 from jsmeix@novell.com 2006-11-29 06:55 MST ------- Submitted yast2-scanner with the fix according to attachment #107339 to STABLE. Regardless whether it solves the problem in this bug, there was a bug in test_and_set_scanner_access_permissions which is now fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|sinderbox+novell@gmail.com | Resolution| |FIXED ------- Comment #8 from jsmeix@novell.com 2006-12-04 02:17 MST ------- Got no info. Therefore I assume it is fixed (see comment #6). Additionally have a look at https://bugzilla.novell.com/show_bug.cgi?id=218393#c26 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 sinderbox+novell@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #9 from sinderbox+novell@gmail.com 2006-12-07 14:22 MST ------- I am sorry I couldn't follow up. It still doesn't work. I next comment I provide the requeste info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #10 from sinderbox+novell@gmail.com 2006-12-07 14:24 MST ------- Created an attachment (id=108769) --> (https://bugzilla.novell.com/attachment.cgi?id=108769&action=view) 80-scanner.fdi -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #11 from sinderbox+novell@gmail.com 2006-12-07 14:25 MST ------- Created an attachment (id=108770) --> (https://bugzilla.novell.com/attachment.cgi?id=108770&action=view) lshal.out -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #12 from sinderbox+novell@gmail.com 2006-12-07 14:27 MST ------- Created an attachment (id=108771) --> (https://bugzilla.novell.com/attachment.cgi?id=108771&action=view) test_and_set_scanner_access_permissions.out -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 sinderbox+novell@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #108771|application/octet-stream |text/plain mime type| | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 ------- Comment #13 from sinderbox+novell@gmail.com 2006-12-07 14:30 MST ------- device permissions were again reset. # l /dev/sg2 crw-r----- 1 root disk 21, 2 Dec 7 08:18 /dev/sg2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=223875 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #14 from jsmeix@novell.com 2006-12-08 02:00 MST ------- Attachment #108771 shows that you still use the old /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which doesn't work in your particular case. Therefore I made the fix according to comment #6 which is included in the openSUSE 10.2 final version. Obviously you must update it (either with attachment #107339 or install the openSUSE 10.2 final version). Therefore I still think it is fixed. If it doesn't work even with attachment #107339 or with the openSUSE 10.2 final version, it might be a duplicate of bug #226044 In problematic cases there is always the following workaround: YaST scanner config: -> [Other] -> "Scanning via Network" -> [Local Host Configuration] -> [Next] -> [Finish] See http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 in the "ibusb + resmgr + PAM" section the info about "saned". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com