Epson GT-5500 scanner advertise itself as a scsi device type 3, so it need a special rule in /etc/udev/rules.d/60-libsane.rules to be recognized and properly configure the device's file rights. There's some entry already there starting line 1497, so just adapt one : # EPSON GT-5500 KERNEL=="sg[0-9]*", ATTRS{type}=="3", ATTRS{vendor}=="EPSON", ATTRS{model}=="SCANNER GT-5500", MODE="0664", GROUP="usb", ENV{libsane_matched}="yes"
Source RPM: sane-backends-1.0.22-1.mga1 => sane
assigning to maintainer
CC: (none) => marja11Assignee: bugsquad => dmorganecSource RPM: sane => sane-1.0.22-1.mga1.src.rpm
Whiteboard: (none) => OK
CC: (none) => djmarian4uSummary: Add udev rule to support Epson GT-5500 scsi scanner ootb => add udev rule to support Epson GT-5500 scsi scanner ootb
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
Status: RESOLVED => REOPENEDVersion: 1 => 5Resolution: WONTFIX => (none)
Reopened for Mageia5 : Epson GT-5500 scanner advertise itself as a scsi device type 3, so it need a special rule in 60-libsane.rules to be recognized and properly configure the device's file rights. There's some entry already there starting line 1967, so just add this one : # EPSON GT-5500 KERNEL=="sg[0-9]*", ATTRS{type}=="3", ATTRS{vendor}=="EPSON", ATTRS{model}=="SCANNER GT-5500", MODE="0664", GROUP="usb", ENV{libsane_matched}="yes"
Source RPM: sane-1.0.22-1.mga1.src.rpm => sane-backends-1.0.24-10.mga5
This package has no dedicated maintainer for now that I can assign the bug to (I've asked for one in the dev mailing list, let's hope). Adding packagers who touched it recently in CC.
CC: (none) => anaselli, ennael1, juergen.harmsAssignee: dmorganec => bugsquad
It's strange that GT-5500 scanner needs some changes in udev rules. There is already the following rule that should cover this scanner: # Some scanners advertise themselves as SCSI device type 3 # Wildcard: for some Epson SCSI scanners KERNEL=="sg[0-9]*", ATTRS{type}=="3", ATTRS{vendor}=="EPSON", ATTRS{model}=="SCANNER*", MODE="0644", GROUP="usb", ENV{libsane_matched}="yes" The only difference with the requested change is the wildcard usage in ATTRS{model}.
CC: (none) => olegbosis
(In reply to Oleg Bosis from comment #6) > It's strange that GT-5500 scanner needs some changes in udev rules. There is > already the following rule that should cover this scanner: You are right, just tested and it works without the specific "SCANNER GT-5500" line. The problem isn't the udev rules, it's the module sg that wasn't loaded : i had to add it to the modprobe.preload for the scanner to be recognized, i totally missed the point here... Do i need to open a different bug report to move forward ?
(In reply to Yann Cantin from comment #7) > Do i need to open a different bug report to move forward ? It depends: is it the same cause as that of the initial bug report, or a different cause? If it's different, open a new bug report. If it's the same, it's up to you: either open a new one so that it's more readable, with only relevant information, or reuse this one and alter the summary.
Status: REOPENED => NEW
Udev rule are out, so i've opened a new bug report https://bugs.mageia.org/show_bug.cgi?id=16306 Closing this one.
Closed, invalid.
Status: NEW => RESOLVEDResolution: (none) => INVALID