https://bugs.kde.org/show_bug.cgi?id=472591
--- Comment #2 from Chris <cjd...@brokensolstice.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.
