Hi there Currently does the internal Konsole of Dolphin not find my movements in the GUI - which is pretty dangerous, since i launch commands in directories, where not intended, which is also the reason why i set this to the major level. How can i track this issue? Suggestion: I use on this user profile fish as the default shell, it does not work in bash anyway now. I think bash got maybe infected, since fish went crazy here as well: https://bugs.kde.org/show_bug.cgi?id=381313 I will try in another user and report then again. Thanks a lot in advance
New user is not effected, as bided
This is going to almost certainly a duplicate of the issue you filed two days ago: https://bugs.kde.org/show_bug.cgi?id=381313 fish shell is simply not yet well-supported. *** This bug has been marked as a duplicate of bug 381313 ***
I think it gets pretty clear from my text, that bash is meant. I just suggested, that the misbehave might be connnected with the fish issue.
Confirmed. I didn't find any other open issues related. Konsole/Terminal window in Dolphin doesn't always follow the current directory path shown in GUI. The terminal path can "lag" one step behind. For example: Dolphin GUI shows content of /home/fincer/ directory, while embedded konsole window points to /home/. Usually re-navigating to /home/fincer/ (or whichever) folder in GUI "fixes" the problem. The folder here is just an example, it can be any folder user is browsing. This bug is *very* dangerous while executing commands such as "rm" since unintended operations may take place. As Matthias pointed out, this a major issue and should not be ignored. Dolphin 17.04.3 Konsole 17.04.2
Setting the status to CONFIRMED, as multiple users have reported the bug. It would be great if somebody could provide reproducible steps to trigger such an inconsistency.
*** Bug 399616 has been marked as a duplicate of this bug. ***
STEPS TO REPRODUCE (by swagfortress@gmail.com, thanks!) 1. Open the terminal view 2. $ mkdir -p foo/bar 3. Open foo using the GUI 4. Open bar using the GUI 5. Go up one directory level using the GUI 6. Repeat steps 4-5
Doesn't seem to reproduce anymore. Can someone confirm?
Yes, this seems to be resolved. Had no such issue since years. Thanks a lot
Maybe this was a packaging issue, since I have changed distro since then.
Works for me too using Julian's steps to reproduce.