Bug 356127 - "Save as" dialog for "Save copy as": path editing widget and list widget out of sync
Summary: "Save as" dialog for "Save copy as": path editing widget and list widget out ...
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-30 20:58 UTC by Thomas Fischer
Modified: 2016-08-13 20:44 UTC (History)
2 users (show)

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 Thomas Fischer 2015-11-30 20:58:39 UTC
After a successful "Save copy as" operation, the next save copy as operation will re-use the previous target directory as its base directory in the "save as" dialog in the 'directory' path editing widget. The list widget below, supposed to show the content of this directory (files contained) still shows the current PDF file's directory's location

Reproducible: Always

Steps to Reproduce:
1. Create temporary directories /tmp/A and /tmp/B
2. Create example PDF files /tmp/A/a.pdf and /tmp/A/b.pdf
3. Open /tmp/A/a.pdf in Okular
4. "Save Copy as" this file as /tmp/B/a.pdf
5. Issue "Save Copy as" a second time to get a "Save as" dialog again. Observe that the path editing widget shows "/tmp/B" (last location of a successful "save copy as" operation), whereas the file list widget below shows the content of "/tmp/A" (the current location of the currently open directory), as you will see both a.pdf and b.pdf (the latter does not exist in /tmp/B).
Comment 1 Thomas Fischer 2015-11-30 21:00:14 UTC
When reporting this bug in KDE's Bugzilla, version 1.0.0 was not in the list of available versions. This should be fixed as well.

I am using Okular 1.0.0 on KDE Frameworks 5.16.0 using Qt 5.5.1 on X11/xcb.
Comment 2 Luigi Toscano 2015-11-30 21:12:42 UTC
Version 1.0.0 has not been released. You are using an unsupported branch (frameworks).
Comment 3 Martin Sandsmark 2016-08-13 20:44:12 UTC
Can't reproduce with the latest frameworks branch, which has had a lot of work done, so I'm marking this as resolved. Feel free to re-open if you can reproduce with a version later than ff274fdecc9d872ba8a58ed57cc29c36c30b1e89.