Red Hat Bugzilla – Bug 980103
gscan2pdf fails with "invalid argument"
Last modified: 2015-01-14 06:08:47 EST
Created attachment 767391 [details]
Error popup on the screen
Description of problem:
Trying to use gscan2pdf with my CANON LIDE30 USB scanner.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.File->scan, then select scanner in GUI
3.press the scan button
See description. Addiotionally, getting the following msg in the terminal:
*** unhandled exception in callback:
*** can't open /tmp/gscan2pdf-gI6G/out1.pnm: No such file or directory
*** ignoring at /usr/share/perl5/vendor_perl/Gscan2pdf/Dialog/Scan/Sane.pm line 1466.
Some additional notes:
* The problem also exists with HP scanners or my laptop's integrated camera, so it seems to be a generic issue.
* The problem apparently was introduced with F19 (as in: it worked before the upgrade).
* Other programs such as Simple Scan still work.
The default device if I start gscan2pdf is the builtin laptop camera. When switching to my HP scanner, the Device dialog is not updated for the Scanner options although it now shows the Scanner in the Device line at the top of the dialog.
When selecting "Rescan for Devices" I see the following error in the terminal window:
Use of uninitialized value $device in string eq at /usr/share/perl5/vendor_perl/Gscan2pdf/Dialog/Scan/Sane.pm line 77.
It looks like selecting a different device than the default in the device dialog is ignored. However when I start gscan2pdf with the --device option and the scanner as the parameter, it works correctly. So the problem appears to be in the device management UI.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.