Summary: | Unexpected behaviour after cancel scanning in Skanpage | ||
---|---|---|---|
Product: | [Applications] Skanpage | Reporter: | Olga <urozhaevaoo> |
Component: | general | Assignee: | Alexander Stippich <a.stippich> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | j-p-t |
Priority: | NOR | ||
Version First Reported In: | 24.12.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/libraries/ksanecore/-/commit/a634ea0406f091cff46f9320c9e977aaee814907 | Version Fixed In: | |
Sentry Crash Report: |
Description
Olga
2025-03-12 15:07:44 UTC
Does this also happen with other scan software on linux, i.e. GNOME's Document Scanner? (In reply to Alexander Stippich from comment #1) > Does this also happen with other scan software on linux, i.e. GNOME's > Document Scanner? I've tried such softwares as Simple-scan (https://apps.gnome.org/en/SimpleScan/) and XSane (https://wiki.ubuntuusers.de/XSane/) and haven't faced with this problem A possibly relevant merge request was started @ https://invent.kde.org/libraries/ksanecore/-/merge_requests/34 Great find! I could try if this helps with my samsung printer. (now I got three different drivers/backends which all s**ck) if I build from AUR skanpage-git v24.01.90.r110.gd6faca0-1 Will this include the fix, or do I have to wait for an AUR update? Git commit a634ea0406f091cff46f9320c9e977aaee814907 by Alexander Stippich. Committed on 04/06/2025 at 17:23. Pushed by astippich into branch 'master'. call sane_cancel when a user cancels the scan M +1 -0 src/scanthread.cpp https://invent.kde.org/libraries/ksanecore/-/commit/a634ea0406f091cff46f9320c9e977aaee814907 This has just been merged to the master branch, so it likely was not included before in any packaged git version. You would need a git snapshot from today of the KSaneCore library to be able to test the fix. |