Bug 2029 - Confusing xsane GUI message when the scanner firmware is missing
Summary: Confusing xsane GUI message when the scanner firmware is missing
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Tomas Kindl
QA Contact:
URL:
Whiteboard: OK
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-04 21:31 CEST by Radu Cristian Fotescu
Modified: 2012-12-02 14:36 CET (History)
2 users (show)

See Also:
Source RPM: xsane-0.998-1.mga1
CVE:
Status comment:


Attachments

Description Radu Cristian Fotescu 2011-07-04 21:31:13 CEST
Description of problem:

When the scanner doesn't work because the firmware is missing, xsane raises the following error message in a dialog:

Failed to open device `gt68xx:libusb:002:005': Invalid argument

The user can't find any information in this text. Only by running xsane from a terminal the real error is shown:

[gt68xx] Couldn't open firmware file (`/usr/share/sane/gt68xx/ccd68861.fw'): No such file or directory

(that was for my Genius scanner, the message should change depending of your scanner)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Samuel Verschelde 2011-10-01 01:03:07 CEST
Assigning to maintainer now that our maintainer's database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

CC: (none) => stormi
Assignee: bugsquad => supp

Comment 2 Marja Van Waes 2012-01-06 21:10:59 CET
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED


@ Tomas
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Comment 3 Tomas Kindl 2012-07-01 14:54:05 CEST
Thing is that xsane only generates 2 error messages (invalid argument + invalid option), rest of stuff incl. Radu's invalid fw message is generated by SANE backend and xsane doesn't have any interface for reporting these errors. So we can either modify one of generic xsane error messages to say "Invalid argument, possibly missing firmware!" or forget about it (as said modification can cause many misleading bug reports)...

Whiteboard: (none) => OK

Comment 4 Manuel Hiebel 2012-11-05 16:54:05 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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

--
Mageia Bugsquad
Comment 5 Manuel Hiebel 2012-12-02 14:36:29 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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.

--
Mageia Bugsquad

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


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