| Summary: | Mageia/SANE does not find my scanner anymore | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Peter Hartmann <phartmann> |
| Component: | Release (media or process) | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | ftg, marja11, sysadmin-bugs, tmb |
| Version: | 5 | ||
| Target Milestone: | Mageia 5 | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Peter Hartmann
2017-07-22 17:07:42 CEST
Peter Hartmann
2017-07-22 17:08:27 CEST
Target Milestone:
--- =>
Mageia 5 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 Sorry to tell you but "chmod 777 /dev/bus -R" does not work 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. 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. (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. also, check if kernel sees the scanner with the command: lsusb CC:
(none) =>
tmb @ 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. (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 |