Hello nany, or anyone else affected, Accepted simple-scan into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/simple- scan/46.0-0ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Debcrafters packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2112619 Title: simple-scan returns error when saving when using an empty post- processing value Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Noble: Fix Committed Status in simple-scan source package in Plucky: Fix Committed Status in simple-scan source package in Questing: Fix Released Bug description: [ Impact ] * Errors that occur while running postprocessing scripts in simple-scan will be erroneously reported as save failures instead, leading the user to believe their file has not been saved. * Scripts that output into stdout and stderr are supposed to have this echoed to the terminal when running with simple-scan --debug, but do not. [ Test Plan ] * Run simple-scan with `simple-scan --debug test`. * In the Preferences menu, enable postprocessing. * Set the path of the postprocessing script to a non-existent file. * Attempt to save a scanned file. Saving should succeed, and the postprocessing error should get a popup with the title "Failed to run postprocessing" and a description stating the actual error. * There should be no popup if the postprocessing succeeds. * Error codes in the postprocessing script itself should not result in an error popup, only if the provided script path is incorrect or inaccessible. * Anything the postprocessing script prints to stdout and stderr should be reflected in the terminal running simple-scan. [ Where problems could occur ] * Logic around saving has been changed, so there might be possible regressions when saving without postprocessing enabled, and this scenario should be tested. [ Other Info ] * This bug has already been fixed upstream, and the changes here are cherry-picked from there: https://gitlab.gnome.org/GNOME/simple- scan/-/merge_requests/290 [ Original Description ] Release: Ubuntu 24.04.2 LTS Simple-scan version: 46.0-0ubuntu2 When saving a file, simple-scan warns that the file cannot be saved, even though the file is actually saved. Then saving is proposed when I quit simple-scan and I have to quit without saving. It's not blocking, but it's annoying all the same. I found this answer that solves the problem: https://askubuntu.com/a/1411037 So it seems like the problem is post-processing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2112619/+subscriptions -- Mailing list: https://launchpad.net/~debcrafters-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~debcrafters-packages More help : https://help.launchpad.net/ListHelp
