Red Hat Bugzilla – Bug 118516
xsane scans over and over again
Last modified: 2007-11-30 17:10:38 EST
Description of problem:
xsane scans images over and over again
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Scan an image in xsane
Images are scanned allright. Problem is that when xsane is finished
scanning it starts over again, scanning the same image. Pressing
cancel during scan just makes it start from the beginning again. This
repeats over and over again until i quit the program.
Scan the image once and then wait til I tell it to scan another.
It doesn't seem to matter whether xsane is set to view, save etc.
While in view mode it opens up a new viewer window for every time it
scans the image, in save mode I get a requester about the file already
existing for every loop.
I get no error messages whatsoever.
Using a HP psc 1110, using hpoj driver.
Is this something that worked for you in a previous release? (Which?)
Yep. Problem is I don't really know when I last used my scanner :-/ I
asked my girlfriend and she says when she last scanned "a couple of
weeks ago" it worked allright. My best guess is that that was 0.92-5.
According to the changelog nothing important has changed since then
though, so it's something of a mystery...
Well, did it work in Fedora Core 1, for example? How are you updating
In fc1 it worked good, these strange things started just a couple of
weeks ago. The machine is updated using yum.
I could test downgrading to 0.92-5 if I just had the rpm. Where can I
It's really unlikely to be xsane -- there are no code changes since
What kernel are you running?
Self compiled 2.6.3 (no patches, vanilla from kernel.org). I'll attach
my .config, haven't found any problems there myself though. Compiled
my kernel feb 19, it has been working after that.
Created attachment 98650 [details]
My kernel config
What did you use before that? Seems like it might coincide with the
Does the same problem occur with a Fedora devel kernel?
I think I used 2.6.2-rc3 before that. But since xsane worked a couple
of weeks ago and my kernel is a month old I don't think that's the
problem. Well, downloading a fedora kernel rpm and trying won't hurt,
I'll try that and report back afterwards.
After working for a while trying to get anything at all to work with
fedora kernel I give up. I think I've adapted quite much of my
configuration to my own kernel config, it'll be too much work
configuring everything back to working with fedora kernel. Sorry...
Ok. After a couple more hours of work I succeeded to get the fedora
kernel running and I can confirm that the problem is still there, so
it can't be a kernel issue.
Upgraded to 2.6.5 today and noticed this bug is still there. Quite
sure now it isn't a kernel issue...
Perhaps "Batch scan" is checked in the advanced options window?
Nope, it isnt...
Which version of xsane are you using now? Does "scanimage > scanned.pnm" do the
scanime works just fine, I don't get the same result there.
I just tried upgrading xsane to 0.95. Sadly enough that version doesn't start at
all, so I can't say whether this bug is still there. I'll file another bug about
Ok, now xsane works again. This bug is still there though. I tried
removing xsane configuration file (to solve #142148), it doesn't seem
to solve this one though.
I now use the latest rawhide versions:
What does this say?:
grep -1w adf .sane/xsane/*
[~$] grep -1w adf .sane/xsane/*
Created attachment 108100 [details]
I'll attach the entire file...
Change this line:
Does that help?
Yep. That did the trick!
Is this xsane misinterpreting it's own settings?
Not sure what the cause is. Can you find which preference switch in the GUI
affects that setting?
I can't seem to find any setting for it. When I tried removing the drc file and
then starting xsane the file was back, with working settings, so this maybe is a
fault in some earlier xsane version?
Oh, btw, the setting is now not (nil) but "", seems to do the same difference.
As this seems to have been a transient, not reproducible bug, I'll close it.