[Bug 867820]

[vontrapp]

This is a highly annoying bug.. I  confirm that it is across all of KDE
as comment 11 says.

No program should assume it will be started from any particular cwd and
use that cwd blindly. Also, no program should assume that any cwd that
it DOES start in is invalid and should be overridden. Either case
violates the principle of least surprise. Either a program should go to
some specific directory, hopefully configured and not hardcoded (and
ignore cwd altogether), OR the program should graciously use whatever
cwd happens to be.

So, that said, the problem is NOT with whatever programs might be doing
with the cwd that the parent-of-all KDE is passing on to them. In most
cases they ARE doing the correct thing. In the cases where having KDE
*not* use ~/Documents as its cwd would break some programs, it is
*those* programs that are doing something wrong.

The problem, then, is KDE changing cwd to ~/Documents in the parent
process that forks all other gui applications, and changing it back to ~
*should* not pose any damage. If it does, it is a bug in something else.

Some grepping revealed absolutely no textual or otherwise configuration
files that determine where KDE changes its cwd to. /usr/bin/kde4-config,
however, matches for both DOCUMENTS and Documents.

And no, I do not believe changing DOCUMENTS=Documents in /etc/xdg/user-
dirs.defaults is a proper or desirable solution.

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/867820

Title:
  getcwd() function from python module os returns wrong directory in
  kubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/867820/+subscriptions