Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15573 - [sane] Do not find my scanner after computer reboot

Attached to Project: Arch Linux
Opened by Nicolas Houdoin (binuts) - Sunday, 19 July 2009, 09:23 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 01 January 2011, 14:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When i run xsane after a computer reboot, it can not find my scanner "CanoScan Lide 25 plustek:libusb:003:003".
I have to reinstall the package sane "pacman -S sane"
After it work fine !


package version : sane 1.0.20-3 with xsane 0.996-2
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 01 January 2011, 14:32 GMT
Reason for closing:  Fixed
Comment by Roman Kyrylych (Romashka) - Sunday, 19 July 2009, 09:39 GMT
I'm not sure if I got the problem correctly. Do you mean that you have to reinstall sane after every reboot to get xsane working?
Comment by Nicolas Houdoin (binuts) - Sunday, 19 July 2009, 09:53 GMT
Yes i must reinstall sane after each reboot for xsane detects my scanner.
Comment by Roman Kyrylych (Romashka) - Sunday, 19 July 2009, 10:18 GMT
Hmmm, I have only one guess.
Where/how are user/group credentials stored on your system?
The fact is that this is called on every sane install:
getent group scanner >/dev/null || usr/sbin/groupadd -g 96 scanner
so I guess the created group is not remembered on your system.
Comment by Nicolas Houdoin (binuts) - Sunday, 19 July 2009, 10:32 GMT
After reboot

[binuts@margotte ~]$ getent group scanner
scanner:x:96:binuts
[binuts@margotte ~]$ getent group scanner >/dev/null || usr/sbin/groupadd -g 96 scanner
Xsane do not find my scanner

[binuts@margotte ~]$ sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM9832/3) at libusb:003:003
# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

# Not checking for parallel port scanners.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.

# You may want to run this program as root to find all devices. Once you
# found the scanner devices, be sure to adjust access permissions as
# necessary.

[binuts@margotte ~]$ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c048 Logitech, Inc.
Bus 003 Device 003: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 04cf:8819 Myson Century, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Strange ?
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 26 January 2010, 07:09 GMT
  • Field changed: Status (Assigned → Waiting on Response)
this is still a problem?
Comment by Nicolas Houdoin (binuts) - Thursday, 28 January 2010, 22:13 GMT
yes the problem is identical
Comment by Leonid Isaev (lisaev) - Sunday, 20 June 2010, 14:23 GMT
I don't think it is a sane/xsane issue. I have exactly the same scanner and it worked for me with all versions of sane, including the latest one from /extra and a custom compiled one...
Comment by Thomas Dziedzic (tomd123) - Sunday, 04 July 2010, 02:21 GMT
status?
Comment by Nicolas Houdoin (binuts) - Tuesday, 06 July 2010, 13:12 GMT
I have update my system.
sane-1.0.21-3
But the problem persists.
If you think that the problem does not come from xsane, then close the bug.
But can reorient trade towards a more general level?
Comment by Philipp (hollunder) - Monday, 08 November 2010, 07:59 GMT
Are you sure dbus is running? I just spent an hour trying to get the scanner to work and the only problem was that dbus wasn't running.

The error message I got was the rather stupid: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c

Also, I thought programs were supposed to start dbus when they need it. Sane apparently doesn't do this.
Comment by Nicolas Houdoin (binuts) - Friday, 03 December 2010, 18:25 GMT
Dbus is running
Now the package is "sane 1.0.21-3" and the problem persist.
Comment by Nicolas Houdoin (binuts) - Saturday, 01 January 2011, 12:28 GMT
The bug is solved !!
The package is "sane 1.0.21.-4" and it work.
You can closed this bug.
Thanks.

Loading...