Description of problem: Sorry, I don't speak english, but! Please add suport for Xsane (scanner - print Laserjet 100 color MFP M175a).
Please add the output of lscpidrake -v (and why do you assign the bug to yourself ? you want to do it yourself a be a contrib of mageia ?
Source RPM: Scanner for print Laserjet 100 color MFP M1'75a => (none)
@ Ronaldo Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Keywords: (none) => NEEDINFOCC: (none) => marja11Assignee: rochiare => bugsquad
It forgives for the delay friend! I have been very atarefado in the work. The package that you it suggested: âlscpidrake-vâ is not available in the CCM of the Mageia 2 Gnome 64 bits. Where I can find it?
(In reply to comment #1) > Please add the output of lscpidrake -v (In reply to comment #3) > > The package that you it suggested: âlscpidrake-vâ is not available in the CCM > of the Mageia 2 Gnome 64 bits. > Where I can find it? That is not a package, it is a command for in the Konsole or Terminal, and it should contain a space, like in comment 1. On my system (because I log in as marja, and the name of my computer is DenkBlok2), that looks like: [marja@Denkblok2 ~]$ lspcidrake -v Anyway, I understand the printer prints fine? Could you please become root (super user) and give the outputs of the commands: sane-find-scanner and scanimage -L For me that looks like: [root@Denkblok2 marja]# sane-find-scanner and: [root@Denkblok2 marja]# scanimage -L Note that you must see # instead of $ now
CC: (none) => doktor5000
@Ronaldo : If this bug is still valid , can you give answers to comment 4 within 2 weeks. Otherwise we have to close this bug. Roelof
CC: (none) => r.wobben
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD