Bug 480425 - Skanlite runs the scan again after saving a scanned image
Summary: Skanlite runs the scan again after saving a scanned image
Status: RESOLVED WORKSFORME
Alias: None
Product: Skanlite
Classification: Applications
Component: general (show other bugs)
Version: 23.08.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-28 10:52 UTC by Mohammed Khoory
Modified: 2024-04-22 05:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mohammed Khoory 2024-01-28 10:52:12 UTC
SUMMARY
When I scan a document wirelessly, it opens a dialog with the scanned result. After saving the document, for some reason, skanlite sometimes runs the scanner again. This sometimes happens and sometimes doesn't, if I recall correctly. I'm not sure what triggers it.

STEPS TO REPRODUCE
1. Run skanlite
2. Preview a document
3. Make a selection in the preview
4. Scan the document
5. In the document that pops up, save the document (I used PDF)

OBSERVED RESULT
The documents gets saved, and the dialog closes, but the scanner is scanning again unnecessarily (sometimes).

EXPECTED RESULT
The document gets saved and the dialog closes only

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro Linux 
KDE Plasma Version:  KDE Plasma 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
I am using an HP Officejetpro 8620 via network (laptop connected wirelessly, scanner is via ethernet). I am using the flatbet scanner at 300dpi.
Comment 1 Kåre Särs 2024-01-29 12:29:35 UTC
Hi,

Thanks for the report, I think the reason might be that you have not disabled the automatic area detection and it has probably detected two areas and then go on to scan the next area.

Might that be the issue?
Comment 2 Bug Janitor Service 2024-02-13 03:45:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-02-28 03:46:38 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 4 Mohammed Khoory 2024-04-21 13:04:28 UTC
Hello, my apologies for not replying sooner. I wanted to revisit the bug when I wanted to do another scan, but this didn't happen as soon as I thought.

I tried to replicate this issue on my machine, but for some reason I couldn't. Perhaps a newer version of skanlite was instaleld that solved this issue?

I also tried to trigger the automatic area detection to see if that was the issue.  but for some reason it just wasn't working for me. To do this, in the configure dialog, I made sure that "Disable automatic selections" is unchecked. I then scanned two separate flyers on my flatbed scanner to ensure that it can clearly detect two items. But it didn't seem to detect a single item. I'm not sure if I'm doing anything wrong here.
Comment 5 Kåre Särs 2024-04-22 05:57:46 UTC
Thanks for the update.

The area detection maybe just could not find the two areas... 

If you cannot reproduce the unexpected behavior, maybe we can leave this as WORKSFORME?

/Kåre