Summary: | Dolphin can't write to folder with group write access | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | S. Christian Collins <s_chriscollins> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | asturm, ben-public, bugs.kde.org.facelift226, felixernst, kde-bugs, kfm-devel, linus.kardell, miranda, nicolas.fella, p.r.worrall, stuartksmith |
Priority: | NOR | Keywords: | qt6, regression |
Version: | 24.02.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
S. Christian Collins
2024-03-08 17:28:09 UTC
*** Bug 482993 has been marked as a duplicate of this bug. *** Yep, I am seeing this bug on Arch KDE 6.0.1 and Dolphin 24.02.0 as well. I have a folder with root:users and 775 permissions. My user belongs to the users group and yet can not write in that folder with Dolphin at all. I can reproduce this using the steps provided so setting status to confirmed Dolphin can't create files in testfolder but the file-save dialog in kde apps does allow saving to that folder Operating System: KaOS (2024) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: Wayland *** Bug 483313 has been marked as a duplicate of this bug. *** This seems to be caused by https://invent.kde.org/frameworks/kio/-/merge_requests/1221 A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1581 I am not sure if this was now fixed by https://invent.kde.org/frameworks/kio/-/commit/8e622280d070df7824baffd684e866c085b56f64. At least for me this was fixed after backporting this (among other) commits. Let's consider this fixed then. 🌠S. Christian Collins, Benjamin Xiao, Paul Worrall, if this bug still persists while using KDE frameworks 6.1 (which will be released by us on Fri April 13, 2024 and then arrive at your door step at a point in time controlled by your distribution), we would be interested in hearing from you. Good job everyone! :) I can confirm this bug is indeed fixed in Frameworks 6.1. Thank you! *** Bug 485631 has been marked as a duplicate of this bug. *** |