Linux software

[#1]

The Gtk-WARNING messages don't matter.
The "failed to open device" message suggests the scanning program didn't get very far, either it could not find the filename of the device it was expecting, or couldn't open it due to permissions problems.
You may find some more messages in the system logs - open Log File Viewer from the applications menu.
Is there actually a "snapscan" program? Try xsane.

[#2]

Quote from: gleneagles

ls CONF        etc                    mozilla.pdf         Templates Desktop     firefox                Music               Untitled1.pdf dir         Firefox_wallpaper.png  Pictures            Untitled2.pdf Documents   Graphics               ppdMP620-630en-1.5  usr Downloads   iscan-2.10.0           Public              Videos Esfw41.bin  iscan for scanner      scanner             XSane

The existence of files/directories such as etc, usr would seem to indicate a seriously peculiar setup.
Perhaps you have copied some of your system files into your home directory???

[#3]

I Think there is a major problem with the setup and that is why this specific program is failing to install correctly.
Looking at the log viewer I also get errors about the log viewer ! ie
Log Viewer: Could not open the following files:
/var/log/bootstrap.log/error starting file '/var/log/bootstrap.log: No such file or directory
/var/log/fontconfig.log/error starting file'var/log/fontconfig.log: No such file or directory.
So I guess the best course of action is to do nothing further as the rest of the OS appears to be working ok, or at least the bits I am using and keep going until such time as I need to do a full reinstall and at that point have another attempt to get the scanner working.
NB: There is a snapscan program but clearly it cannot link with the scanner as it comes up with the following when I try to scan,
Error failed to open Device.
Snapscan:libusb:002:003
Error during device I/O

[#4]

So the Log Viewer is configured to try and open some log files that don't exist - doesn't seem to be a big problem really. /var/log/messages is the main system logfile.
I can't find any trace of a program called "snapscan". There's no snapscan program on Fedora or Ubuntu. Try xsane (GUI) or scanimage (command line). What does the "scanimage -L" command say?

[#5]

Look at http://snapscan.sourceforge.net/
The Epson 2480 is supported and there are install/configure instructions at the bottom of the web page for using with SANE.
BTW Any reference to your current kernel version can be taken to be at least 2.6.
However, 
First find out the nature of those etc, usr files or directories.
Unless you know what they are, I would rename ~/usr to ~/usr_x and similarly with ~/etc
It is just possible that their current names could upset your install scripts.

[#6]

Quote from: ejs

So the Log Viewer is configured to try and open some log files that don't exist - doesn't seem to be a big problem really. /var/log/messages is the main system logfile. I can't find any trace of a program called "snapscan". There's no snapscan program on Fedora or Ubuntu. Try xsane (GUI) or scanimage (command line). What does the "scanimage -L" command say?

scanimage -L
device `snapscan:libusb:002:003' is a EPSON EPSON Scanner flatbed scanner

[#7]

Must admit this is getting above my head, following message when I try to rename file,
rename ~/usr to ~/usr_x
Bareword found where operator expected at (eval 1) line 1, near "/home/duncan"
(Missing operator before duncan?)
syntax error at (eval 1) line 1, near "/home/duncan"

[#8]

Quote from: gleneagles

Must admit this is getting above my head, following message when I try to rename file, rename ~/usr to ~/usr_x Bareword found where operator expected at (eval 1) line 1, near "/home/duncan" (Missing operator before duncan?) syntax error at (eval 1) line 1, near "/home/duncan"

Just use the file manager?

Quote from: gleneagles

scanimage -L device `snapscan:libusb:002:003' is a EPSON EPSON Scanner flatbed scanner

That looks OK, what about trying "scanimage --test --verbose"?

[#9]

For that rename operation, I was speaking in English!    Try

Quote

mv ~/usr ~/usr_x mv ~/etc ~/etc_x

[#10]

OMG that program was last updated "June 25, 2004"  Don't use it.
Use xsane, easy and works. (Under Graphics on my pc, you may need to install it from Synaptic) or simple-scan (for an easy to use scan and forget program)

[#11]

Quote from: Hairy

OMG that program was last updated "June 25, 2004"  Don't use it.

Which program? The scanimage command line tool that's part of sane-backends and is mainly useful for testing and debugging?

[#12]

Quote from: ejs

Quote from: Hairy OMG that program was last updated "June 25, 2004"  Don't use it. Which program? The scanimage command line tool that's part of sane-backends and is mainly useful for testing and debugging?

Just because a program hasn't been updated does not make it any less usable. I have a program (written for Windows in the early 1990's) has not been updated or supported since, but still works perfectly. I used it under Windows up to XP and Ubuntu from v6.04 to v10.04 LTS (my current version) with Wine.

[#13]

The actual snapscan program. If he starts to use it now, there is no guarantee that it will still work when/if he moves to a G3 based system. Much better to use a program that is supported and updated like simplescan,
An example of this is Nero (V3). It works fine in Mint 11 (G2) but under Mint 12 (G3) it just errors saying it can't find the language files. I assume Nero 4 would work but I am not paying to get an upgrade, having already paid to move from M$ to Linux. (That and the fact you get a full demo (unlimited) package under M$ not Linux where it times out in 30 days)

Quote from: Ellis

I have a program (written for Windows in the early 1990's) has not been updated or supported since, but still works perfectly. I used it under Windows up to XP and Ubuntu from v6.04 to v10.04 LTS (my current version) with Wine.

Yes but would it work under W7? And M$ programs are notorious for not being updated/charging for updates.

[#14]

Quote from: gleneagles

That looks OK, what about trying "scanimage --test --verbose"?

scanimage --test --verbose
scanimage: open of device snapscan:libusb:002:003 failed: Error during device I/O
Rather interestingly this is the first time I heard the scanner try to start up after using this command.
dick:green Quote fixed.

[#15]

It's worked !
No one more amazed than me !
I Ran the scanimage test and got the message shown in the previous post.
I Then renamed the files as suggested  by a Fox is evil and that seems to have done the trick.
Many thanks to those who have contributed to this topic.