https://bugzilla.novell.com/show_bug.cgi?id=422771
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=422771#c3
--- Comment #3 from Johannes Meixner 2008-09-04 02:24:20 MDT ---
Did you perhaps unplug and re-plug your scanner at the USB?
Or did perhaps something in the USB system do anything
like this?
If a scanner is re-plugged to the USB, it gets by this
famous plug and play USB kernel system a new device file
and then it is clear that a scanning application will
no longer find it. Usual scanning applications select
the scanner device file during startup - they are just
not (yet) prepared for the new wonderful world of
changing devce nodes at arbitrary time.
When I re-connect my Canon Lide 30 USB scanner,
I can quit a running xscanimage plugin and
I can also re-start it from Gimp with
File->Acquire->xscanimage.
But then I get an error that the scanner is not
accessible under the old SANE device ID
(e.g. for me "plustek:libusb:002:004").
This may look like a bug in Gimp because it seems
Gimp somehow remembers the SANE device ID?
In contrast when I run xscanimage stand-alone,
it retreives the current SANE device ID during
each startup anew.
In contrast when I use xsane as Gimp plugin,
there is under "File->Acquire" a separated
"XSane Device dialog..." where one can select
the current SANE device ID after an USB re-plug.
This seems to indicate that the bug is in the
xscanimage Gimp plugin which does not provide
a correct "device dialog"?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.