Bug 493815 - In Dolphin terminal prompt path does not switch properly with F4
Summary: In Dolphin terminal prompt path does not switch properly with F4
Status: RESOLVED UPSTREAM
Alias: None
Product: dolphin
Classification: Applications
Component: panels: terminal (show other bugs)
Version: 24.08.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-29 08:34 UTC by Cherkah
Modified: 2024-10-29 17:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
inconsistencies prompt path (305.28 KB, video/webm)
2024-09-29 08:34 UTC, Cherkah
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cherkah 2024-09-29 08:34:55 UTC
Created attachment 174193 [details]
inconsistencies prompt path

SUMMARY
the terminal prompt opened in dolphin via the F4 shortcut gives a different path for each activation.
see attachment

STEPS TO REPRODUCE
1. open dolphin and press F4 (shortcut) several times
2. observe the prompt path
3. 

OBSERVED RESULT
every time the terminal is called, the prompt path is not the same.
this does not happen if the "exit" command is passed

EXPECTED RESULT
that the prompt path is the same: the path of the current tab/window

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Graphics Platform: Wayland


ADDITIONAL INFORMATION
Comment 1 TraceyC 2024-10-02 20:16:29 UTC
Thank you for the bug report and the screen recording. I see the problem you're describing.

What's happening is that when opening the terminal pane is: It does cd to / and then cd to the directory that's open in the Dolphin window. Then clear. So

cd /
cd ~/directory
clear

On your system, it's getting hung on "cd /" and not then changing to the current directory.

On my system, if I am looking at ~/Music, I see this in the terminal pane when I open the terminal, close and then re-open

cd /
cd ~/Music

We need more information to find out why Dolphin is hanging when it does on your system. 

1. Start up Dolphin
2. You'll need to get the pid of Dolphin with
ps -ef | grep Dolphin

The first number is the pid. In this example the pid is 381805

❯ ps -ef |rg Dolphin
tracey    381805  350334  0 15:11 pts/4    00:00:00 rg -S Dolphin
❯ pgrep 381805

3. Now reproduce the bug. While the terminal in Dolphin is hung at cd /   run the following command (put the pid you got in this command instead of PID)
gdb attach -p $(PID)

4. If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
5. When you see a prompt that says "(gdb)", type "bt" and press the enter key.
6. If it says "--Type  for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the "c" key.
7. Copy-and-paste the contents of the terminal window into a comment here.

Thanks!
Comment 2 Cherkah 2024-10-13 13:32:12 UTC
even after Downloading the separate debug info, i got nothing && the process exited normally.

i'm pretty sure that the issue come from on the eza side (so on my side).*
i'm gonna to investigate my zsh conf files (zshrc / zaliases/ functions) and get in touch with the eza github community.

If i can find a relevant info related with dolphin, i'll inform you

thx
Comment 3 Bug Janitor Service 2024-10-28 03:46:43 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Cherkah 2024-10-29 15:48:57 UTC
after trying several times to debug this problem in gdb, i found nothing to share: gdb provides absolutely nothing. only lines like that:
```
[Detaching after vfork from child process 8565]
[Detaching after vfork from child process 8566]
Downloading 1.94 M separate debug info for /usr/lib/libnss_systemd.so.2
[Detaching after vfork from child process 8569]                                                                    
[Detaching after vfork from child process 8570]
Downloading 2.67 M separate debug info for /usr/lib/qt6/plugins/kf6/parts/konsolepart.so
Downloading 48.81 M separate debug info for /usr/lib/libkonsoleprivate.so.24.08.2                                  
Downloading 1.29 M separate debug info for /usr/lib/libKF6Pty.so.6                                                 
[Detaching after fork from child process 8591]                                                                     
[New Thread 0x7cf5ce4006c0 (LWP 8678)]
[Detaching after vfork from child process 8700]
[New Thread 0x7cf5cda006c0 (LWP 8708)]
[Thread 0x7cf5ce4006c0 (LWP 8678) exited]
[New Thread 0x7cf5ce4006c0 (LWP 8774)]
[Detaching after vfork from child process 8841]
[Thread 0x7cf5ce4006c0 (LWP 8774) exited]
[New Thread 0x7cf5ce4006c0 (LWP 8875)]
Downloading 3.60 M separate debug info for /usr/lib/qt6/plugins/kf6/kwindowsystem/KF6WindowSystemKWaylandPlugin.so
[Thread 0x7cf5ce4006c0 (LWP 8875) exited]                                                                          
[Detaching after fork from child process 8952]
[Detaching after fork from child process 8954]
[New Thread 0x7cf5ce4006c0 (LWP 8971)]
[Thread 0x7cf5ce4006c0 (LWP 8971) exited]
This plugin supports grabbing the mouse only for popup windows
This plugin supports grabbing the mouse only for popup windows
```

however, i can say that the problem is only if i call the terminal with less than 3 seconds of interval. after 3 seconds, the terminal prompt displays the location of the folder presented in dolphin.
Comment 5 TraceyC 2024-10-29 17:01:32 UTC
Thanks for going through the effort of trying to get a backtrace. I'm going to close this out for now, since you suspect this is being caused by eza. Feel free to re-open it if it turns out that's not the case.

For reference in case its needed in the future
https://github.com/z-shell/zsh-eza