Hello, On Jun 13 11:30 A. den Oudsten wrote (shortened):
Johannes Meixner wrote:
On Jun 12 17:17 A. den Oudsten wrote (shortened):
I recently installed opensuse 10.2 and could scan via kooka, but only a few times Now I get every time when I start kooka the message 'no sane installed' Kooka, SANE and SANE-frontends are installed when I check with Yast
I guess it is https://bugzilla.novell.com/show_bug.cgi?id=141079
We cannot reproduce it. Sometimes kooka fails but later it works again. If someone can reliable reproduce it, it would be nice. ... Yesterday I checked, with Yast, if the scanner HP PSC 2110 was configured correctly. I was, and suddenly kooka worked perfectly. For me a mystery or a miracle; that I can't distinguish!! Meanwhile I have several times started kooka, but happily I can't reproduce the fault
Perhaps this one is related: In the YaST scanner setup I do an ugly workaround for a strange problem (Suse/Novell Bugzilla bug #75709 - an old internal bug report for Suse Linux 9.3): ------------------------------------------------------------------------ Symptoms (happens sometimes - not always): A) When starting the YaST scanner module, no scanner is autodetected. But after a simple abort and re-start of the YaST scanner module, the scanner is autodetected. B) After a backend was activated by the YaST scanner module, no matching active scanner is shown. But after a simple redo (i.e. activate the same backend again) or after finish and re-start of the YaST scanner module, the matching active scanner is shown. Background information: Regarding A): YaST calls "sane-find-scanner" to autodetect scanners. Sometimes "sane-find-scanner" doesn't autodetect a scanner. But a simple re-run of "sane-find-scanner" autodetects it. Regarding B): YaST calls "scanimage -L" to get the active scanners. Sometimes "scanimage -L" doesn't find the scanner. But a simple re-run of "scanimage -L" finds it. It never happened in the 9.2 environment. It happens only in the 9.3 environment. Obviously it is not a problem in YaST. I don't think it is a problem in "sane-find-scanner" or in "scanimage -L" because the sane package was not changed after I switched from 9.2 environment to 9.3 environment. I assume it is a problem somewhere in the hotplug/udev magic regarding USB devices but I have no idea what it might be. ------------------------------------------------------------------------ Up to now the reason is unknown. Therefore the scanner autodetection (i.e. "sane-find-scanner") is simply called a second time in YaST (after waiting 10 seconds) if it ran without errors but didn't detect a scanner on the first run. In this case you get the nice Welcome to the wonderful world of full automated USB device magic ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org