Description of problem: While scanning multiple pages with latest gscan2pdf a window appears with the message "Unknown message: Use of uninitialized value $batch_count in printf at /usr/bin/scanimage-perl line 1199." When you close that window, a second one appears with the message "Unknown message: Use of uninitialized value $batch_count in numeric eq (==) at /usr/bin/scanimage-perl line 1203." Version-Release number of selected component (if applicable): gscan2pdf 0.9.30. How reproducible: When scanning multiple, black and white pages using the document multi-feeder option. Steps to Reproduce: 1.Start gscan2pdf 2.Set for multiple black and white scanning. 3.Start scanning Actual results: The above-described message windows appear, although the program keeps scanning normally. Expected results: No "Unknown message" windows at all. Additional info: Using Fedora 12 64 bit fully updated with GNOME as desktop. Scanning to a Brother MFC-8460N multifunction machine.
The issue seems worse than originally reported. While the messages keep coming, the program tends to abort scanning (without crashing) when doing multiple-pages scans. For example, it scans the first two pages from a 10-page batch and then the message window appears and the rest of the batch is not scanned, forcing me to start the process for the remaining pages.
gscan2pdf-0.9.30-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gscan2pdf-0.9.30-3.fc12
gscan2pdf-0.9.30-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/gscan2pdf-0.9.30-3.fc13
I installed the update and the message window is gone! Thank you very much. However, the interruption problem still remains, so they were clearly not related. I will post a new bug report for that specific issue.
(In reply to comment #4) > I installed the update and the message window is gone! Thank you very much. > However, the interruption problem still remains, so they were clearly not > related. I will post a new bug report for that specific issue. Please do file another bug report. Also run gscan2pdf from the command line and see if any messages are being emitted to stdout/stderr. Try to describe what triggers the bug and all other details as best as you can. I looked at the upstream version control and I don't see any changes to address this new bug, but I'll take a closer look once you post the full details.
(In reply to comment #5) > (In reply to comment #4) > > I installed the update and the message window is gone! Thank you very much. > > However, the interruption problem still remains, so they were clearly not > > related. I will post a new bug report for that specific issue. > > Please do file another bug report. Also run gscan2pdf from the command line > and see if any messages are being emitted to stdout/stderr. Try to describe > what triggers the bug and all other details as best as you can. > > I looked at the upstream version control and I don't see any changes to address > this new bug, but I'll take a closer look once you post the full details. I will do. Right know I'm a little busy but expect to find sometime next weekend to follow your guide and file a new bug report. gscan2pdf is one of the most important projects for me, since I try to run a paperless office.
gscan2pdf-0.9.30-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gscan2pdf'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gscan2pdf-0.9.30-3.fc13
gscan2pdf-0.9.30-3.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gscan2pdf'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gscan2pdf-0.9.30-3.fc12
(In reply to comment #5) > (In reply to comment #4) > > I installed the update and the message window is gone! Thank you very much. > > However, the interruption problem still remains, so they were clearly not > > related. I will post a new bug report for that specific issue. > > Please do file another bug report. Also run gscan2pdf from the command line > and see if any messages are being emitted to stdout/stderr. Try to describe > what triggers the bug and all other details as best as you can. > > I looked at the upstream version control and I don't see any changes to address > this new bug, but I'll take a closer look once you post the full details. Done. See bug 581136.
gscan2pdf-0.9.30-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
gscan2pdf-0.9.30-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.