Description of problem: impossible to configure scanner in MCC (mageia 6- Plasma) Steps to Reproduce: 1.In MCC "configure the scanner" : not in the database 2.Manual configuration. 3. At the top of the window I have "selected a scanner, detected model: epson scanner, port: libusb: 004:011," but looking in the list not epson perfection v350 scanner model. in list for info in MCC >hardware>Explore and configure hardware> scanner : Identification Manufacturer: EPSON Description: EPSON Scanner Media Rating: Log in Bus: USB PCI bus no .: 4 PCI Device #: 11 Manufacturer identifier: 0x04b8 Device ID: 0x012f Various Module: unknown ----
work with mageia5
*** Bug 21275 has been marked as a duplicate of this bug. ***
Assignee: bugsquad => pkg-bugsCC: (none) => thierry.vignaud
The scanner doesn't work in xsane? I have to manually add a libsane.rule for all my Brother MFC for xsane to use it, so you might try that, if xsane can't start it. If this is a bug in MCC scanner module, nevermind... My workaround for my scanner not listed in /usr/lib/udev/rules.d/60-libsane.rules is to find with lsusb the manufacturer and device identifiers (looks like what MCC reports for you): $ lsusb ... Bus 001 Device 003: ID 04f9:0346 Brother Industries, Ltd MFC-J5620DW ... The top of /usr/lib/udev/rules.d/60-libsane.rules explains where your new rule needs to go. I make a comment that describes my machine, copy/paste one of the other rules, and substitute the ID values for my machine from lsusb: # Brother MFC-J5620DW ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="0346", MODE="0664", GROUP="usb", ENV{libsane_matched}="yes" It looks like your scanner already has a rule, so it might work with xsane, if that is what you need: $ grep -B 1 012f /usr/lib/udev/rules.d/60-libsane.rules # EPSON GT-F700 | EPSON Perfection V350 Photo ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012f", MODE="0644", GROUP="usb", ENV{libsane_matched}="yes"
CC: (none) => rolfpedersen
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). 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 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was 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
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => ouaurelien