Bug 15458 - impossible to start brother DCP-j4110DW scanner since lasts mageia 5 updates
Summary: impossible to start brother DCP-j4110DW scanner since lasts mageia 5 updates
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-03-09 07:15 CET by j pierre LAJOIE
Modified: 2015-06-06 10:05 CEST (History)
3 users (show)

See Also:
Source RPM: system-config-printer, sane
CVE:
Status comment:


Attachments

Description j pierre LAJOIE 2015-03-09 07:15:02 CET
Description of problem:
my printer and scanner was properly working .Since lasts (1 week max)  updates 
it was ok with 3.19.04desktop 
Now, it's impossible to start scanner with Xsane , acquisition d'images , or simple scan. Theses softs start correcly, but when i click on "scan" or "preview", the  scanner don't start and the  the soft scan windows disapear.
Itried to re_install drivers => same problème
I tried to add  254 sane.rules and br4scan.rules in /etc/udev/rules.d/ as i read in magéia forums => same problem

Version-Release number of selected component (if applicable):
I use a 64 bits home computer , with mageia5 desktop 3.19.06.mga5

How reproducible:
every time


Steps to Reproduce:
1.start mageia
2.start printer scanner
3.start Xsane 


Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-04-06 19:32:35 CEST
@ j pierre

Sorry for not having replied earlier.

Does this problem still persist now, in a fully updated Mageia 5 ?

CC: (none) => marja11
Whiteboard: (none) => NEEDINFO

Comment 2 Marja Van Waes 2015-04-08 09:16:02 CEST
The problem got solved:

On 08/04/15 06:51, Arbedall wrote:> Sorry i have some problèmes to connect to bugzilla  N° 15458
> 
> 
> Since the big crash Mageia5 boot I reinstalled everything.
>   It was nearly impossible to scan and  print  with the Brother printer, 
> I had installed from mageia5 deposits. There was no error but nothing 
> was printed.
> I rebooted drivers from Brother website (Tar Version) and installed with 
> the Konsole
> Now it's works
> I don't know the reason  why ,

I know someone was working on system-config-printer, yesterday, for an issue reported on dev ml and for bug 15549 
However, I do not know whether s-c-p can cause scanning problems if the printer contains a scanner, too.

@ Florian @ Phillipe

You probably know better than me :-)

> 
> Thanks
> You can close this bug if you want.

Thanks for the feedback :-)

I'll leave it open, in case someone else hits this issue, too, but also for Documentation Team.

If someone has a problem with his scanner, even if the scanner is part of a 3-in-1 printer, he'll look at our help page about scanning, but there it doesn't direct to the Brother website for drivers, so it'll be harder to find a solution or workaround.

However, the help page for printers does give a link to Brother. We should probably add a note at the top of the scanner help page, to check the printer help page, too, in the case of combined printer/scanners.

CC: (none) => doc-bugs, doktor5000, makowski.mageia
Summary: impossible to start scanner since lasts mageia 5 updates => impossible to start brother DCP-j4110DW scanner since lasts mageia 5 updates
Source RPM: printer scanner brother DCP-j4110DW => system-config-printer, sane
Whiteboard: NEEDINFO => (none)

Philippe Makowski 2015-04-10 13:16:04 CEST

CC: makowski.mageia => (none)

Comment 3 Florian Hubold 2015-04-12 18:53:43 CEST
system-config-printer is not relevant for the scanner part. I'm not aware about any recent changes of sane or udev rules, but that doesn't mean there haven't been any of these.

Nevertheless, sounds like a basic permissions problem. Would have been helpful to get some debug information as indicated in the traige guide: https://wiki.mageia.org/en/Triage_guide#Scanner_problems
Maybe also run "journalctl -af" as root and then plugin the printer/scanner and attach the newly added output here.


Without that probably nobody can tell what the issue is.
Florian Hubold 2015-04-12 18:53:53 CEST

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 4 Samuel Verschelde 2015-06-06 01:34:27 CEST
j pierre, could you run "sane-find-scanner" and "scanimage -L" as root and attach the output to this bug report?

Also, run journalctl -af, plug the scanner in, then attach the output to the bug report.

Keywords: (none) => NEEDINFO

Samuel Verschelde 2015-06-06 01:34:55 CEST

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Comment 5 j pierre LAJOIE 2015-06-06 10:05:51 CEST
I'm sorry, I did not fenced bug
The problem disappeared after an update MAGEIA5
I can not say when exactly.
It does work well with SANE
I can even use an old Epson scanner whose drivers are no longer existing for WINDOWS!
What happiness!
thank you for your help

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


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