This is perhaps excessively paranoid, but I accidentally ran ksmserver as root.
I don't suppose this means I've opened myself up to potential vulnerabilities?
It seems fairly innocuous but wanted to be sure. I'm on KDE so ksmserver was
already running and I get this output:
root@computer:/home/user# ksmserver
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000
instead of 0
Qt: Session management error: networkIdsList argument is NULL
Configuring Lock Action
Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus
server")
Failed to connect to the kglobalaccel daemon
QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus
server")
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000
instead of 0
ksmserver: "/KSMserver"
ksmserver: KSMServer: SetAProc_loc: conn 0 , prot= local , file=
@/tmp/.ICE-unix/27257
ksmserver: KSMServer: SetAProc_loc: conn 1 , prot= unix , file=
/tmp/.ICE-unix/27257
ksmserver: KSMServer::restoreSession "saved at previous logout"
"Session bus not found\nTo circumvent this problem try the following command
(with Linux and bash)\nexport $(dbus-launch)"
root@computer:/home/user# QStandardPaths: wrong ownership on runtime directory
/run/user/1000, 1000 instead of 0
Qt: Session management error: Could not open network socket
kwin: unable to claim manager selection, another wm running? (try using
--replace)
Which to me indicates it can't start a new instance as it's already running.
Anyway, is there anything to worry about?
