Summary: | Opening a symbolic link folder when the Terminal Panel is open changes the URL to the actual location | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Frank Reininghaus <frank78ac> |
Component: | panels: terminal | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | audvare, frank78ac, konsole-devel, manuavazquez, oleh |
Priority: | NOR | Keywords: | reproducible |
Version: | 2.0.95 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kde-baseapps/2e123de94f6d654cbe37e4ac1841422632ca5451 | Version Fixed In: | 4.10.3 |
Description
Frank Reininghaus
2012-06-17 07:09:53 UTC
*** Bug 302254 has been marked as a duplicate of this bug. *** Sorry for the late response. Unfortunately, that behavior of konsolepart can't be "fixed" under current implementation. The way konsole/konsolepart getting to know the working directory of the process(shell) in Linux is looking at /proc/<pid>/cwd, which is itself already a symlink pointing to the "actual location". So although the process(shell) may understand symlink and target, konsole only knows the target (actual location). Thanks for the explanation Jekyll! In that case, the best way to fix this is probably to check on the Dolphin side if the current URL of the view is a symlink that points to the URL received from the Konsole part, and in that case, ignore the message received from the Konsole part. I'll add that to my TODO list. Resetting assignee to default as per bug #305719 Git commit 2e123de94f6d654cbe37e4ac1841422632ca5451 by Frank Reininghaus. Committed on 02/05/2013 at 19:38. Pushed by freininghaus into branch 'KDE/4.10'. Do not change the view URL if it is a symlink to the current directory FIXED-IN: 4.10.3 REVIEW: 110233 M +6 -1 dolphin/src/panels/terminal/terminalpanel.cpp http://commits.kde.org/kde-baseapps/2e123de94f6d654cbe37e4ac1841422632ca5451 *** Bug 314246 has been marked as a duplicate of this bug. *** (In reply to comment #5) I confirm that this has been fixed in KDE 4.10.3. Thank you for the much needed fix. This was the most annoying bug in the whole KDE for me. |