Mailinglist Archive: opensuse-factory (581 mails)

["Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Tuesday, 2008-12-02 at 11:43 +0100, Johannes Meixner wrote:


> 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.
> ---------------------------------------------------------------

That's the same thing I'm seing in 11.0 - with the exception that on Nov 
11 it worked (last scan I remember), and now it doesn't. Could be an 
update to something in the stack? I know I haven't changed anything 
myself in the configuration related to scanning...


> Compare
> https://bugzilla.novell.com/show_bug.cgi?id=438867#c3
> which points to
> https://bugzilla.novell.com/show_bug.cgi?id=340173
> where I describe a similar problem.


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:~ #


I can open a bugzilla if you want.


- -- 
Cheers,
       Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkk1ITsACgkQtTMYHG2NR9WXqACeJ5BqBab1OD0CbGG/1SZAfeAN
EUgAn3KjlqT5tRje9YSvrOpftDdUacod
=2XJX
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx