On Sat, Oct 08, 2011 at 12:09:51PM +1100, Scott Ferguson wrote: > On 08/10/11 01:31, Thomas H. George wrote: > > On Fri, Oct 07, 2011 at 10:37:04AM +1100, Scott Ferguson wrote: > >> On 06/10/11 01:38, Thomas H. George wrote: > >>> On Wed, Oct 05, 2011 at 08:57:59AM -0400, Alan Greenberger wrote: > >>>> On 2011-10-03, Thomas H. George <li...@tomgeorge.info> wrote: > >>>> (...) > >>>>>>>> Tell us your scanner model? :-) > >>>>>>>> > >>>>>>> Epson Perfection 2400 Photo > >>>>>> > >>>>>> > >>>> (...) > >>>>> Just found the following: > >>>>> > >>>>> > >>>>> Script started on Mon 03 Oct 2011 03:38:15 PM EDT > >>>>> tom@dragon:~$ lsusb -s 001:005 > >>>>> Bus 001 Device 005: ID 04b8:011b Seiko Epson Corp. Perfection 2400 Photo > >>>>> tom@dragon:~$ scanimage -L > >>>>> device `epson2:libusb:001:005' is a Epson GT-9300 flatbed scanner > >>>>> device `epson:libusb:001:005' is a Epson GT-9300 flatbed scanner > >> > >> Alan's post has broken the thread - but in a previous post I mentioned > >> that "The problem seems to be that *both* epson and epson2 backends are > >> being called" > >> > >> <snipped> > >>>> $ grep epson /etc/sane.d/dll.conf > >>> epson > >>> epson2 > >> > >> This is where epson *and* epson2 are *both* being called. > >> Comment one of them out. > >> The default on Squeeze is for *only* the epson2 backend to be active. > >> > > I did comment out epson in dll.conf. This did not solve the problem. > >> What was the result of trying the suggested scanimage commands? (in the > >> post you didn't respond to) > >> > >> Cheers > >> > >> > > I did respond to Alan's post repeating all his commands and finding no > > difference in the file permissions. I don't know why that response > > didn't appear in this thread. > > It may have, and I may have missed it. > I still can't find your answer to the outcome of running:- > $ scanimage -d epson2:libusb:001:005 > and > $ scanimage -d epson:libusb:001:005
These commands respond "output is not a file, exiting" To add to the confusion xcanimage now works from a command line, no more segfault. I have changed nothing since installing iscan. My best guess is that commenting out epson in /etc/sane.d/dll.conf may have solved the problem but only took effect after the system was rebooted. > <snipped> > > > > Tom > >> -- > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/4e8fa2df.8050...@gmail.com > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111008140615.ga21...@tomgeorge.info
