SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Create folder with name ```[www.qqqq, Вввв ВАвввввввв ] Ууууу ууууууууууу-ццццццццццццц (4444)``` 2. Press f4 to open terminal 3. Open folder by double clicking OBSERVED RESULT Opening the wrong path EXPECTED RESULT The path is right SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION video of the problem https://cloud.mail.ru/public/77XD/HQSPqP7X6
I'm unable to reproduce this issue. I see in your terminal you're using Powerline with zsh maybe? I tried using my default shell of fish and bash with the exact naming of the folder as you described in your steps. Can you please re-test with bash as the shell and confirm if this works for you?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Justin Zobel from comment #1) > I'm unable to reproduce this issue. I see in your terminal you're using > Powerline with zsh maybe? > > I tried using my default shell of fish and bash with the exact naming of the > folder as you described in your steps. > > Can you please re-test with bash as the shell and confirm if this works for > you? The problem does not occur when using bash. Only on zsh