Red Hat Bugzilla – Bug 443199
HP Scanjet G 3010 does not work properly
Last modified: 2009-07-14 14:14:03 EDT
Description of problem:
When any doeument is scanned the output is in the form of black, grey and white
Version-Release number of selected component (if applicable):
sane as with Fedora-9-Beta-i386
Scan any document
Steps to Reproduce:
1.Put a document in the sanner
2.Go to scanner and scan
Hazy black, grey and white lines and dots
The document should have been scanned
Full profile of the machine is avaiable at
What is the model and manufacturer you using?
Has this same scanner worked on previous version of Fedora or other linux distros?
nevermind, i see it was in the subject
hardware == HP Scanjet G 3010
*** Bug 443198 has been marked as a duplicate of this bug. ***
Reply to Comment #1
The scanner did not work on F7.
I have not tested the working of the scanner on F8 as the driver for the TFT
monitor attached to my computer was not available in F8, and I used to get a
floating window saying Input Not Supported.
Now in F9-Beta the floating window problem is solved so I have installed it on
my computer for testing.
Reply to Comment #3
Yes there was some problem while I was posting the bug, so it got double posted
by mistake and therefore two consecutive serial numbers Bug 443198 and Bug
443199. Thanks for removing Bug 443198.
Looking at the SANE list of supported devices, I find that this scanner is
not completely supported yet. Comments there suggest that your model is similar
to the ScanJet 4370 which is reported to work with resolutions lower than 1200
dpi. What resolution did you use?
Created attachment 303147 [details]
Scanned image of a white sheet using default setting of XSane 0.995
I am using the default settings.
(In reply to comment #6)
> Created an attachment (id=303147) 
> Scanned image of a white sheet using default setting of XSane 0.995
And the default settings are? I'm asking because I'm not 100% positive they are
the same with every scanner model and I'd like to verify that.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.