Bug 504032 - Dolphin only recognizes the user's ability to create a new folder on a network share for brief, intermittent time periods
Summary: Dolphin only recognizes the user's ability to create a new folder on a networ...
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: panels: folders (other bugs)
Version First Reported In: 25.04.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-10 22:30 UTC by linuxares
Modified: 2025-05-16 02:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Video of the strange issue (1.88 MB, video/x-matroska)
2025-05-10 22:30 UTC, linuxares
Details

Note You need to log in before you can comment on or make changes to this bug.
Description linuxares 2025-05-10 22:30:22 UTC
Created attachment 181152 [details]
Video of the strange issue

SUMMARY


STEPS TO REPRODUCE
1. Enter some folders (not all got this issue) on my NAS.
2. Right click and it flashes on "Create New".
3. CTRL+SHIFT+N needs to be spammed to be needing to be able to create a folder, claims missing permission until I frame hit right.
4. Once managed to get to create a new folder with CTRL+SHIFT+N, I can move files, delete files etc without problems. Only the "right click" menu is the issue.

OBSERVED RESULT
Uploaded video as mkv, its easier to see the error than the explain it.

EXPECTED RESULT
To get to create a new folder without the permission dropping and gets re-added over and over.

SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-3-cachyos (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Restarted computer, tried to re-add it again, restarted the NAS, no difference.
Comment 1 John Kizer 2025-05-14 18:47:39 UTC
Hi - thanks for your bug report! Just to clarify, how are you connecting to that NAS? When you're seeing this issue, are any messages being printed to the system journal (sudo journalctl --since=-1m should cover that if run right after you saw it)?
Comment 2 linuxares 2025-05-15 16:53:30 UTC
(In reply to John Kizer from comment #1)
> Hi - thanks for your bug report! Just to clarify, how are you connecting to
> that NAS? When you're seeing this issue, are any messages being printed to
> the system journal (sudo journalctl --since=-1m should cover that if run
> right after you saw it)?

Hi!

I have added it to Dolphin via "Remote" and "Network" then "Add Network Folder" and as a SMB drive.
Found something new interesting. If I scroll all the way down and up again in the folders, I can create the folders fine. Like it cached the whole folder so everything is okey?

If I go in to a folder in the NAS where I don't need to scroll, I can create folders instantly again as well.
If I change folder to another one where I need to scroll a little bit, and then go back up again. I can again create the folder etc.



Here is the log:

❯ sudo journalctl --since=-1m
maj 15 18:48:06 <removed-for-privacy>-Asuslaptop sudo[35636]: pam_unix(sudo:session): session closed for user root
maj 15 18:48:07 <removed-for-privacy>-Asuslaptop sudo[35665]:   <removed-for-privacy> : TTY=pts/0 ; PWD=/home/<removed-for-privacy> ; USER=root ; COMMAND=/usr/bin/journalctl --since=-1m
maj 15 18:48:07 <removed-for-privacy>-Asuslaptop sudo[35665]: pam_unix(sudo:session): session opened for user root(uid=0) by <removed-for-privacy>(uid=1000)
maj 15 18:48:10 <removed-for-privacy>-Asuslaptop sudo[35665]: pam_unix(sudo:session): session closed for user root
maj 15 18:48:23 <removed-for-privacy>-Asuslaptop systemd[1]: snapperd.service: Deactivated successfully.
maj 15 18:48:35 <removed-for-privacy>-Asuslaptop sudo[35715]:   <removed-for-privacy> : TTY=pts/0 ; PWD=/home/<removed-for-privacy> ; USER=root ; COMMAND=/usr/bin/journalctl --since=-1m
maj 15 18:48:35 <removed-for-privacy>-Asuslaptop sudo[35715]: pam_unix(sudo:session): session opened for user root(uid=0) by <removed-for-privacy>(uid=1000)
maj 15 18:48:35 <removed-for-privacy>-Asuslaptop sudo[35715]: pam_unix(sudo:session): session closed for user root
maj 15 18:48:40 <removed-for-privacy>-Asuslaptop kioworker[35605]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
maj 15 18:48:40 <removed-for-privacy>-Asuslaptop kioworker[35605]: kf.kio.core: An error occurred during write. The worker terminates now.
maj 15 18:48:44 <removed-for-privacy>-Asuslaptop kioworker[33487]: kf.kio.core: Connection::send() called with connection not inited
maj 15 18:48:44 <removed-for-privacy>-Asuslaptop kioworker[33487]: kf.kio.core: An error occurred during write. The worker terminates now.
maj 15 18:48:44 <removed-for-privacy>-Asuslaptop kioworker[35745]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
maj 15 18:48:44 <removed-for-privacy>-Asuslaptop kioworker[35745]: kf.kio.core: An error occurred during write. The worker terminates now.
maj 15 18:48:46 <removed-for-privacy>-Asuslaptop kioworker[35741]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
maj 15 18:48:46 <removed-for-privacy>-Asuslaptop kioworker[35741]: kf.kio.core: An error occurred during write. The worker terminates now.
maj 15 18:48:55 <removed-for-privacy>-Asuslaptop sudo[35777]:   <removed-for-privacy> : TTY=pts/0 ; PWD=/home/<removed-for-privacy> ; USER=root ; COMMAND=/usr/bin/journalctl --since=-1m
maj 15 18:48:55 <removed-for-privacy>-Asuslaptop sudo[35777]: pam_unix(sudo:session): session opened for user root(uid=0) by <removed-for-privacy>(uid=1000)
Comment 3 John Kizer 2025-05-16 02:56:12 UTC
Thanks!