I was hoping that the logs would have some obvious, Google-able error. The only one I see is "Did not find alt setting 1 for intf 0, config 1". I googled that and found this:
Which is a very long and technical thread from last March, debugging what looks like the same issue. In this case, the guy can't print from his HP printer, sees "Did not find alt setting 1 for intf 0, config 1" in the logs, and finds that reverting to an earlier kernel allows him to print.
I also found a similar issue here: https://bugs.launchpad.net/ubuntu/+sour … bug/899746
Sadly neither thread has a quick fix. Maybe you'll have better luck googling for that error.
My only suggestion for now, which you've probably already tried, is making sure you have the latest updates. It seems like this issue was introducted in a kernel update, and may or may not have been fixed since then. So either a very new kernel, or a very old kernel, might allow you to print.
I was thinking you could look only at the logs that appear immediately upon plugging in the scanner. That will be a lot easier to look at than the entire syslog file.
Run `tail -f /var/log/syslog` in a terminal, then plug in the scanner. You should see some text in the terminal about initializing the device. There might be some clues in that text. Then try to perform a scan and see if anything else interesting shows up.
You could also try running `lsusb` to see if the scanner is listed as a recognized usb device.
Using UNetbootin to extract the #! Lite ISO to a flash drive was a cinch. The rest of the installation was effortless.
Thank you #! team, for rekindling my love of my Eee! I plan to be switching my workstation, home desktop, and my more-normally-sized laptop to #! very soon.