[dolphin] [Bug 496145] Gwenview
Pedro
bugzilla_noreply at kde.org
Tue Mar 25 06:41:12 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=496145
Pedro <pehg_ at outlook.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|24.08.3 |git-master
Ever confirmed|0 |1
Assignee|gwenview-bugs-null at kde.org |dolphin-bugs-null at kde.org
Status|REPORTED |CONFIRMED
CC| |kfm-devel at kde.org,
| |pehg_ at outlook.com
Component|general |general
Product|gwenview |dolphin
--- Comment #1 from Pedro <pehg_ at outlook.com> ---
I can confirm this bug in Dolphin 25.07.70. Changing the `Product` to `Dolphin`
since it seems more an issue in Dolphin (or KIO) than Gwenview.
Steps
1. In Dolphin, create a new folder in any user's directory. Call it "test"
2. Open the new folder and create a new text file using the right click
context menu. Call the file "test-file.txt"
3. Go up one level and rename the "test" folder to "test "
4. Enter the renamed folder and try to open the `txt` file by using double
click or pressing enter
Observed: The mouse pointer displays the icon of Kate (or any text editor set
by the user) as if it's loading but the app never launches.
Expected: The app is launched and the file opened.
In `journalctl` I can see the following messages:
```
systemd[1449]: Started
app-org.kde.kate at 0a4a2f72cb1d44e9acceef7936cd65ac.service - Kate - Advanced
Text Editor.
(kate)[1890384]: app-org.kde.kate at 0a4a2f72cb1d44e9acceef7936cd65ac.service:
Changing to the requested working directory failed: No such file or directory
systemd[1449]: app-org.kde.kate at 0a4a2f72cb1d44e9acceef7936cd65ac.service:
Main process exited, code=exited, status=200/CHDIR
systemd[1449]: app-org.kde.kate at 0a4a2f72cb1d44e9acceef7936cd65ac.service:
Failed with result 'exit-code'.
```
Software
Dolphin 25.07.70
Operating System: TUXEDO OS
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-109019-tuxedo (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list