Steam client version (build number or date): Mar 14 2022
Distribution (e.g. Ubuntu): Neon
Opted into Steam client beta?: [Yes/No] No.
Have you checked for system updates?: [Yes/No] Yes.
Please describe your issue in as much detail as possible:
Describe what you expected should happen:
I click "Browse local files", Dolphin opens, I click "Open Terminal", and I have a working terminal in that directory.
And what did happen:
I click "Browse local files", Dolphin opens, I click "Open Terminal", and the new Konsole window hangs until I manually kill it. If I let it go long enough, I get the following error:
Warning: Could not start program '/bin/bash' with arguments '/bin/bash'.
Warning: Process operation timed out
This bug also applies to any children Dolphin instances, too. For example, if I right click a folder and select "Open in New Window", a new Dolphin instance will be started and clicking "Open Terminal" in that new instance will cause the same bug, again.
And I never let it run this long until just now while I was typing this out, but apparently if I let it run even longer after that, eventually I will end up with Konsole in a working state.
The whole process takes several minutes before I have a working Konsole. But if I just wait long enough, I guess it will fix itself...? But I would have to wait a long time, every time.
And of course I've tested it outside of Steam and yes it works fine at all other times.
Steps for reproducing this issue:
Install Neon (maybe?) (This may not be Neon or even KDE specific, I honestly don't know. But I do know the Steam Deck uses KDE by default, so this could be important.)
Install Steam and a game.
Right click game in library and click "Browse local files"
When Dolphin opens, click "Open terminal"
I've been having this problem for months and I use this method to quickly open a terminal in that given directory a lot. So thanks in advance for any help on this.
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen:
I click "Browse local files", Dolphin opens, I click "Open Terminal", and I have a working terminal in that directory.
And what did happen:
I click "Browse local files", Dolphin opens, I click "Open Terminal", and the new Konsole window hangs until I manually kill it. If I let it go long enough, I get the following error:
This bug also applies to any children Dolphin instances, too. For example, if I right click a folder and select "Open in New Window", a new Dolphin instance will be started and clicking "Open Terminal" in that new instance will cause the same bug, again.
And I never let it run this long until just now while I was typing this out, but apparently if I let it run even longer after that, eventually I will end up with Konsole in a working state.
The whole process takes several minutes before I have a working Konsole. But if I just wait long enough, I guess it will fix itself...? But I would have to wait a long time, every time.
And of course I've tested it outside of Steam and yes it works fine at all other times.
Steps for reproducing this issue:
I've been having this problem for months and I use this method to quickly open a terminal in that given directory a lot. So thanks in advance for any help on this.