[Bug 867820] Re: getcwd() function from python module os returns wrong directory in kubuntu
Bug Watch Updater
867820 at bugs.launchpad.net
Thu Jul 5 20:29:32 UTC 2012
Launchpad has imported 12 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=183534.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2009-02-07T09:08:56+00:00 Kde-bugzilla-2 wrote:
Version: unknown (using 4.2.00 (KDE 4.2.0), Gentoo)
Compiler: x86_64-pc-linux-gnu-gcc
OS: Linux (x86_64) release 2.6.25-gentoo-r7-20080501
On my system, KRunner's Command Line plugin uses ~/Documents as the
working directory rather than ~. Thankfully, I habitually prefix all my
home-relative paths with ~/, so I only noticed when I was double-
checking my facts to file a feature request.
It'd probably be best to add a field in the preferences dialog for the
Command Line plugin where the user can set any working directory they
want and to have it default to "~".
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/0
------------------------------------------------------------------------
On 2009-05-29T14:52:13+00:00 Jnelson-kde wrote:
confirmed. openSUSE 11.1 and KDE 4.2.3.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/1
------------------------------------------------------------------------
On 2010-01-09T12:23:54+00:00 Wilder wrote:
here with 4.3 running pwd from krunner (checking the option to work in a terminal) prints the correct path to ~
Was this your issue (and hence it got fixed) or is it something else I don't understand?
Thanks
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/2
------------------------------------------------------------------------
On 2010-01-09T23:56:46+00:00 Kde-bugzilla-2 wrote:
Still unfixed. Put a file named TODO.txt in ~ and another one in
~/Documents with different contents, run `kwrite TODO.txt`, and you'll
see the contents of the one in ~/Documents.
However, your test with pwd shows where things get odd. If you don't run
in a terminal, the working directory is ~/Documents. If you do, it's ~.
(Try "kwrite TODO.txt" in a terminal and it works)
That kind of "smarts" reminds me of Microsoft's Personalized Menus
feature. (Well-intentioned, but poorly thought out and counter-
intuitive)
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/3
------------------------------------------------------------------------
On 2010-01-12T18:42:17+00:00 Wilder wrote:
As I found out (thanks to dfaure) this behaviour turns out to be consistent with the fact that non-KDE apps need to have ~/Documents as a working dir to behave correctly with respect to kde global settings (see old bug 108510).
In this view, forcing ~ to be the working directory is inconsistent, for instance if you type "oowriter" and "oowriter --some-option" you would end up in two different paths, which makes little sense.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/4
------------------------------------------------------------------------
On 2010-01-12T19:31:42+00:00 David Faure wrote:
SVN commit 1073715 by dfaure:
Add the possibility to specify a working directory in KRun::runCommand, and make it
default to documentPath for consistency with apps started via kdeinit.
CCBUG: 183534
M +20 -1 krun.cpp [POSSIBLY UNSAFE: KRun::runCommand]
M +21 -1 krun.h
WebSVN link: http://websvn.kde.org/?view=rev&revision=1073715
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/5
------------------------------------------------------------------------
On 2010-01-13T01:16:12+00:00 Kde-bugzilla-2 wrote:
Not an ideal solution, but I don't see a much better alternative.
Ideally, I'd prefer to see separate settings for documents directory and
default working directory with a selector to choose which one non-KDE
apps fall back to... but that's getting a little excessive.
Given that I'm still in the habit of ignoring KRunner and just using
xbindkeys+gmrun, this bug isn't really a big problem for me any more.
(To be perfectly honest, having more GUI latency on my Athlon64 X2 5000+
than my 2Ghz Celeron (IceWM+PCManFM) after over a year of fixes is
really grating on my nerves and souring me on KDE 4 and the only thing
that's really been keeping me on KDE since Konqueror started sucking is
the open/save dialogs and the effort involved in getting suitable dual-
monitor panels out of an alternative WM. Lesser of two pains in the butt
and all.)
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/6
------------------------------------------------------------------------
On 2010-08-07T23:01:43+00:00 EgLe wrote:
Hello,
i have install Kubuntu Maverick Alpha3 with Krusader 2.2.0beta1 and here
i have the Same problem.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/7
------------------------------------------------------------------------
On 2011-07-06T20:15:46+00:00 flying sheep wrote:
i can confirm that. i commented on a similar bug (related to the kde
paths), but i can’t find it now.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/8
------------------------------------------------------------------------
On 2011-07-25T22:26:02+00:00 Jnelson-kde wrote:
Still a problem as of KDE 4.7rc2.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/9
------------------------------------------------------------------------
On 2011-10-11T12:40:40+00:00 Jonathan Thomas wrote:
*** Bug 226070 has been marked as a duplicate of this bug. ***
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/12
------------------------------------------------------------------------
On 2011-11-26T13:18:43+00:00 J20111130 wrote:
This problem is across all of KDE, and causes grief with interoperability with other desktop environments.
To see for yourself, open a terminal - any terminal program will do, such as xterm.
Maximise it
Enter this command:
john at Boomer:~/Documents$ ls -l /proc/*/cwd | grep $USER
You will see practically everything is running in ~/Documents.
In GNOME, XFCE, LXDE (at least) all the terminal programs are in ~
I guess some place early that KDE does a chdir() to change to the users
Documents directory.
I propose that KDE be changed (urgently!) to start in the Documents
directory only those applications that should be started there. I am, by
the way, not sure that there are any, because any that are will behave
differently depending on whether they are started from a men or from s
(Konsole) commandline.
fwiw I am on Debian Stable and Fedora 16.
Reply at: https://bugs.launchpad.net/kdebase-
workspace/+bug/867820/comments/14
--
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
More information about the kubuntu-bugs
mailing list