Description of problem: I run xsane, the initial dialog to select which image device comes up, and has my HP photosmart all-in-one already selected as the default. I click OK, the initial dialog goes away, xsane goes into a 100% cpu loop, and the preview app never appears. The scanner device is: hpaio:/usb/Photosmart_C5500_series?serial=MY8AFC20JZ056H Hewlett-Packard Photosmart_C5500_series all-in-one Same hardware works fine with fedora 10 xsane. Also the command line scanimage tool seems to work just fine on this device even in rawhide. Version-Release number of selected component (if applicable): xsane-0.996-6.fc11.x86_64 How reproducible: every time Steps to Reproduce: 1.see above 2. 3. Actual results: infinite loop Expected results: scanner app Additional info:
Created attachment 341317 [details] debug session from attach to hung xsane I downloaded some debuginfo files, attached to xsane, and found it searching for the end of a linked list in which list->next apparently points to list, so finding the end of that will take a while :-). The backtrace looks like it is fiddling with gtk menus when it gets into this loop.
I am having the same problem: FC11 Beta x86_64 with Rawhide updates xsane x86_64 0.996-6.fc11 Intel Core i7 Scanner: Brother MFC-240C all-in-one Symptom: Initial "Scanning for devices..." dialog appears, then disappears. Nothing follows. Xsane is then running in the background at high CPU with no windows visible. Alternatives: The command line tool "scanimage" makes the scanner begin scanning apparently normally. (I interrupted it at that point.) I downgraded to the xsane RPM xsane-0.996-3.fc10.x86_64.rpm from Fedora 10 and the problem went away. The scanning windows appear normally and I can scan an image.
http://kojipkgs.fedoraproject.org/packages/xsane/0.996/7.fc11/ Please try this build. It made xsane work for me. If it works for you, then this is the same bug as Bug #493659.
I can confirm the exact same behaviour as the original report, but with an HP PSC 1310. The updated packages (xsane-0.996-7) indeed solve that issue for me.
Me too. I just installed the x86_64 rpms from the above link and it works fine. I'm looking at a preview image now.