Red Hat Bugzilla – Bug 458914
dolphin . opening Documents folder
Last modified: 2008-10-09 10:25:12 EDT
Description of problem:
dolphin . opens /home/user/Documents directory regardless of where you issue the command. and dolphin .. opens home directory. I deally dolphin . should have opened current working directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.in terminal type dolphin .
opens /home/user/Documents directory
should have opened current directory
Since Fedora 9 Dolphin is now part of kdebase, its no longer packaged separately.
Is there any temporary fix to this problem?
I could not reproduce your problem with the latest kdebase (4.1.0-1) from updates-testing.
Maybe you should consider upgrading to kde 4.1, or wait for its inclusion in stable updates.
My kdebase is also 4.1.0-9.fc9. I also use kde 4.1 from updates testing
Also in my kick off menu system->file manager use to open HOME but now its opening HOME/Documents
I did an update in kdelibs,kdegames and oxygen-icon-theme from testing just now and now its working correctly. I dont know what did the trick.
But file manager from system menu is still opening Documents. Is this the actual behaviour? I remember it opening Home folder before.
Yes File Manager does default to opening the documents folder. There a (RFE) filed requesting we add Home to the top level menu. See https://bugzilla.redhat.com/show_bug.cgi?id=457756 We also discussed this during a recent KDE SiG meeting and you can find the minutes of that meeting here. https://fedoraproject.org/w/uploads/a/a2/Kde-sig-2008-08-05.txt
For now will close this bug as working
The problem exists. Now I can tell you how exactly to reproduce it.
If there is any open dolphin windows dolphin . will open Documents folder irrespective of where the command is issued/.
Rex, Kevin is this a real issue we need to address or is it as I believe working normally?
I can reproduce is. The important part for reproducing this bug is "If there is any open dolphin windows" - Dolphin must be already running for it to misbehave this way.
Thanks for the report. I checked upstream and could not find a matching bug.Please file a bug report in the the upstream bugzilla located at http://bugs.kde.org for the particular component involved.
Once you've filed your bug report to the upstream bugzilla, please add the upstream info to this report. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Setting status to NEEDINFO, and awaiting upstream bug report URL for tracking.
Thanks in advance.
Actually I filed this bug there. At that time I didnt know how to reproduce and they closed it. Now I reopened it.
We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Thank you for the bug report.
*** Bug 466266 has been marked as a duplicate of this bug. ***