Bug 485136
Summary: | Xsane don't work with Epson DX5050 (and other...) with F11 rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | dominique <chepioq> |
Component: | xsane | Assignee: | Nils Philippsen <nphilipp> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | nphilipp |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-16 16:40:39 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: | |||
Bug Depends On: | |||
Bug Blocks: | 440303, 460866 |
Description
dominique
2009-02-11 19:56:12 UTC
Nobody is here??? This bug is a little bug but it's during since F9 and F10... Where I can post for a reply??? Sorry for being late... Did this work with older sane-backends versions on older Fedora releases? Where did you get "epson5" from? I don't know about that driver so you may just be seing sane-backends ignoring this "epson5" driver it doesn't know... (In reply to comment #2) > Sorry for being late... > > Did this work with older sane-backends versions on older Fedora releases? Answering my own question: yes it did (see bug #440303). Please answer this question though: > Where did you get "epson5" from? I don't know about that driver so you may just > be seing sane-backends ignoring this "epson5" driver it doesn't know... As I don't have Epson hardware with which to test this, I'd like to bring this upstream. Do you want to file the bug or shall I? Please answer this question though:
>
> > Where did you get "epson5" from? I don't know about that driver so you may just
> > be seing sane-backends ignoring this "epson5" driver it doesn't know...
>
> As I don't have Epson hardware with which to test this, I'd like to bring this
> upstream. Do you want to file the bug or shall I?
I don't remember where I see epson5, I think I have seen it on sane site, but I don't find...
For info I don't install epson5 backend, I just change "epson2" line by epson5 in dll.conf and that also work, like when I comment "#epson2"
For me I don't know the difference between "epson" and "epson2" and I think that "epson2" line would be remote in /etc/sane.d/dll.conf
(In reply to comment #4) > I don't remember where I see epson5, I think I have seen it on sane site, but I > don't find... > For info I don't install epson5 backend, I just change "epson2" line by epson5 > in dll.conf and that also work, like when I comment "#epson2" > For me I don't know the difference between "epson" and "epson2" and I think > that "epson2" line would be remote in /etc/sane.d/dll.conf Googling "epson5 sane" doesn't yield anything worthwhile, so I assume there is no driver of that name. In that case, commenting out "epson2" and replacing it by "epson5" have the same effect, i.e. preventing SANE to use the epson2 driver. Again: Do you want to file the upstream bug or shall I? >
> Again: Do you want to file the upstream bug or shall I?
My English is very bad (I am 54 years old and I learn english 40 years ago... but I don't remember all...)
If you can, I prefers that you upstream this bug...
Thank
Dominique
Do you have an account at the SANE bug tracker? You can find it at: https://alioth.debian.org/tracker/?atid=410366&group_id=30186&func=browse I sure can file the bug upstream, but I don't have the hardware. So at least I'd want to put you on Cc so you can answer questions be the upstream maintainers. Hi I post a bug report here: https://alioth.debian.org/tracker/index.php?func=detail&aid=311545&group_id=30186&atid=410366 wait and see... Thanks very much! I'll change the bug status to CLOSED/UPSTREAM in the meantime and when there is a fix, the bug can be reopened and I'll integrate the patch into the Fedora packages. |