Bug 10298 - Epson Stylus CX6600 scanner not installed by the system
Summary: Epson Stylus CX6600 scanner not installed by the system
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-26 19:35 CEST by Christian C
Modified: 2013-11-23 16:14 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Christian C 2013-05-26 19:35:57 CEST
Description of problem:

After running the MCC/Hardware/Set up scanner, the message is :
"There are no scanners found which are available on your system".
xsane says : "no devices available"

But the CX6600 printing function works fine on mga-2.

I connected the Epson Stylus CX6600 on an old mdv-2010.0 and the scanner is detected and Xsane opens normally.


Reproducible: 

Steps to Reproduce:
Comment 1 Morgan Leijström 2013-05-30 01:17:14 CEST
see bug 6120 #4

CC: (none) => fri

Comment 2 Christian C 2013-05-30 15:44:14 CEST
I found a workaround in the french mageia forum by installing the proprietary Epson drivers.
See http://www.mageialinux-online.org/forum/topic-15241-1+imprimante-scanner.php
Comment 3 Christian C 2013-05-30 16:05:55 CEST
I tried with 7.1 version as indicated in bug 6120 #4 but it still doesn't work.
Comment 4 Manuel Hiebel 2013-10-22 12:11:29 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 2'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 2 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.

-- 
The Mageia Bugsquad
Comment 5 Manuel Hiebel 2013-11-23 16:14:46 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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