Bug 13378 - XSane's multipage facility deletes previously scanned images
Summary: XSane's multipage facility deletes previously scanned images
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-05-14 10:18 CEST by Herman Viaene
Modified: 2015-10-25 12:26 CET (History)
0 users

See Also:
Source RPM: xsane-0998
CVE:
Status comment:


Attachments

Description Herman Viaene 2014-05-14 10:18:19 CEST
Description of problem:


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


How reproducible:
Consistently with a specific set of images.

Steps to Reproduce:
1.Start Xsane, choose multipage as target.
2.Choose newly made empty directory to store the scanned images. Loads of free space available
3.Scan pages. After some 30 scans, a few of the previously scanned images are deleted, not only from the multipage list, but also from the disk. Continue scanning and after a random number of scans, the same loss of images repeats.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-08-13 10:47:22 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => supp
Source RPM: xsane.0998 => xsane-0998

Comment 1 Samuel Verschelde 2015-09-11 09:31:19 CEST
Assigning to new maintaner.

Assignee: supp => lists.jjorge

Comment 2 José Jorge 2015-09-14 09:34:22 CEST
Reported upstream, but I am not sure it is still maintained... let's wait a while.
Comment 3 Samuel Verschelde 2015-09-21 13:21:04 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 José Jorge 2015-10-25 12:26:05 CET
No upstream answer.

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


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