Bug 18779

Summary:	Pixma backend broken in latest sane-backend needs patching
Product:	Mageia	Reporter:	jorma mölliäinen <mynicemailbox>
Component:	RPM Packages	Assignee:	José Jorge <lists.jjorge>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	doktor5000, marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
URL:	https://alioth.debian.org/tracker/?group_id=30186&atid=410366&func=detail&aid=315248
Whiteboard:
Source RPM:	sane	CVE:
Status comment:

Description jorma mölliäinen 2016-06-23 19:18:15 CEST

Description of problem:
Pixma backend on sane-backends is broken. Scanner is always busy, can't connect. 

Version-Release number of selected component (if applicable):
sane-backends supplied with mageia. no updates available

How reproducible: Does not need to be confirmed, sane-backends need an update with pixma backend patch. 


Steps to Reproduce:
1.See the link for further details https://alioth.debian.org/tracker/?group_id=30186&atid=410366&func=detail&aid=315248

Patch has been available since January this year which has not made it to the latest release, but apply patch to the source. Affects many Canon Pixma multifunctional printer scanners. Makes scanning stall. Unusable. Problem is not with usblp as it was previously.. There is no workaround.

Marja Van Waes 2016-06-24 17:01:39 CEST

CC: (none) => marja11
Assignee: bugsquad => lists.jjorge
Source RPM: sane-backends => sane

Florian Hubold 2018-04-13 18:27:01 CEST

CC: (none) => doktor5000

Comment 1 Marja Van Waes 2018-10-07 15:03:39 CEST

Hi Jorma,

Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. If you'd like to help maintain sane or any other package, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

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