Opens inaccessible tcp device, errors, doesn't recover

[Jelle Foks]

version 0.9.32-1

I use gscan2pdf on two different locations, where there are two different officejet scanners.

On one location, when I start gscan2pdf, and select File->Scan, it does 'Fetching list of devices', and it chooses the printer that is inaccessible on that location, then it opens a window that says 'Opening Device', followed by a window stating 'Error opening device: Error during device I/O'. After pressing 'Close' on that window, only the main window remains, and File-Scan (or ctrl-G) opens an empty and functionless "Scan Document" window. It is not possible to switch to the other officejet that is accessible, because it always automatically selects the inaccessible one and errors as described.

As a workaround, starting with 'gscan2pdf --device=test' allows selecting of 'Rescan for Devices' in the "Scan Document" window, after which both officejets appear in the list, and the correct one can be chosen and scanning works perfectly.

I'm not sure if the bug is that it tries to connect to an inaccessible (networked) hplip scanner, or if the bug is that after the device I/O error message the program becomes useless, but as of now, I have to use the --device=test workaround to use this program.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Better workarounds would be either to set the SANE_DEFAULT_DEVICE environmental variable (e.g. put SANE_DEFAULT_DEVICE=... in your .bashrc), or to start gscan2pdf --device=device with the actual device name required.

The device names are listed in the scanimage --help output (or if you start gscan2pdf with --log=log, then also in the log file).

[Jeffrey Ratcliffe (jeffreyratcliffe)]

The code for opening the device has changed a great deal between 0.9.32 and the current version 1.0.4, and will change again with the upcoming version 1.0.5.

Would you be happy to test prerelease versions of 1.0.5 if I upload them here so that the problematical device is ignored and another one is tried?

[Jelle Foks (jellefoks)]

I have no problem trying experimental builds from here, or a ppa, etc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Do you see the problem with more recent builds from the ppa?

[Jelle Foks (jellefoks)]

Where is the ppa to use?

[Jeffrey Ratcliffe (jeffreyratcliffe)]

It is described on the website:

http://gscan2pdf.sourceforge.net/

The ppa is

http://ppa.launchpad.net/jeffreyratcliffe/ubuntu

[Jelle Foks (jellefoks)]

All right, I'll do some testing to see if I can trigger the bug with the version of the ppa, and report back here if I see it.

Note, on ubuntu, adding a ppa repository and the key can also be done with a single command:

sudo apt-add-repository ppa:jeffreyratcliffe/ppa

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Thanks for the apt-add-repository tip. I'll update the docs.

[Jelle Foks (jellefoks)]

Just triggered the problem with '1.1.3-0~ppa1raring'.

Steps:
. file->scan
. 'scan document' with 'fetching list of devices'
. then shows the hp deskjet at the other location that isn't reachable here
. main window shows 'opening device' at bottom
. 'scan document' window closes, and immediately:
. popup comes 'Error opening device: Invalid argument'
. close
. main window bottom still shows 'opening device' with a motionless ('stuck') blue part.
. file->scan
. new window pops up with title 'Scan Document' and nothing in it

quit gscan2pdf and restart, same result.

console output:

$ gscan2pdf
Gtk-Message **: Failed to load module "overlay-scrollbar" at /usr/lib/perl5/Gtk2.pm line 138.
Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed at /usr/bin/gscan2pdf line 8183.
Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed at /usr/bin/gscan2pdf line 8183.
ERROR - opening device: Invalid argument
Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed at /usr/bin/gscan2pdf line 8178.
Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed at /usr/bin/gscan2pdf line 8183.

I think the gdk_error_traps message has nothing to do with this problem, it's a common thing for gtk apps, see #1075928

ps: i'm using a kde4 desktop.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Please start gscan2pdf with

gscan2pdf --log=log

reproduce the problem, quit, and post the log file.

[Launchpad Janitor (janitor)]

[Expired for gscan2pdf (Ubuntu) because there has been no activity for 60 days.]