Bug 503277 - PDF-export path selection not working
Summary: PDF-export path selection not working
Status: RESOLVED FIXED
Alias: None
Product: Skanpage
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Stippich
URL:
Keywords:
: 503705 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-04-24 10:13 UTC by s.h.
Modified: 2025-05-03 13:38 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description s.h. 2025-04-24 10:13:15 UTC
If i want to export a scanned image as pdf I can not choose a destination file.
STEPS TO REPRODUCE
1. Scan or import image
2. click "PDF exportieren" (export pdf)
3. select "save as...", navigate to location, enter file name and click "save"

OBSERVED RESULT
file is not changed and export is saved to wrong location with wrong name.

EXPECTED RESULT
Selected file is used and export saved correctly

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
Running Skanpage from a konsole shows the following error message on clicking "save" in the filechooser dialog:
qrc:/qml/ExportDialog.qml:126: ReferenceError: fileNameItem is not defined
qrc:/qml/ExportDialog.qml:126: ReferenceError: fileNameItem is not defined
Comment 1 Alexander Stippich 2025-04-24 17:04:24 UTC
Git commit 2cd831866338cd167d693c6b17f6c08d5ec6cf8d by Alexander Stippich.
Committed on 24/04/2025 at 17:03.
Pushed by astippich into branch 'release/25.04'.

reinsert id in export dialog

M  +1    -0    src/qml/ExportDialog.qml

https://invent.kde.org/utilities/skanpage/-/commit/2cd831866338cd167d693c6b17f6c08d5ec6cf8d
Comment 2 Alexander Stippich 2025-05-03 13:38:35 UTC
*** Bug 503705 has been marked as a duplicate of this bug. ***