On Tue 12 Jul 2016 at 15:59:35 +0200, peekaa wrote: > Dne 12.7.2016 v 12:55 Brian napsal(a): > > You are right. First run OK, any other run gives: > $ scanimage -L > > No scanners were identified. If you were expecting something different, > check that the scanner is plugged in, turned on and detected by the > sane-find-scanner tool (if appropriate). Please read the documentation > which came with this software (README, FAQ, manpages). > > "no scanner frontend will work reliably " - what does it mean? Means that > we can not scan if we need? Or do we have just "give a try"? :-(
We hope not. But we can only try and see. > >If you get this again as a user please post the last few lines shown by > >'journalctl'. > > here: > > čec 12 15:52:15 linuxbox /usr/lib/gdm3/gdm-x-session[12322]: Activating > service name='org.gnome.Terminal' > čec 12 15:52:15 linuxbox /usr/lib/gdm3/gdm-x-session[12322]: Successfully > activated service 'org.gnome.Terminal' > čec 12 15:52:15 linuxbox org.gnome.Shell.desktop[12415]: Gjs-Message: JS > LOG: [pixel-saver]: Can't find original state for dady@linuxbox: ~ with id > 0x1a000 > čec 12 15:52:15 linuxbox org.gnome.Shell.desktop[12415]: > (gnome-shell:12415): Gtk-WARNING **: Allocating size to ShellEmbeddedWindow > 0x36787d0 without call > čec 12 15:53:32 linuxbox scanimage[12734]: io/hpmud/pp.c 627: unable to read > device-id ret=-1 Would see what comes up in the log with searches for "usbfs" and "claimed"?
