Bug 1215476 - sane-backends: Sane scans for /dev/sga but scanner is at /dev/sg10
Summary: sane-backends: Sane scans for /dev/sga but scanner is at /dev/sg10
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stefan Brüns
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-19 09:35 UTC by Bodo Eggert
Modified: 2023-10-08 16:55 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bodo Eggert 2023-09-19 09:35:31 UTC 
The kernel currently uses /dev/sd{\d+}, but the search algorithm uses /dev/sg[0-9a-z].

After (cd /dev && ln -s sg10 sga), the scanner is found:

--8<---
This is sane-find-scanner from sane-backends 1.2.1

…
searching for SCSI scanners:
…
checking /dev/sga... open ok
found SCSI scanner "FUJITSU fi-5120Cdj 0E00" at /dev/sga
…
--8<---

Proposed fix: Also scan for /dev/sd\d{\d+}
Comment 1 Bodo Eggert 2023-09-19 09:46:13 UTC 
PS: scanimage / xsane expects the device node at /dev/scsi/host6/bus0/target4/lun0/generic, but it's not being created there. Only /dev/sg[0-8] are scanned.
Comment 2 Stefan Brüns 2023-10-08 16:55:39 UTC 
1. /dev/sdX is used for disks, not "generic" scsi devices
2. This is apparently an upstream (SANE project) issue, not (open)SUSE specific, please open a bug report there.