Logout are slow or does not happen

Hi,

There is an issue where when I press to Logout through the UI in KDE, are very slow to happen or does not happen. That is with all applications closed.

Anything that can be done about it?

kwin_wayland[3259]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kernel: kauditd_printk_skb: 168 callbacks suppressed
kwin_wayland[3259]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kernel: kauditd_printk_skb: 2741 callbacks suppressed
plasmashell[3385]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot read property 'forceActiveFocus' of null
ksmserver-logout-greeter[79404]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
ksmserver-logout-greeter[79404]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
ksmserver-logout-greeter[79404]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
ksmserver-logout-greeter[79404]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
ksmserver-logout-greeter[79404]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
kernel: kauditd_printk_skb: 393 callbacks suppressed
kwin_wayland[3259]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kernel: kauditd_printk_skb: 1046 callbacks suppressed
kernel: kauditd_printk_skb: 1691 callbacks suppressed
kernel: kauditd_printk_skb: 1511 callbacks suppressed
kernel: kauditd_printk_skb: 1529 callbacks suppressed
sudo[79978]:  user : a password is required ; TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/true
kernel: kauditd_printk_skb: 1547 callbacks suppressed
kernel: kauditd_printk_skb: 1458 callbacks suppressed
systemd-coredump[80053]: Process 80050 (eglinfo) of user 0 terminated abnormally without generating a coredump.
kernel: kauditd_printk_skb: 8799 callbacks suppressed
kded6[3368]: org.kde.plasma.appmenu: Got an error
kded6[3368]: org.kde.plasma.appmenu: Got an error
kded6[3368]: org.kde.plasma.appmenu: Got an error
kded6[3368]: org.kde.plasma.appmenu: Got an error
kwin_wayland[3259]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
kernel: kauditd_printk_skb: 1625 callbacks suppressed
kernel: kauditd_printk_skb: 5685 callbacks suppressed
kernel: kauditd_printk_skb: 1466 callbacks suppressed
kernel: kauditd_printk_skb: 1582 callbacks suppressed
kernel: kauditd_printk_skb: 1457 callbacks suppressed
plasmashell[3385]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot read property 'forceActiveFocus' of null
kernel: kauditd_printk_skb: 1583 callbacks suppressed
kernel: kauditd_printk_skb: 1954 callbacks suppressed
kernel: kauditd_printk_skb: 3358 callbacks suppressed
kernel: kauditd_printk_skb: 156 callbacks suppressed
kernel: kauditd_printk_skb: 233 callbacks suppressed
kernel: kauditd_printk_skb: 278 callbacks suppressed
kernel: kauditd_printk_skb: 350 callbacks suppressed
kernel: kauditd_printk_skb: 377 callbacks suppressed
kernel: kauditd_printk_skb: 746 callbacks suppressed
kernel: kauditd_printk_skb: 485 callbacks suppressed
kernel: kauditd_printk_skb: 656 callbacks suppressed
kernel: kauditd_printk_skb: 462 callbacks suppressed
kernel: kauditd_printk_skb: 422 callbacks suppressed
kernel: kauditd_printk_skb: 349 callbacks suppressed
kernel: kauditd_printk_skb: 1385 callbacks suppressed
kernel: kauditd_printk_skb: 422 callbacks suppressed
kernel: kauditd_printk_skb: 3203 callbacks suppressed
plasmashell[3385]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot read property 'forceActiveFocus' of null
kwin_wayland[3259]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kwin_wayland[3259]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kwin_wayland[3259]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kwin_wayland[3259]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kwin_wayland[3259]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated.
kernel: kauditd_printk_skb: 3120 callbacks suppressed
systemd-coredump[80687]: Process 80684 (eglinfo) of user 0 terminated abnormally without generating a coredump.

KDE Plasma v: 6.2.4

Same behavior on both X11 and Wayland.

1 Like

Hi - to help folks here best guide you, could you please add your basic system information to this thread? The Info Center app in Plasma has a “Copy Details” button to help with that:

You mentioned logging out is very slow - how many seconds/minutes is it taking?

Is it only the specific “Log Out” action that shows that behavior, or is it all actions (ex. Shut Down or Restart) that cause you to leave your desktop session?

Operating System: CachyOS Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.7-2-cachyos (64-bit)
Graphics Platform: X11 (or Wayland, I use both)
Processors: 16 Ă— AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2

Logout was working before, not sure why it is not now.

Sometimes Restart and Shutdown behaves the same way, but today it worked. I usually tend to use the command line if UI does not work.

Not sure what packages are related to it, if I knew, I could try to reinstall.

Hmm, it might be worthwhile to check the system journal of the previous boot with sudo journalctl --boot -1 after a time when it does occur on Shutdown. You could then check toward the end of that journal entry list to see if anything sticks out as causing a large delay between timestamps.

(The same thing could be done with a time-based journal check when it happens after logging out)

There was an update today.

KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Graphics Platform: X11

After doing a restart, I tried to log out, the UI stopped responding, and it didnt log out. I was only able to launch a terminal through keybindings and then do another reboot.


Some KDE related logs. After the last restart.

kded6[3139]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
kconf_update[3201]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
kconf_update[3201]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_detailsmodesettings.upd defined Version=5 but Version=6 was expected
kconf_update[3201]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_directorysizemode.upd defined Version=5 but Version=6 was expected
kconf_update[3201]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
kconf_update[3201]: kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected
....
kded6[3139]: kf.modemmanagerqt: Failed enumerating MM objects: "org                                      "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"
dbus-broker-launch[2249]: Activation request for 'org.bluez' failed: The systemd unit 'dbus-org.bluez.service' could not be found.
kded6[3139]: colord: EDID ICC Profile already exists "/home/user/.local/share/icc/edid-9204574b4d3e6adfec544b7eed186f4d.icc"
kded6[3139]: kf.bluezqt: PendingCall Error: "The name is not activatable"
kded6[3139]: kf.bluezqt: PendingCall Error: "Could not activate remote peer 'org.bluez': activation request failed: unknown unit"
...
org_kde_powerdevil[3224]: Failed to create wl_display (No such file or directory)
kded6[3139]: kscreen.kded: PowerDevil SuspendSession action not available!
...
plasmashell[3155]: Toolbox not loading, toolbox package is either invalid or disabled.
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth": file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
plasmashell[3155]: Toolbox not loading, toolbox package is either invalid or disabled.
plasmashell[3155]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.69'
kernel: kauditd_printk_skb: 2062 callbacks suppressed
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
plasmashell[3155]: org.kde.plasma.notificationmanager: Setting window before initialising the model NotificationManager::Notifications(0x58a968afb610) QWindow(0x0)
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
plasmashell[3155]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
plasmashell[3155]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
org_kde_powerdevil[3224]: org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback
backlighthelper[3422]: org.kde.powerdevil: no kernel backlight interface found
org_kde_powerdevil[3224]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
org_kde_powerdevil[3224]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
org_kde_powerdevil[3224]: org.kde.kscreen.dpms: DPMS extension not available
org_kde_powerdevil[3224]: org.kde.kscreen.dpms: DPMS extension not available
org_kde_powerdevil[3224]: org.kde.kscreen.dpms: DPMS extension not available
org_kde_powerdevil[3224]: org.kde.powerdevil: Handle button events action could not check for screen configuration
org_kde_powerdevil[3224]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
kernel: kauditd_printk_skb: 331 callbacks suppressed
plasmashell[3155]: file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot call method 'forceActiveFocus' of null
plasmashell[3155]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
plasmashell[3155]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
plasmashell[3155]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
plasmashell[3155]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
kwin_x11[3140]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
kernel: kauditd_printk_skb: 87 callbacks suppressed
systemd[2742]: dbus-:1.2-org.kde.KSplash@0.service: Failed with result 'exit-code'.
plasmashell[3155]: qt.svg: <input>:1:14095: Could not resolve property: #linearGradient10962

And just double-checking, does the same issue occur under a freshly-created new user account? Just to rule out something that’s configured or cached or something like that in your specific user account.

I did a lot of configuration, but nothing related to logout, restart or shutdown. Unsure of the new user.

Restart and Shutdown for the most parts still works in the UI, not always. Only logout seems to mostly have the problem. I dont use any other option to know about them.

What sort of thing would cache, that would make it not work?

Not sure, but testing under a new user can generally help rule out things that are unique to your existing user’s ~/.config , ~/.local , etc. directories. If it happens under a fresh user account, then that at least some combination of system-level components and default user settings is at fault - not some custom configuration that was set after installation, and might have some weird unforeseen interaction.

Unless a specific thing is pointed, I dont see the point in doing it, because if I cannot configure KDE, i’d rather not use it.

I dont see how that is going to show the cause. It might work, but then what. I still would not know the cause.

I just found the reason.

I noticed today that after trying it out, some tray closed, but some didnt.

Then there was one in between that were not native. And that was it.

I removed the package that kept the tray there. cloudflare-warp-bin

Weird that it doesnt close as restart does.

Anyhow, it has been reported to bugs.kde