Bug 21322 - Mageia/SANE does not find my scanner anymore
Summary: Mageia/SANE does not find my scanner anymore
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal major
Target Milestone: Mageia 5
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-22 17:07 CEST by Peter Hartmann
Modified: 2017-07-29 23:39 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Peter Hartmann 2017-07-22 17:07:42 CEST
Description of problem:
Mageia/SANE does not find my scanner anymore.

Version-Release number of selected component (if applicable):
SANE-Version 1.0.24-10.2.mga5

How reproducible:
always

Steps to Reproduce:
1. Start MCC /Hardware/Scanner
2. A small window appears: "Searching for Installed Scanners"
3. That's it!!

My scanner is a Canon CanoScan N1240U.
When starting with a fresh (old) Mageia 5 there was no problem working with it.
It also runs perfectly with Windows XP SP2 on the same machine.
Peter Hartmann 2017-07-22 17:08:27 CEST

Target Milestone: --- => Mageia 5

Comment 1 Frank Griffin 2017-07-22 20:36:22 CEST
Try "chmod 777 /dev/bus -R" and see if it finds it then.  There was a bug in that udev was creating USB devices with ownership root:root and permissions rw-rw-r--.  This won't work with SANE because it needs write access to the scanner.

CC: (none) => ftg

Comment 2 Peter Hartmann 2017-07-24 12:11:06 CEST
Sorry to tell you but "chmod 777 /dev/bus -R" does not work
Comment 3 Frank Griffin 2017-07-24 15:23:38 CEST
Sorry, I should have mentioned that you need to do it as root.

Also, I read too quickly.  I thought it was xsane run as a normal user that couldn't find the scanner.  MCC Scanner Setup is different.

Try running xsane from the command line and see what shows up on the terminal.
Comment 4 Peter Hartmann 2017-07-24 20:41:39 CEST
I did the chmod command as root > it does not work

When I start xsane in Konsole a small message box appears but it was completely empty.
Also there was no output at the Konsole Prompt.
Comment 5 Frank Griffin 2017-07-24 22:08:41 CEST
(In reply to Peter Hartmann from comment #4)
> I did the chmod command as root > it does not work

Do you mean that the chmod itself doesn't work or that xsane still doesn't work after the chmod ?

I tried this on a laptop with a camera.  xsane was not previously installed, so I did a "urpmi xsane".  When it completed, I did xsane from a user command line, got a window saying "scanning for devices", and then xsane opened using the camera device (the laptop has no scanner).  There was no output on the terminal.  If you can try this on a laptop, see if the camera is recognized.

My only other suggestion is to issue xsane as root and see if that makes a difference.
Comment 6 Thomas Backlund 2017-07-24 22:25:36 CEST
also, check if kernel sees the scanner with the command: lsusb

CC: (none) => tmb

Comment 7 Peter Hartmann 2017-07-26 15:28:29 CEST
@ Thomas Backlund
Yes the lsusb command shows me the scanner

@ Frank Griffin
The chmod command itself works but xsane doesn't.

In the meantime my scanner is working again. I don't know why but xsane needs more than 15 minutes to find my scanner. After that everything is working again. 
After a reboot my scanner is found within a few seconds.

Thanks all for helping.
Comment 8 Marja Van Waes 2017-07-29 23:39:29 CEST
(In reply to Peter Hartmann from comment #7)
> @ Thomas Backlund
> Yes the lsusb command shows me the scanner
> 
> @ Frank Griffin
> The chmod command itself works but xsane doesn't.
> 
> In the meantime my scanner is working again. I don't know why but xsane
> needs more than 15 minutes to find my scanner. After that everything is
> working again. 
> After a reboot my scanner is found within a few seconds.
> 
> Thanks all for helping.

Closing, because it works now, but please reopen this report, Peter, if xsane needs far too long to find your scanner, again.

In that case, please open a terminal, become root, and run:

    journalctl -ab > logs.txt

    xz logs.txt

and attach logs.txt.xz

Resolution: (none) => FIXED
CC: (none) => marja11
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.