After the Plasma 6.7.0 update on Tumbleweed, System Settings crashes when I click on Colors & Themes> Login Screen (SDDM). I’m running an Intel ARC A750 and Wayland.
Running systemsettings kcm_sddm in a terminal starts System Settings at the Login Screen (SDDM) configuration page and I am able to navigate to other settings and return to the SDDM settings without issues. It also prints warnings about themes in the terminal, but no errors.
This could have been happening before the 6.7.0 update and I hadn’t used it so I didn’t notice the problem. I need to know if it’s specific to my system and if it’s a bug in Tumbleweed or Plasma.
When I run just systemsettings in a terminal, it crashes like it does from an app launcher, except I get some warnings about themes and an error about X.
> systemsettings
org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
Using fontconfig file: “/home/john/.config/fontconfig/fonts.conf”
kf.coreaddons: “Could not load plugin from /usr/share/plasma/systemsettings/externalmodules/YaST-systemsettings.desktop: Failed to extract plugin meta data from ‘/usr/share/plasma/systemsettings/externalmodules/YaST-systemsettings.desktop’: ‘/usr/share/plasma/systemsettings/externalmodules/YaST-systemsettings.desktop’ is not a valid ELF object (invalid signature)”
qt.qpa.services: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Connection already associated with an application ID”)
kf.bluezqt: InitManagerJob Error: Job was deleted before finished!
KPackageStructure of KPluginMetaData(pluginId:“LightbulbSplash3D”, fileName: “/home/john/.local/share/plasma/look-and-feel/LightbulbSplash3D/metadata.json”) does not match requested format “Plasma/LookAndFeel”
qt.multimedia.ffmpeg: Using Qt multimedia with FFmpeg version 8.1.2 nonfree and unredistributable
X Error of failed request: BadAccess (attempt to access private resource denied)
Major opcode of failed request: 151 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 28
Current serial number in output stream: 28
Yes. I’ve tried different users and using X or Wayland. It seems strange that it works if you launch system settings directly to the SDDM configuration page, but crashes when launched normally.
This exact crash is happening for me as well. If I search for SDDM in Application Launcher and open settings it works fine, but crashes when systemsettings is launched and then I navigate to SDDM settings page.
On running systemsettings in terminal I get:
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
And then on navigating to SDDM settings (and it crashes) the logs are:
qt.multimedia.ffmpeg: Using Qt multimedia with FFmpeg version n8.1.2 GPL version 3 or later
X Error of failed request: BadAccess (attempt to access private resource denied)
Major opcode of failed request: 150 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 28
Current serial number in output stream: 28
Same crashes here, openSUSE TW with an AMD RX9060XT in a wayland session.
X Error of failed request: BadAccess (attempt to access private resource denied)
Major opcode of failed request: 151 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 28
Current serial number in output stream: 28