Created attachment 166724 [details] xsession errors SUMMARY *** This moring it seemed all ok, after creating a new user, but I have still problem *** STEPS TO REPRODUCE 1. Click log-out (or restart or shutdown) on kde menu 2. Nothing happens OBSERVED RESULT Power commands (logout, reboot, shutdown) not working EXPECTED RESULT They should work SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION I see this error in xsessione errors dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory Error: Can not contact kdeinit5!
I add also this output from loginctl user-status: mar 08 17:42:25 duns-neon plasmashell[2778]: error creating screencast "Could not find window id 0" mar 08 17:42:25 duns-neon systemd[2510]: Started Dolphin - File Manager. mar 08 17:42:25 duns-neon plasmashell[2778]: error creating screencast "Could not find window id {25a97489-9afa-4ca3-a> mar 08 17:42:25 duns-neon plasmashell[2778]: kpipewire_logging: PipeWire remote error: -2 unknown resource 6 op:7 mar 08 17:42:25 duns-neon dolphin[6720]: inotify_add_watch(/run/udisks2) failed: (Permission denied) mar 08 17:42:33 duns-neon plasmashell[2778]: error creating screencast "Could not find window id 0" mar 08 17:42:33 duns-neon systemd[2510]: Started Waterfox - Web Browser. mar 08 17:42:33 duns-neon systemd[2510]: Started app-flatpak-net.waterfox.waterfox-6775.scope. mar 08 17:43:45 duns-neon plasmashell[2778]: error creating screencast "Could not find window id 0" mar 08 17:43:45 duns-neon systemd[2510]: Started Konsole - Terminal.
I have found where is the problem: in espanso (as service). If I close espanso (espanso stop), I can log-out and reboot and all. Strange, but true :) Therefore I have created a script (espanso stop), made it executable and set as logout script. And now this problem is solved.