https://bugs.kde.org/show_bug.cgi?id=489008
Bug ID: 489008
Summary: Cannot open files in /dev with error
"WorkingDirectory= may not be below /proc/, /sys/ or
/dev/"
Classification: Applications
Product: dolphin
Version: 24.05.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: eamonn...@protonmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
When trying to open a file in "/dev", such as log files in "/dev/shm/", Dolphin
is unable to open them and displays the error "WorkingDirectory= may not be
below /proc/, /sys/ or /dev/" when trying to open them using any application
such as Kate. However the applications themselves can open these files. You can
run `kate /dev/shm/myfile.log` and open it just fine. Likewise you can open
these files just fine, for example opening files in this directory with Kate
using its file picker works just fine. It is only Dolphin which does not let
you open files in this directory.
This is a regression in 6.1.0, and was not present in 6.0.5 and below - I
regularly open files from /dev/shm, which is how I noticed this, but this bug
is specific to any files in /dev.
STEPS TO REPRODUCE
1. Navigate to /dev in Dolphin.
2. Attempt to open a file in this directory.
3. Dolphin will display the message "WorkingDirectory= may not be below /proc/,
/sys/ or /dev/"
a. When trying to double-click the file, it will show it in a red box
inside the Dolphin window
b. When trying to open the file by right clicking -> Open With ->
Application, the error is displayed in a dialog box.
OBSERVED RESULT
Dolphin cannot open files in /dev, whereas applications themselves (such as
Kate) can open files in this directory.
EXPECTED RESULT
Dolphin should be able to open files in /dev, in particular /dev/shm as some
applications will put logging information there.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.5 Linux Zen
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
ADDITIONAL INFORMATION
I confirmed this issue across two separate machines, so I do not think it is an
isolated problem.
If this is intentional, this is going to be quite problematic for applications
that put logging information in /dev/shm, and should perhaps be reconsidered?
--
You are receiving this mail because:
You are watching all bug changes.
