-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-12-02 at 12:39 +0100, Johannes Meixner wrote:
Hello,
On Dec 2 12:09 Carlos E. R. wrote (shortened):
I use 11.0, but I can't see that report:
The initial comment in this report is (shortened): --------------------------------------------------------------- configured scanner using control-center -> hardware -> scanner. test scan said ok.
$ xsane a popup flashes for 0.1sec: "scanning for devices" or similar then a popup 'no devices available' [close] [help]
One of the suggestions displayed by pressing the help button, is 'try as root'
xsane indeed works when called as root. ---------------------------------------------------------------
same thing, execept that I configured the scanner years ago, and on nov 11 it worked, and I have changed nothing. Could be an update to something in the stack? I know I haven't changed anything myself in the configuration related to scanning... nimrodel:~ # /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions The following models are currently not known to HAL: USB-ID(hex)=04b8:0110 To access the scanner as normal user, udev, HAL, and hal-resmgr are needed to grant appropriate access permissions automatically. Therefore the scanner model must be known to HAL. If the scanner is not known to HAL, a re-plug of a USB scanner should help. Otherwise a reboot should be done to restart the whole udev/HAL/hal-resmgr machinery. Check if the scanner is listed in the 'lshal' output. If a SCSI scanner which was switched on during boot is not listed in the 'lshal' output, the usual reason is that the kernel module for the scanner's SCSI host adapter does not notify HAL about the scanner device. If even a reboot does not help, you could access the scanner via the 'saned' as a workaround. For this workaround choose 'scanning via network' and select the 'local host configuration'. nimrodel:~ # (disconnect / connect usb cable, repeat) nimrodel:~ # /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions The following models are currently not known to HAL: USB-ID(hex)=04b8:0110 To access the scanner as normal user, udev, HAL, and hal-resmgr are needed to grant appropriate access permissions automatically. Therefore the scanner model must be known to HAL. If the scanner is not known to HAL, a re-plug of a USB scanner should help. Otherwise a reboot should be done to restart the whole udev/HAL/hal-resmgr machinery. Check if the scanner is listed in the 'lshal' output. If a SCSI scanner which was switched on during boot is not listed in the 'lshal' output, the usual reason is that the kernel module for the scanner's SCSI host adapter does not notify HAL about the scanner device. If even a reboot does not help, you could access the scanner via the 'saned' as a workaround. For this workaround choose 'scanning via network' and select the 'local host configuration'. nimrodel:~ # Notice that it says it knows nothing about my scanner - and this scanner worked a month ago. It looks like a regression of some kind. nimrodel:~ # lshal | grep -i scanner nimrodel:~ # lshal | grep -i epson info.vendor = 'Seiko Epson Corp.' (string) usb_device.vendor = 'Seiko Epson Corp.' (string) usb.vendor = 'Seiko Epson Corp.' (string) nimrodel:~ # There is nothing about "scanner". cer@nimrodel:~> getfacl /dev/bus/usb/003/007 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/003/007 # owner: root # group: lp user::rw- group::rw- other::r-- The above says I have permission as user. I can open a bugzilla if you want. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkk1KUwACgkQtTMYHG2NR9VgFACeKosD1zfAP7d7bkyl0fbjyckS lF0AoIQlS1xaRgihOmfQlOPIJd5gOyZa =ONNe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org