Bug 118516
| Summary: | xsane scans over and over again | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Malmgren <dm> | ||||||
| Component: | xsane | Assignee: | Nils Philippsen <nphilipp> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rawhide | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2005-10-11 08:26:23 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Daniel Malmgren
2004-03-17 11:48:48 UTC
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 this machine? 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 find that? It's really unlikely to be xsane -- there are no code changes since 0.92-5. 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 failure.. 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 same thing? 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 that. 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: xsane-0.95-1 sane-backends-1.0.15-7 What does this say?: grep -1w adf .sane/xsane/* [~$] grep -1w adf .sane/xsane/* .sane/xsane/Hewlett-Packard:psc1100series.drc-"" .sane/xsane/Hewlett-Packard:psc1100series.drc:"xsane-adf-scansource" .sane/xsane/Hewlett-Packard:psc1100series.drc-"Flatbed" Created attachment 108100 [details]
~/.sane/xsane/Hewlett-Packard:psc1100series.drc
I'll attach the entire file...
Change this line: "Flatbed" to read: (nil) 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. |