From a6ba0cfc9743167943dd5fbda3ad6be4b295e977 Mon Sep 17 00:00:00 2001 From: Jonas Kvinge Date: Wed, 7 Jun 2023 01:23:01 +0200 Subject: [PATCH] KDSingleApplicationLocalSocket: Exclude XDG_SESSION_ID from socket name --- .../kdsingleapplication/kdsingleapplication_localsocket.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/3rdparty/kdsingleapplication/kdsingleapplication_localsocket.cpp b/3rdparty/kdsingleapplication/kdsingleapplication_localsocket.cpp index dc4a4291e..5dc6184a7 100644 --- a/3rdparty/kdsingleapplication/kdsingleapplication_localsocket.cpp +++ b/3rdparty/kdsingleapplication/kdsingleapplication_localsocket.cpp @@ -47,9 +47,9 @@ KDSingleApplicationLocalSocket::KDSingleApplicationLocalSocket(const QString &na { #if defined(Q_OS_UNIX) /* cppcheck-suppress useInitializationList */ - m_socketName = QStringLiteral("kdsingleapp-%1-%2-%3") + m_socketName = QStringLiteral("kdsingleapp-%1-%2") .arg(::getuid()) - .arg(qEnvironmentVariable("XDG_SESSION_ID"), name); + .arg(name); #elif defined(Q_OS_WIN) // I'm not sure of a "global session identifier" on Windows; are // multiple logins from the same user a possibility? For now, following this: