Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-04-20 Thread Leech Joe
Leech Joe wrote on 04/04/05 13:22:
Same Scanner same Problem, but here _everytime_ the scanner gets wedged. 
After removing the package
  libsane-extras
everything works again. Very strange.
hth somebody else, Joachim Lechner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-04-20 Thread Julien BLACHE
Leech Joe [EMAIL PROTECTED] wrote:

Hi,

 Same Scanner same Problem, but here _everytime_ the scanner gets
 wedged.

 After removing the package

libsane-extras

 everything works again. Very strange.

 hth somebody else, Joachim Lechner

That's another problem. Remove libsane-extras or disable the epkowa
backend...

I should really make the extras backends come last in the list.

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-04-04 Thread Leech Joe
Same Scanner same Problem, but here _everytime_ the scanner gets wedged. 
With knoppix 3.7 no problems occured.

/var/log/kern.log
---snip---
...
kernel: usb 2-2: usbfs: interface 0 claimed while 'xsane' sets config #1
---snip---
sane-find-scanner -v:
---snip---
This is sane-find-scanner from sane-backends 1.0.15
...
searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
...
checking /dev/usbscanner15... failed to open (Invalid argument)
found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON 
Scanner], chip=LM9832/3) at libusb:002:005
...
done
---snip---
(I removed the comments and the scsi section)

USB_DEBUG=255 xsane
---snip---
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 005 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 004 on 003
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 003 on 003
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 003
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
usb_os_find_devices: Found 005 on 002
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 001
error obtaining child information: Operation not permitted
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 005 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 004 on 003
skipped 1 class/vendor specific interface descriptors
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 003 on 003
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 003
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
usb_os_find_devices: Found 005 on 002
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Operation not permitted
error obtaining child information: Operation not permitted
usb_os_find_devices: couldn't get connect info
usb_os_find_devices: Found 001 on 001
error obtaining child information: Operation not permitted
usb_set_debug: Setting debugging level to 255 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
Check that you have permissions to write to 002/005 and, if you don't, 
that you set up hotplug (http://linux-hotplug.sourceforge.net/) correctly.
USB error: could not claim interface 0: Device or resource busy
usb_set_debug: Setting 

Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Julien BLACHE
reassign 299721 libsane
thanks

 This is with the 2.6.8-2-686 kernel (Jan 24 03:58:38 date);
 and I suspect that it has some USB problems.  Possibly,
 this is a reflection of some USB transport failure.

Anything of interest in /var/log/messages when this happens ?

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Greg Kochanski
Here is /var/log/messages.
The scanner got wedged twice, once around 00:33:50 and again
around 00:38:00.   Then, it worked nicely until I turned it
off, around 01:09.
Mar 16 00:13:52 gpk -- MARK --
Mar 16 00:29:41 gpk kernel: usb 2-2.1: new full speed USB device using 
address 4Mar 16 00:29:42 gpk usb.agent[8271]:  libusbscanner: loaded 
successfully
Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed while 
'xsane' sets config #1
Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar 16 
00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using address 
5Mar 16 00:33:54 gpk usb.agent[8357]:  libusbscanner: loaded 
successfully Mar 16 00:38:07 gpk kernel: usb 2-2.1: USB disconnect, 
address 5
Mar 16 00:38:10 gpk kernel: usb 2-2.1: new full speed USB device using 
address 6Mar 16 00:38:11 gpk usb.agent[9189]:  libusbscanner: loaded 
successfully
Mar 16 00:53:52 gpk -- MARK -- Mar 16 01:09:02 gpk kernel: usb 2-2.1: 
USB disconnect, address 6

Julien BLACHE wrote:
reassign 299721 libsane
thanks

This is with the 2.6.8-2-686 kernel (Jan 24 03:58:38 date);
and I suspect that it has some USB problems.  Possibly,
this is a reflection of some USB transport failure.

Anything of interest in /var/log/messages when this happens ?
JB.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Julien BLACHE
Greg Kochanski [EMAIL PROTECTED] wrote:

 Here is /var/log/messages.
 The scanner got wedged twice, once around 00:33:50 and again
 around 00:38:00.   Then, it worked nicely until I turned it
 off, around 01:09.


 Mar 16 00:13:52 gpk -- MARK --
 Mar 16 00:29:41 gpk kernel: usb 2-2.1: new full speed USB device using
 address 4Mar 16 00:29:42 gpk usb.agent[8271]:  libusbscanner:
 loaded successfully
 Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed
 while 'xsane' sets config #1
 Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar
 16 00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using
 address 5

Interesting, although I don't know what I should think about that :/
Aurélien may have an idea.

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Aurélien Jarno
Julien BLACHE a écrit :
Greg Kochanski [EMAIL PROTECTED] wrote:

Here is /var/log/messages.
The scanner got wedged twice, once around 00:33:50 and again
around 00:38:00.   Then, it worked nicely until I turned it
off, around 01:09.
Mar 16 00:13:52 gpk -- MARK --
Mar 16 00:29:41 gpk kernel: usb 2-2.1: new full speed USB device using
address 4Mar 16 00:29:42 gpk usb.agent[8271]:  libusbscanner:
loaded successfully
Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed
while 'xsane' sets config #1
Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar
16 00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using
address 5

Interesting, although I don't know what I should think about that :/
Aurélien may have an idea.
Not really.
Could you please run USB_DEBUG=255 xsane and send us the output log ?
Aurelien
--
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Henning Meier-Geinitz
Hi,

On Wed, Mar 16, 2005 at 06:12:34PM +0100, Julien BLACHE wrote:
 Greg Kochanski [EMAIL PROTECTED] wrote:
 
  Here is /var/log/messages.
  The scanner got wedged twice, once around 00:33:50 and again
  around 00:38:00.   Then, it worked nicely until I turned it
  off, around 01:09.
 
 
  Mar 16 00:13:52 gpk -- MARK --
  Mar 16 00:29:41 gpk kernel: usb 2-2.1: new full speed USB device using
  address 4Mar 16 00:29:42 gpk usb.agent[8271]:  libusbscanner:
  loaded successfully
  Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed
  while 'xsane' sets config #1
  Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar
  16 00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using
  address 5
 
 Interesting, although I don't know what I should think about that :/
 Aurélien may have an idea.

Check if the scanner's power supply is ok. I've seen similar trouble
when either the scanners power supply was defective (too low current)
or I used the wrong power supply accidently. Or with scanners which
use power from USB, the power supply of the hub may not be plugged in,
or the computer or hub may not have enough power.

Bye,
  Henning


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-16 Thread Julien BLACHE
Henning Meier-Geinitz [EMAIL PROTECTED] wrote:

Hi Henning,

  Mar 16 00:33:42 gpk kernel: usb 2-2.1: usbfs: interface 0 claimed
  while 'xsane' sets config #1
  Mar 16 00:33:52 gpk kernel: usb 2-2.1: USB disconnect, address 4 Mar
  16 00:33:54 gpk kernel: usb 2-2.1: new full speed USB device using
  address 5
 
 Interesting, although I don't know what I should think about that :/
 Aurélien may have an idea.

 Check if the scanner's power supply is ok. I've seen similar trouble
 when either the scanners power supply was defective (too low current)
 or I used the wrong power supply accidently. Or with scanners which
 use power from USB, the power supply of the hub may not be plugged in,
 or the computer or hub may not have enough power.

Thanks for the input; I tend not to think about this kind of issues.

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 



Bug#299721: xsane on epson perfection 1260 -- sometimes scanner gets wedged

2005-03-15 Thread Greg Kochanski
Package: xsane
Version: 0.97-3
Severity: normal


Occasionally, especially when first starting the scanner,
the scanner gets wedged, and sits there emitting a humming
noise (about 500 Hz to my ear).

When this happens, one cannot stop it with the buttons
on xsane.   Unplugging and replugging the scanner seems
to do the trick, though.

This is with the 2.6.8-2-686 kernel (Jan 24 03:58:38 date);
and I suspect that it has some USB problems.  Possibly,
this is a reflection of some USB transport failure.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xsane depends on:
ii  libatk1.0-0 1.8.0-4  The ATK accessibility toolkit
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libgimp2.0  2.2.4-1  Libraries necessary to run the GIM
ii  libglib2.0-02.6.3-1  The GLib library of C routines
ii  libgtk2.0-0 2.6.2-3  The GTK+ graphical user interface 
ii  libieee1284-3   0.2.8-2  Cross-platform library for paralle
ii  libjpeg62   6b-9 The Independent JPEG Group's JPEG 
ii  libpango1.0-0   1.8.1-1  Layout and rendering of internatio
ii  libpng12-0  1.2.8rel-1   PNG library - runtime
ii  libsane 1.0.15-7 API library for scanners
ii  libtiff43.7.1-4  Tag Image File Format (TIFF) libra
ii  libusb-0.1-42:0.1.10a-6  userspace USB programming library
ii  xsane-common0.97-3   GTK+-based X11 frontend for SANE (
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]