Ubuntu
xsane package

Epson CX4800 scanner gets "no devices available"

Bug #37499 reported by z_diver
10
Affects Status Importance Assigned to Milestone
xsane (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

distribution: Dapper flight 5 upgraded to flight 6

xsane does not see the Epson CX4800 Scanner although it works perfectly if xsane is started with sudo after adding "usb 0x04b8 0x0819" to the /etc/sane.d/epson.conf file.

/var/log/messages writes only the line below if xsane is started as a normal user.
Mar 31 08:09:39 localhost python: hpssd [WARN] Inrecognized URI: usb://EPSON/Stylus%20CX4800

sudo xsane writes a bit more and works:
Mar 31 08:21:00 localhost kernel: [4533417.940000] usb 5-6: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1
Mar 31 08:21:00 localhost python: hpssd [WARN] Inrecognized URI: usb://EPSON/Stylus%20CX4800
Mar 31 08:21:01 localhost kernel: [4533417.940000] usb 5-6: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1

The workaround has been verified by several people on ubuntuforums.

Revision history for this message
Robin Sheat (eythian) wrote :

This also applies to the CX5900 scanner/printer in Edgy. In this case the line to add is:

usb 0×04b8 0×082e

Details are here: http://www.kallisti.net.nz/blog/2006/11/ubuntu-and-the-epson-stylus-cx5900/

Revision history for this message
mikko (mikko-) wrote :

If xsane have started first time by sudo, the .sane -directory might be owned by root now. And so xsane doesn't find your scanner. Try to delete the .sane -directory in your home folder.

http://ubuntuforums.org/showthread.php?p=1651194#post1651194

Revision history for this message
Hew (hew) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you? Can you try with the latest Ubuntu release (Hardy Heron)? Thanks in advance.

Changed in xsane:
status: New → Incomplete
Revision history for this message
Hew (hew) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xsane:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.