https://bugs.kde.org/show_bug.cgi?id=356098
--- Comment #6 from nsane...@gmail.com --- I'm not sure if this is a systemd bug or a dolphin bug. The relevant journalctl lines pertinent to the problem are: May 03 18:47:15 Home-PC su[943]: Successful su for root by hodor May 03 18:47:15 Home-PC su[943]: + /dev/pts/3 hodor:root May 03 18:47:15 Home-PC kdesud[939]: org.kde.kdesud: Password set! May 03 18:47:15 Home-PC su[943]: pam_unix(su:session): session opened for user root by (uid=1000) May 03 18:47:15 Home-PC kdesud[939]: org.kde.kdesud: priority set to 50 May 03 18:47:15 Home-PC su[943]: pam_systemd(su:session): Cannot create session: Already running in a session May 03 18:47:15 Home-PC kdesud[939]: org.kde.kdesud: Scheduler set to 0 May 03 18:47:15 Home-PC su[943]: pam_unix(su:session): session closed for user root May 03 18:47:15 Home-PC kdesud[939]: org.kde.kdesud: Executing command: " dolphin" May 03 18:47:15 Home-PC kwin_x11[762]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6328, resource id: 60817423, major code: 18 (ChangeProperty), minor code: 0 May 03 18:47:15 Home-PC su[949]: Successful su for root by hodor May 03 18:47:15 Home-PC su[949]: + /dev/pts/3 hodor:root May 03 18:47:15 Home-PC su[949]: pam_unix(su:session): session opened for user root by (uid=1000) May 03 18:47:15 Home-PC su[949]: pam_systemd(su:session): Cannot create session: Already running in a session May 03 18:47:15 Home-PC su[949]: pam_systemd(su:session): Cannot create session: Already running in a session May 03 18:47:15 Home-PC dolphin[955]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC dolphin[955]: Cannot creat accessible child interface for object: PlacesView(0x286c0a0) index: 21 May 03 18:47:16 Home-PC dolphin[955]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC dolphin[955]: klauncher not running... launching kdeinit May 03 18:47:16 Home-PC kdeinit5[966]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC klauncher[967]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC klauncher[967]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) May 03 18:47:16 Home-PC klauncher[967]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC kdeinit5[972]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC dolphin[955]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC kdeinit5[973]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC dolphin[955]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 May 03 18:47:16 Home-PC kdeinit5[974]: QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0 It should be using /run/user/0 for the socket files. It instead tries to use the user's XDG_RUNTIME_DIR. It detects the incorrect perms and, I guess, defaults to / instead. It appears to be similar in nature to this bug: https://lists.freedesktop.org/archives/systemd-devel/2013-November/014370.html -- You are receiving this mail because: You are watching all bug changes.
