https://bugs.kde.org/show_bug.cgi?id=393447
Bug ID: 393447
Summary: Kleopatra uses current directory of parent process
Product: kleopatra
Version: 3.1.0
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
When Kleopatra is opened (if it is not already running in the background) it
will have its current directory (working directory) typically set to that of
its parent process.
This means that, for example, if I open a file associated with Kleopatra from
Explorer, and if Kleopatra is not already running in the background, then
Kleopatra will open and perform any operations on the file, and stay open in
the background when finished. However, Kleopatra's current directory will be
set to the directory the file was in, even after it is finished with the file.
In turn, this leads to issues such as when launching Kleopatra by clicking a
file on a removable disk, and letting Kleopatra stay open after it finishes,
then Windows will complain that the "device is currently in use" if I try
ejecting the disk, since there is still an open handle to a directory on the
disk, and even though the Kleopatra has closed any handles to the file I
opened.
I'm not sure what the general advice or trends are regarding which working
directory a program should use. I'm just under the impression it isn't
necessary for a program like Kleopatra to need to use the parent process'
current directory since it doesn't appear to affect functionality.
--
You are receiving this mail because:
You are on the CC list for the bug.
