https://bugzilla.novell.com/show_bug.cgi?id=720222 https://bugzilla.novell.com/show_bug.cgi?id=720222#c1 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jsmeix@suse.com InfoProvider| |bruno@ioda-net.ch --- Comment #1 from Johannes Meixner 2011-09-27 10:33:49 UTC --- Nothing was changed in yast2-scanner or in sane-backends so that the root cause why it does no longer work is somewhere else. Please provide debugging information according to "Trouble-Shooting (Debugging)" in http://en.opensuse.org/SDB:Configuring_Scanners For background information how scanning with SANE works, you may have to read the whole article. Regarding third-party drivers: The YaST2 scanner module cannot support third-party scanner drivers because there is no defined way in SANE how third-party scanner driver software must install so that generic scanner setup software (like the YaST2 scanner module) could support it. But such support is usually not needed because: Basically a third-party scanner driver software which works in compliance with SANE would add its driver name during installation to /etc/sane.d/dll.conf so that its driver is activated and then the driver would work, see "SANE Backends" at http://en.opensuse.org/SDB:Configuring_Scanners In your case check if the driver is listed in /etc/sane.d/dll.conf so that the driver is activated and then check if "scanimage -L" (run it as root and as normal user) finds the scanner. If "scanimage -L" (when run as root) does not find the scanner, it is the driver which does no longer find the scanner which means that the driver does no longer work. It would not help if YaST supports the third-party scanner driver because all what YaST could do is to activate the driver in /etc/sane.d/dll.conf but YaST cannot fix a driver which is activated but does not work. If the issue is in the third-party driver, we cannot do anything here. We neither have such a printer/scanner model to reproduce it nor do we test third-party drivers nor do we provide support for third-party drivers. If the issue is in the third-party driver, the bug report is "invalid" for us. In this case please contact those wherefrom you got the third-party driver for help and support. If the third-party driver is proprietary software (i.e. when it contains parts which are proprietary software) nobody - except the authors of the proprietary software - can provide support for such kind of software because nobody - except the authors - know how their proprietary software works. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=720222 https://bugzilla.novell.com/show_bug.cgi?id=720222#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Other AssignedTo|jsmeix@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa@suse.de --- Comment #2 from Johannes Meixner 2011-09-27 14:15:14 UTC --- Why is it assigned to me whe nothing was changed in yast2-scanner or in sane-backends so that the root cause why it does no longer work is somewhere else? I change component to "Other" and "Reset Assignee and QA to default". -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=720222 https://bugzilla.novell.com/show_bug.cgi?id=720222#c3 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bruno@ioda-net.ch | --- Comment #3 from Bruno Friedmann 2011-09-27 15:35:24 UTC --- Ok fixed, this is due to a malfunctionning rpm proposed by brother (don't find the why). It miss the part of pushing the dirver inside /etc/sane.d/dll.conf Can be easily fixed by doing sudo /usr/local/Brother/sane/setupSaneScan2 -i Sorry for the noise, this was working before, and I've feared about a regression somewhere. -- 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.