Hi. I've been getting this error a lot the last few months... I thought it would go away with some updates, so I gave it some time. But it still occurs. When I try to copy a file from one folder to another I get this error: The file or folder Message recipient disconnected from message bus without replying does not exist. The error does not occur on the command line. Only when trying to use dolphin, either from a drag-and-drop or from a copy and paste. STEPS TO REPRODUCE 1. Pull up dolphin on a folder (like /home/myname/Documents/" 2. Open another dolphin instance and navigate to another folder 3. Drag the file from the first dolphin instance to the 2nd. OBSERVED RESULT The file or folder Message recipient disconnected from message bus without replying does not exist. EXPECTED RESULT I expect it to copy the file SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.27.6 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION After a reboot, this behavior stops for a while, but inevitably starts again within half an hour of use or so and persists until reboot, when the cycle begins again. It seems to be worse when I'm using it through a vnc session... but that might be just because I use it that way more often... not sure. But I do use tigervnc over ssl a lot for this system.
Confirm this behavior on two systems: Version 23.04.3 KDE Frameworks Version 5.108.0 Fuse is enabled in kernel. Dolphin is essentially useless at this point.
I found some more information on this. Everything on the Internet seems to be pointing me in the wrong direction when trying to get to the bottom of this. It has nothing to do with Fuse (though that is the most popularly suggested reason). The reason why this occurring is because the system (for whatever reason) doesn't have permissions to /run/user to write a directory for the UID of the user that is launching dolphin. In my case: /run/user/1000. As a test, I changed the permissions of /run/user to 777, and suddenly dolphin works. Perhaps you could restrict it to 775, and put yourself in the root group, as an alternative. Obviously, this is not a good solution -- but it does put a much finer point on what is going on. For me, I just temporarily change the permissions if it is causing me too much of a headache as a work-around, then flip it back. Its something for now... which is better than nothing... I hope the KDE team can come up with a real fix relatively soon.
Unfortunately... my above workaround has ceased to work. I"m now getting: kf.coreaddons: Some files could not be exported. QDBusError("org.freedesktop.DBus.Error.NoReply", "Message recipient disconnected from message bus without replying")