Johannes Meixner wrote:
I assume you already tried a reboot with the scanner connected to the system?
More than once. Did absolutely no good.
If I noticed correctly you can currently scan as normal user via running the saned (and the net backend) on your local host. Therefore there is currently no real loss of functionality.
True, though it makes me a little nervous when something's broken with no explanation. And I have to wonder how many users who aren't willing to hack obscure conf files just walk away from SuSE/Linux in despair.
Kind Regards Johannes Meixner
Thanks very much for your help and suggestions, Johannes. I eventually invoked the ultimate solution: I wiped the disk and re-installed SuSE from scratch. Felt a little like the old days with Windows, but it succeeded: scanning as a normal user worked out of the box. Only difference in the installations (that I'm aware of) was that I picked KDE instead of Gnome as the desktop. Hard to believe that's related, but who knows? One side benefit of the switch to KDE is that I was able to uninstall the beagle packages; under Gnome the dependencies were so intertwined with everything else that it just wasn't feasible to remove beagle. -- Bob Kline http://www.rksystems.com mailto:bkline@rksystems.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org