Bug 835685 - gscan2pdf-1.0.4-1.fc16 unable to scan from Epson - older gscan2pdf-1.0.0-1.fc16 works fine
Summary: gscan2pdf-1.0.4-1.fc16 unable to scan from Epson - older gscan2pdf-1.0.0-1.fc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gscan2pdf
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bernard Johnson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-26 20:14 UTC by Kai Engert (:kaie) (inactive account)
Modified: 2012-09-03 00:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-03 00:47:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kai Engert (:kaie) (inactive account) 2012-06-26 20:14:46 UTC
Fedora 16, i686, 32 bit.
Epson Stylus Photo RX520 all-in-one printer/scanner, USB.
The device is reported by gscan2pdf as Epson PM-A750

With version 1.0.4-1.fc16 installed, I get the following broken behaviour:
- start gscan2pdf
- select epson scanner
- click scan options tab, it comes up with "lineart" mode selected
- select a different mode, "color"
- the device options are removed from the dialog, 
  the progress indicator starts moving
- after a couple of seconds, the progress indicator stops

- problem 1:
  unfortunately, the dialog section "device options" remains empty!

  (expected: device option gets filled with controls)

- problem 2:
  despite the empty device options, I click "scan" anyway,
  but the result is an error message
  (it says that the threshold parameter doesn't apply to the current scan
   mode, which means, parameters from the original dialog opening
   are still effective.)

Comment 1 Kai Engert (:kaie) (inactive account) 2012-06-26 20:16:08 UTC
When I had downgraded to the older 1.0.0 version, it worked.
The device options section gets correctly updated each time I switch to a different scan "mode".
I was able to scan in the desired mode.

Comment 2 Kai Engert (:kaie) (inactive account) 2012-06-26 20:23:10 UTC
I will provide some additional findings, in the hope it helps.

I reinstalled the newer gscan2pdf.

As expected I still have the problem that the device option doesn't get updated when switching "mode".

I can quit and restart gscan2pdf - and it will remember the "mode" selected in the previous run - and it will show device options.

However, after the restart, the device options section is filled correctly. I can even scan in the desired mode.

It's simply necessary to restart (the newer 1.0.4) gscan2pdf each time I switch the scan mode.

Comment 3 Kai Engert (:kaie) (inactive account) 2012-08-20 19:53:12 UTC
Bernhard, could you please update the gscan2pdf package to something newer?

This bug is still present, and fedora is still at 1.0.4

I downloaded the upstream package version 1.0.6 from http://sourceforge.net/projects/gscan2pdf/files/gscan2pdf/ which works fine.

Comment 4 Fedora Update System 2012-08-24 19:17:48 UTC
gscan2pdf-1.0.6-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/gscan2pdf-1.0.6-1.fc17

Comment 5 Fedora Update System 2012-08-25 02:59:44 UTC
Package gscan2pdf-1.0.6-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gscan2pdf-1.0.6-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-12679/gscan2pdf-1.0.6-1.fc17
then log in and leave karma (feedback).

Comment 6 Kai Engert (:kaie) (inactive account) 2012-08-25 16:16:56 UTC
Thanks a lot for the updated build. It works for me and I've given karma

(others should give karma, too!)

Regarding the bugs. I still had some issues with the latest 1.0.6.
I removed $HOME/.gscan2pdf settings file, and now things look good.

Comment 7 Fedora Update System 2012-09-03 00:47:31 UTC
gscan2pdf-1.0.6-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.