[dolphin] [Bug 493815] inconsistencies prompt path in dolphine terminal (F4)

[TraceyC]

https://bugs.kde.org/show_bug.cgi?id=493815

TraceyC <kdedev at tlcnet.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdedev at tlcnet.info
         Resolution|---                         |BACKTRACE
             Status|REPORTED                    |NEEDSINFO

--- Comment #1 from TraceyC <kdedev at tlcnet.info> ---
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!

-- 
You are receiving this mail because:
You are on the CC list for the bug.