https://bugs.kde.org/show_bug.cgi?id=500038
Robin Laing <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from Robin Laing <[email protected]> --- What I am adding may or not be useful. I am having lots of switch user freezes after the latest updates. Fedora 42 Nvidia graphics KDE 6.5.1 This has caused me major headaches in the last 24 hrs. Many issues with switch users but the last 24hrs have been a nightmare causing multiple reboots. Looking through my journal logs I see many error messages that are not making sense. I don't know how to use the journal logs properly yet. I have sshd into the system when it has frozen and in one case, sddm_helper_start_wayland was frozen. Killed the process and I was able to use the machine again. I also Just some of the journal messages I am getting after logging into a new session. sddm-helper-start-wayland[23235]: "kwin_scene_opengl: Could not delete render time query because no context is current\n" sddm-greeter-qt6[23264]: file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml:238:17 Parameter "username" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead. sddm-helper-start-wayland[23235]: "QSGContext::initialize: stencil buffer support missing, expect rendering errors\n" sddm-helper-start-wayland[23235]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\n" When the system was locked, I have hundereds of this message. kwin_wayland[18168]: kwin_wayland_drm: Failed to create a framebuffer: Invalid argument And a whole series of these with the last cfg_ being different. plasmashell[18355]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationContainmentAppearance.qml: Setting initial properties failed: ConfigurationContainmentAppearance does not have a property called cfg_labelWidth I also have these but not sure if they are related or just another issue. kconf_update[18512]: kf.config.kconf_update: /usr/share/kconf_update/webenginepart.upd defined Version=5 but Version=6 was expected kconf_update[18512]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected kded6[18330]: kf.dbusaddons: The kded module name "oom-notifier" is invalid! kded6[18330]: QDBusObjectPath: invalid path "/modules/oom-notifier" kded6[18330]: kf.dbusaddons: The kded module name "kded_plasma-welcome" is invalid! kded6[18330]: QDBusObjectPath: invalid path "/modules/kded_plasma-welcome" In one of the many crashes where the screen and keyboard were not responsive to changing ttys, I killed startplasma-wayland of one of the sessions and I was able to get back into the computer. One of the user sessions related to the startplasma-wayland was terminated. Still better than a hard reboot. I am also getting a message about xcb and xdg which are not installed. Again, don't know if they are related or not. I don't have a gnome desktop installed on this system. -- You are receiving this mail because: You are watching all bug changes.
