Hello, On Nov 6 11:28 Jason Craig wrote (shortened): > Johannes Meixner wrote: > > On Nov 1 14:46 Jason Craig wrote: > > > >> I recently upgraded from 10.2 to 10.3 and now my HP PSC2350 scanner no > >> longer > >> works. In GIMP, when I go to acquire, nothing happens. When I went to go > >> check on settings in YaST, when I go to "Scanners" it leaves me with an > >> error > >> of "Cannot build driver database". Anyone have ideas? > >> > > > > Was it "Aborting: Failed to create the scanner database."? > > If yes, the comment in the YaST sources is: > > > Yes, sorry :) > > ----------------------------------------------------------------- > > Only a simple message because this error does not happen > > on a normal system (i.e. a system which is not totally broken > > or totally messed up). > > ----------------------------------------------------------------- > > ;-) ... > At first the result was a message saying "missing sane-backends" so I > fired up the package manager and installed "sane-backends", which at the > same time removed "sane" (I figure the system knows what it's doing). > After that this command worked fine and /tmp/database was filled with a > driver database. Also, the Scanner section of YaST no longer complains,
It is strange why you have to install it manually because the YaST scanner module tests if sane-backends is installed and if not, it tries to install it and if it fails to install, the YaST scanner module should abort. It is perfectly o.k. that "sane" is replaced by "sane-backends" because the package "sane" was renamed to "sane-backends" so that now we use the same name as the rest of the world which is in compliance to the original name of the SANE project. The scaner database is created from scanner description files in the sane-backends package. Because the YaST scanner module tests and installs sane-backends first of all and aborts if this fails, it should be impossible that the YaST scanner module tries to create the database without having sane-backends installed. I wonder how it happened on your system that the YaST scanner module tried to create the database without having sane-backends installed. > but it does now display two scanners; one driver: "not configured" HP > PSC2350 series and one driver: "hpaio" Hewlet Packard PSC_2350_series. See https://bugzilla.novell.com/show_bug.cgi?id=220276 > Testing the hpaio scanner works, attempting to delete (or test) the not > configured scanner doesn't work and GIMP still does not work when I do > File->Acquire->xscanimage->Device Dialog... > > xscanimage from the command line as root works like a charm, but from > user level it complains that no scanners were identified. ... > but a shutdown and later restart seemed to do the system well. > All seems fine now. The reboot (more precisely the restart of the udev/HAL/hal-resmgr machinery) is needed in your case because of https://bugzilla.novell.com/show_bug.cgi?id=218393#c28 In your case the YaST scanner module added an entry to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi to grant normal user access via the udev/HAL/hal-resmgr machinery but HAL doesn't notice a changed fdi file. Even a unplug of the device from the USB and re-plug doesn't help because HAL wouldn't apply the new rules from the changed fdi file because HAL didn't notice the changed fdi file. Only a restart of the udev/HAL/hal-resmgr machinery helps. Usually "rchal restart" should be sufficient but who knows all those dependencies in the udev/HAL/hal-resmgr machinery for each particular case so that the easiest "solution" is a nice reboot - just like in those other well known operating system ;-) By the way: I will not do an automated "rchal restart" in the YaST scanner module because this does a complete shutdown and restart of the complete HAL system which has unexpected side-effects on whatever devices like USB mass storage devices and whatever-else-there-is-in-HAL. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
