Op 10-01-04 21:59:13 schreef Jim George:
> Hi Eddy,
>
> I do have a printer connected to the same port. It's an Epson Photo
> Stylus 820cxi if that makes any difference.
Have you tried disconnecting it?
> I tried turning off/on my scanner but that made no difference, then I
> rebooted and when
--=_20040110205913_95570
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hi Eddy,
I do have a printer connected to the same port. It's an Epson Photo
Stylus 820cxi if that makes any difference.
I tried turning off/on my scanner but that made no difference, then
--=_2004011317_94993
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
> Hi Jim,
>
> now we are getting somewhere.
> It looks like the driver is waiting for the scanner motor to stabilize,
but it waits forever, either because it doesn't stabilize, or because the
Jim George wrote:
> without inetd running but with gdb.
>
> scanimage hung and when I crtl-c'd out I get the following
> "scanimage: received signal 2
> scanimage: trying to stop scanner"
>
> saned didn't quit. When I pressed ctrl-c in gdb I got
>
> [...]
>
> Program received signal SIG
Eddy,
Without inetd...
scanimage hung and when I ctrl-c'd out of scanimage I get the following
"scanimage: received signal 2
scanimage: trying to stop scanner "
saned did not quit. When I killed it, the saned window showed these last
few lines
"[saned] do_scan: read 0 bytes from scanner
[sane
Jim George wrote:
> > 2) Without xinetd, no gdb
> >* Does scanimage hang?
> It didn't even get started. I got the following error message:
> scanimage: open of device net:localhost:mustek_pp:Mustek-1200CP failed:
> Invalid argument
Sorry, I forgot to mention this: you have to run saned as roo
Hi Eddy,
see in-line below.
Jim
> Hi Jim,
>
> I think it's normal that saned exits after one scan. Normally, it's
> xinetd that restarts saned when a new request comes in.
> To restart saned in gdb, you only have to enter "r" at the prompt and
> then you can perform another scan.
>
> What surpr
Jim George wrote:
> Eddy,
>
> I have now run saned through gdb and done two scans. The first appeared
> to complete successfully so I ran the second but the client timed out and
> eventually saned quit (as you will see from the attached).
>
> Thanks for your continued help,
>
> Jim
>
Hi Jim,
--=_20040107102039_63664
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
> Hi,
>
> as I said before (but I don't know whether it came through because of
> the mail hickups), the problem in gdb is almost certainly caused by
> xinetd that is still running and listen
Hi,
as I said before (but I don't know whether it came through because of the
mail hickups), the problem in gdb is almost certainly caused by xinetd
that is still running and listening to port 6566. xinetd has to be stopped
first before running saned in gdb:
/etc/rc.d/init.d/xinetd stop
A
Hello,
another idea. May it be, that there are any saned or scanimage running
after the first scan attempt?
regards
-- jochen
Jim George wrote:
> Eddy and Joachen,
>
> when I tried to run saned under gdb I got the following output. Doesn't
> look good does it? Can you tell me what I should do
Hello,
I've thought long about your problem but I still don't get how your
parport can be locked that badly.
What kernel version are you using? What Linux distribution? Could you
please send the output of (after rebooting - that is in a state where
the scan will work?)
SANE_DEBUG_SANEI_PA4S2=6 s
"Jim George" wrote:
Hi,
> [saned] main: [0] bind failed: Address already in use
> [saned] main: [1] bind failed: Address already in use
> [saned] main: couldn't bind an address. Exiting.
>
> Program exited with code 01.
I guess you have (x)inetd configured to listen on port 6566 ... ?
JB.
--
Eddy and Joachen,
when I tried to run saned under gdb I got the following output. Doesn't
look good does it? Can you tell me what I should do now?
SANE_DEBUG_MUSTEK_PP=255 gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public Lic
14 matches
Mail list logo
