mikko, you are mostly correct! Deleting /home/<user>/.sane indeed makes Xsane start up correctly and run the scanner. However, if I close Xsane then start it again during the same session, the same hanging behaviour occurs. This repeats if I delete .sane again.
As far as I can tell, .sane is set to <user> access all the way through. I didn't check the individual files in /.sane/xsane/, so maybe I need to change some rights to a file in there. I believe this is a bug in xsane, both because it lets itself get hung while it should throw an error if it runs into a permissions proble, and because it appears to be creating a file or content that it cannot access afterwards. -- xsane does not start https://launchpad.net/bugs/47174 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
