Description of problem: xsane doesn't work when gpilotd is running Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1. plug in an usb scanner (I got an epson perfection 1650) 2. start gpilotd (I am using the applet) 3. use xscan Actual results: xsane hangs and fails Expected results: proper scan Additional info: this shows in the logs usb 2-2: usbfs: USBDEVFS_BULK failed ep 0x2 len 2 ret -110 usb 2-2: usbfs: USBDEVFS_BULK failed ep 0x81 len 1 ret -75 usb 2-2: xsane timed out on ep2out usb 2-2: usbfs: USBDEVFS_BULK failed ep 0x2 len 2 ret -110 usb 2-2: xsane timed out on ep2out
*** Bug 147809 has been marked as a duplicate of this bug. ***
No idea what's going on here. CCing kernel and gnome-pilot owners in case they can shed any light on it.
I found the following debian bug, which seems to be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=289894 btw: Sorry about the duplicate, but bugzilla was hanging the first time
That bug seems to indicate pretty strongly that it's a gnome-pilot bug. Reassigning.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Is this problem still present in Fedora Core 6?
The distribution against which this bug was reported is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as INSUFFICIENT_DATA. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
You can close this. My Palm has died on me now and I am not using the scanner either. My guess is that is fixed anyway, as it was easy to reproduce and is two years old.
Closing as requested. Thanks for responding.