https://bugzilla.novell.com/show_bug.cgi?id=387555 Summary: yast2-scanner: better user info if the net backend hangs up Product: openSUSE 11.0 Version: Beta 2 Platform: All OS/Version: openSUSE 11.0 Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: jsmeix@novell.com ReportedBy: jsmeix@novell.com QAContact: jsrain@novell.com Found By: Development When the net backend is activated and something is wrong in the network (e.g. a remote saned server for the local running net backend does not respond at all) there are very long limeouts or it may just hang up. Therefoere there is already a 60 seconds timeout with a time-bomb in /usr/lib/YaST2/bin/determine_active_scanners so that yast2-scanner does not hang up completely. But if the time-bomb kills determine_active_scanners the result is an empty list of active scanners even if other backends for locally connected scaners would work but cannot because the net backend blocks all which is therefore technically corect but looks wrong for the unexperienced user. What is missing is a better user information when the net backend is activated and such timeouts happen in particular with a hint that an unexpected epmty list of active scanners might be caused by problems with the net backend so that it might help to disable the net backend. -- 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.