Bug 472858 - Export PDF doesn't save files but says it did
Summary: Export PDF doesn't save files but says it did
Status: RESOLVED FIXED
Alias: None
Product: Skanpage
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.12.3
Platform: Other Linux
: NOR critical
Target Milestone: ---
Assignee: Alexander Stippich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-31 21:06 UTC by David Given
Modified: 2023-09-11 17:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 23.08
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Given 2023-07-31 21:06:24 UTC
STEPS TO REPRODUCE
1. Scan something.
2. Open the 'Export PDF' dialogue.
3. Type in a filename like '/tmp/something.pdf' into the File box and press the Save button.

OBSERVED RESULT

A toast pops up saying the file has been saved, but no file is actually created.

EXPECTED RESULT

File gets saved!

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.0-2-amd64 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Manufacturer: ASUS

ADDITIONAL INFORMATION

If I type in a filename beginning with file:///tmp/something.pdf, the file _does_ get created, so it sounds like something isn't handling the lack of a file handler properly.
Comment 1 Nate Graham 2023-09-07 19:32:14 UTC
Can confirm, this is quite bad. Marking as Critical since this could lead to unintentional data loss. I'll try to look into it soon.
Comment 2 Alexander Stippich 2023-09-10 09:45:17 UTC
This seems to be fixed by
https://invent.kde.org/utilities/skanpage/-/commit/83b814a777a2237c0044d3e12ad896aa17d2a298
Are you able to test Skanpage version 23.08 to confirm?
Comment 3 Nate Graham 2023-09-11 17:01:37 UTC
Right right, I was testing with 23.04. Can confirm it's fixed in 23.08 and current git master. Thanks for the tip!