1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.KDE

  • Bullseye KDE logout lasts 10 sec.minimum

    From Herbert@21:1/5 to All on Sat Oct 9 12:30:02 2021
    Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user
    same behavior.
    Any idea about the reason ?

    Herbert S.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Benjamin Eikel@21:1/5 to All on Sat Oct 9 15:40:02 2021
    Dear Herbert,

    Am Samstag, 9. Oktober 2021, 12:17:01 CEST schrieb Herbert:
    Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user same behavior.
    Any idea about the reason ?

    I have no idea about the reason, but I think I suffer from the same problem with KDE Plasma (5.21.5 at time of this writing) in Debian unstable. I thought that it might be some other services running on the machine, but I see this on my desktop and laptop. Will try to investigate to see what is blocking the shutdown if I have some spare time next week.

    Kind regards
    Benjamin


    Herbert S.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From luca.pedrielli@21:1/5 to All on Sat Oct 9 15:40:03 2021
    This is a multi-part message in MIME format.
    Il 09/10/21 12:17, Herbert ha scritto:
    Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user same behavior.
    Any idea about the reason ?

    Herbert S.


    Hi Herbert,

    have you tried to compare the logs of the last session(root and user)
    using journalctl -b -1?

    you can also enable a debug-shell with |systemctl enable debug-shell
    (turn it on only as needed and disable it afterwards) and use it on logout|

    ||

    |||https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early_debug_shell|

    ||

    |||I had a similar problem ago, solved by removing Kdeconnect, but I
    don't think it's your same problem.|

    --
    Saluti, Luca Pedrielli


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix">Il 09/10/21 12:17, Herbert ha scritto:<br>
    </div>
    <blockquote type="cite" cite="mid:1970823.4zafZJV9KR@debian">
    <pre class="moz-quote-pre" wrap="">Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal as under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user
    same behavior.
    Any idea about the reason ?

    Herbert S.


    </pre>
    </blockquote>
    <p>Hi Herbert,</p>
    <p><span class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
    data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="0"><span>have
    you tried to compare the logs of the last session(</span></span></span>root
    and user) using journalctl -b -1?</p>
    <p>you can also enable a debug-shell with <font size="+1"><code>systemctl
    enable debug-shell (turn it on only as needed and disable it
    afterwards) and use it on logout</code></font></p>
    <p><font size="+1"><code></code></font></p>
    <p><font size="+1"><code></code></font><code><a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early_debug_shell">https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early_debug_
    shell</a></code></p>
    <p><code></code></p>
    <p><code></code><font size="+1"><code><span class="VIiyi" lang="en"><span
    class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="0"><span>I
    had a similar problem ago, solved by removing
    Kdeconnect, but I don't think it's your same problem.</span></span></span></code></font></p>
    <pre class="moz-signature" cols="72">--
    Saluti, Luca Pedrielli </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Herbert Schwarzer@21:1/5 to All on Sat Oct 9 21:10:02 2021
    This is a multi-part message in MIME format.

    Thank you for your replies. I have tested before a lot around i.e. to check logfiles - but there comes a heavy load of messages.
    So the first step for THIS answer I wrote journalctl-output to 2 files (attached) but I am worried about the many lines although I have started
    output only just in time if I LOGGED OUT from KDE and stopped when I returned to new login-window.
    Maybe YOU can recognize something .
    BUT @ Luca Podrelli --> the solution for me too has been deinstalling kdeconnect. Don't know WHY this troubles the logout.

    Thank you - so the problem is solved.
    Can anyone of the Debian KDE people eliminate this conflict within a next Debian 11 update ...

    Saluti a Luca et

    Am Samstag, 9. Oktober 2021, 15:35:37 CEST schrieb luca.pedrielli:
    Il 09/10/21 12:17, Herbert ha scritto:
    Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal
    as
    under Buster logout passed immediately (login screen: sddm or lightdm, does not matter) appeared just in time. If I log in as root (only under lightdm possible) there is no delay in logging out. Even creating a fresh new user same behavior.
    Any idea about the reason ?

    Herbert S.

    Hi Herbert,

    have you tried to compare the logs of the last session(root and user)
    using journalctl -b -1?

    you can also enable a debug-shell with |systemctl enable debug-shell
    (turn it on only as needed and disable it afterwards) and use it on logout|

    |||https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early |||_debug_shell|
    |||
    |||
    |||
    |||I had a similar problem ago, solved by removing Kdeconnect, but I

    don't think it's your same problem.|


    -- Journal begins at Sun 2021-09-05 10:14:23 CEST. --
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:34: ReferenceError: model is not defined
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:34: ReferenceError: model is not defined
    Okt 09 20:15:17 debian org.kde.LogoutPrompt[2372]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:34: ReferenceError: model is not defined
    Okt 09 20:15:24 debian dbus-daemon[1182]: [session uid=1000 pid=1182] Activating service name='org.kde.Shutdown' requested by ':1.21' (uid=1000 pid=1332 comm="/usr/bin/ksmserver ")
    Okt 09 20:15:24 debian dbus-daemon[1182]: [session uid=1000 pid=1182] Successfully activated service 'org.kde.Shutdown'
    Okt 09 20:15:24 debian polkitd(authority=local)[601]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.54, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8)
    Okt 09 20:15:24 debian org.kde.krunner[2068]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/runcommand/RunCommand.qml:75: TypeError: Cannot read property 'canConfigure' of null
    Okt 09 20:15:24 debian org.kde.krunner[2068]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/runcommand/RunCommand.qml:195: TypeError: Cannot read property 'history' of null
    Okt 09 20:15:25 debian dbus-daemon[1182]: [session uid=1000 pid=1182] Activating service name='org.kde.kdeconnect' requested by ':1.26' (uid=1000 pid=1366 comm="/usr/bin/plasmashell ")
    Okt 09 20:15:25 debian dbus-daemon[1182]: [session uid=1000 pid=1182] Successfully activated service 'org.kde.kdeconnect'
    Okt 09 20:15:25 debian org.kde.kdeconnect[2425]: qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 374, resource id: 0, major code: 20 (GetProperty), minor code: 0
    Okt 09 20:15:25 debian org.kde.kdeconnect[2425]: kdeconnect.core: Could not query capabilities from notifications server
    Okt 09 20:15:35 debian org.kde.kdeconnect[2425]: ICE default IO error handler doing an exit(), pid = 2425, errno = 11
    Okt 09 20:15:35 debian lightdm[863]: pam_unix(lightdm:session): session closed for user herbert
    Okt 09 20:15:35 debian kglobalaccel5[1282]: The X11 connection broke (error 1). Did the X11 server die?
    Okt 09 20:15:35 debian systemd-logind[605]: Session 2 logged out. Waiting for processes to exit.
    Okt 09 20:15:35 debian org.kde.ActivityManager[1320]: The X11 connection broke (error 1). Did the X11 server die?
    Okt 09 20:15:35 debian systemd[1158]: plasma-kglobalaccel.service: Succeeded. Okt 09 20:15:36 debian lightdm[2473]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=117) by (uid=0)
    Okt 09 20:15:36 debian systemd[1]: Created slice User Slice of UID 117.
    Okt 09 20:15:36 debian systemd[1]: Starting User Runtime Directory /run/user/117...
    Okt 09 20:15:36 debian systemd-logind[605]: New session c2 of user lightdm.
    Okt 09 20:15:36 debian systemd[1]: Finished User Runtime Directory /run/user/117.
    Okt 09 20:15:36 debian systemd[1]: Starting User Manager for UID 117...
    Okt 09 20:15:36 debian systemd[2480]: pam_unix(systemd-user:session): session opened for user lightdm(uid=117) by (uid=0)
    Okt 09 20:15:36 debian systemd[2485]: gpgconf: Fehler bei Ausführung von `/usr/lib/gnupg/scdaemon': wahrscheinlich nicht installiert
    Okt 09 20:15:36 debian systemd-xdg-autostart-generator[2498]: Exec binary 'hp-systray' does not exist: No such file or directory
    Okt 09 20:15:36 debian systemd-xdg-autostart-generator[2498]: Not generating service for XDG autostart app-hplip\x2dsystray-autostart.service, error parsing Exec= line: No such file or directory
    Okt 09 20:15:36 debian systemd[2480]: Queued start job for default target Main User Target.
    Okt 09 20:15:36 debian systemd[2480]: Created slice User Application Slice.
    Okt 09 20:15:36 debian systemd[2480]: Reached target Paths.
    Okt 09 20:15:36 debian systemd[2480]: Reached target Timers.
    Okt 09 20:15:36 debian systemd[2480]: Starting D-Bus User Message Bus Socket. Okt 09 20:15:36 debian systemd[2480]: Listening on GnuPG network certificate management daemon.
    Okt 09 20:15:36 debian systemd[2480]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
    Okt 09 20:15:36 debian systemd[2480]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
    Okt 09 20:15:36 debian systemd[2480]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
    Okt 09 20:15:36 debian systemd[2480]: Listening on GnuPG cryptographic agent and passphrase cache.
    Okt 09 20:15:36 debian systemd[2480]: Listening on Multimedia System.
    Okt 09 20:15:36 debian systemd[2480]: Listening on debconf communication socket.
    Okt 09 20:15:36 debian systemd[2480]: Listening on Sound System.
    Okt 09 20:15:36 debian systemd[2480]: Listening on D-Bus User Message Bus Socket.
    Okt 09 20:15:36 debian systemd[2480]: Reached target Sockets.
    Okt 09 20:15:36 debian systemd[2480]: Reached target Basic System.
    Okt 09 20:15:36 debian systemd[1]: Started User Manager for UID 117.
    Okt 09 20:15:36 debian systemd[2480]: Started Multimedia Service.
    Okt 09 20:15:36 debian systemd[1]: Started Session c2 of user lightdm.
    Okt 09 20:15:36 debian systemd[2480]: Starting Sound Service...
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2500 of process 2500 owned by '117' high priority at nice level -11.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:15:36 debian systemd[2480]: Started D-Bus User Message Bus.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2502 of process 2500 owned by '117' RT at priority 20.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 8 threads of 4 processes of 2 users.
    Okt 09 20:15:36 debian pipewire[2500]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2501 of process 2501 owned by '117' high priority at nice level -11.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 9 threads of 5 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2505 of process 2505 owned by '117' high priority at nice level -11.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 10 threads of 6 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 10 threads of 6 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 10 threads of 6 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2506 of process 2505 owned by '117' RT at priority 20.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 11 threads of 6 processes of 2 users.
    Okt 09 20:15:36 debian systemd[1158]: pulseaudio.service: Succeeded.
    Okt 09 20:15:36 debian dbus-daemon[2503]: [session uid=117 pid=2503] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=117 pid=2504 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:15:36 debian systemd[2480]: Starting Accessibility services bus... Okt 09 20:15:36 debian dbus-daemon[2503]: [session uid=117 pid=2503] Successfully activated service 'org.a11y.Bus'
    Okt 09 20:15:36 debian systemd[2480]: Started Accessibility services bus.
    Okt 09 20:15:36 debian dbus-daemon[2503]: [session uid=117 pid=2503] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.6' (uid=117 pid=2504 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:15:36 debian systemd[2480]: Starting Virtual filesystem service... Okt 09 20:15:36 debian dbus-daemon[2503]: [session uid=117 pid=2503] Successfully activated service 'org.gtk.vfs.Daemon'
    Okt 09 20:15:36 debian systemd[2480]: Started Virtual filesystem service.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 9 threads of 5 processes of 2 users.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Successfully made thread 2551 of process 2501 owned by '117' RT at priority 5.
    Okt 09 20:15:36 debian rtkit-daemon[814]: Supervising 10 threads of 5 processes of 2 users.
    Okt 09 20:15:36 debian systemd[2480]: Started Sound Service.
    Okt 09 20:15:36 debian systemd[2480]: Reached target Main User Target.
    Okt 09 20:15:36 debian systemd[2480]: Startup finished in 477ms.
    Okt 09 20:15:36 debian at-spi-bus-launcher[2528]: dbus-daemon[2528]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=117 pid=2504 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:15:36 debian at-spi-bus-launcher[2528]: dbus-daemon[2528]: Successfully activated service 'org.a11y.atspi.Registry'
    Okt 09 20:15:36 debian at-spi-bus-launcher[2560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry

    -- Journal begins at Sun 2021-09-05 10:14:23 CEST. --
    Okt 09 20:16:54 debian systemd[1]: user@117.service: Succeeded.
    Okt 09 20:16:54 debian systemd[1]: Stopped User Manager for UID 117.
    Okt 09 20:16:54 debian systemd[1]: Stopping User Runtime Directory /run/user/117...
    Okt 09 20:16:54 debian systemd[2333]: run-user-117.mount: Succeeded.
    Okt 09 20:16:54 debian systemd[1]: run-user-117.mount: Succeeded.
    Okt 09 20:16:54 debian systemd[1158]: run-user-117.mount: Succeeded.
    Okt 09 20:16:54 debian systemd[1]: user-runtime-dir@117.service: Succeeded.
    Okt 09 20:16:54 debian systemd[1]: Stopped User Runtime Directory /run/user/117.
    Okt 09 20:16:54 debian systemd[1]: Removed slice User Slice of UID 117.
    Okt 09 20:16:54 debian systemd[1]: user-117.slice: Consumed 1.590s CPU time. Okt 09 20:16:58 debian dbus-daemon[2595]: [session uid=0 pid=2595] Activating service name='org.kde.Shutdown' requested by ':1.16' (uid=0 pid=2722 comm="/usr/bin/ksmserver ")
    Okt 09 20:16:58 debian dbus-daemon[2595]: [session uid=0 pid=2595] Successfully activated service 'org.kde.Shutdown'
    Okt 09 20:16:58 debian polkitd(authority=local)[601]: Unregistered Authentication Agent for unix-session:7 (system bus name :1.118, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8)
    Okt 09 20:16:58 debian systemd[2333]: app-\x2fusr\x2fbin\x2fkorgac-27731527da174a1296d96dffc2a86721.scope: Succeeded.
    Okt 09 20:16:58 debian dbus-daemon[2595]: [session uid=0 pid=2595] Activating service name='org.kde.kdeconnect' requested by ':1.18' (uid=0 pid=2732 comm="/usr/bin/plasmashell ")
    Okt 09 20:16:58 debian lightdm[2580]: pam_unix(lightdm:session): session closed for user root
    Okt 09 20:16:58 debian systemd-logind[605]: Session 7 logged out. Waiting for processes to exit.
    Okt 09 20:16:58 debian kglobalaccel5[2674]: The X11 connection broke (error 1). Did the X11 server die?
    Okt 09 20:16:58 debian org.kde.ActivityManager[2714]: The X11 connection broke (error 1). Did the X11 server die?
    Okt 09 20:16:58 debian systemd[2333]: plasma-kglobalaccel.service: Succeeded. Okt 09 20:16:59 debian lightdm[2968]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=117) by (uid=0)
    Okt 09 20:16:59 debian systemd[1]: Created slice User Slice of UID 117.
    Okt 09 20:16:59 debian systemd[1]: Starting User Runtime Directory /run/user/117...
    Okt 09 20:16:59 debian systemd-logind[605]: New session c3 of user lightdm.
    Okt 09 20:16:59 debian systemd[1]: Finished User Runtime Directory /run/user/117.
    Okt 09 20:16:59 debian systemd[1]: Starting User Manager for UID 117...
    Okt 09 20:16:59 debian systemd[2975]: pam_unix(systemd-user:session): session opened for user lightdm(uid=117) by (uid=0)
    Okt 09 20:16:59 debian systemd[2980]: gpgconf: Fehler bei Ausführung von `/usr/lib/gnupg/scdaemon': wahrscheinlich nicht installiert
    Okt 09 20:16:59 debian systemd-xdg-autostart-generator[2993]: Exec binary 'hp-systray' does not exist: No such file or directory
    Okt 09 20:16:59 debian systemd-xdg-autostart-generator[2993]: Not generating service for XDG autostart app-hplip\x2dsystray-autostart.service, error parsing Exec= line: No such file or directory
    Okt 09 20:16:59 debian systemd[2975]: Queued start job for default target Main User Target.
    Okt 09 20:16:59 debian systemd[2975]: Created slice User Application Slice.
    Okt 09 20:16:59 debian systemd[2975]: Reached target Paths.
    Okt 09 20:16:59 debian systemd[2975]: Reached target Timers.
    Okt 09 20:16:59 debian systemd[2975]: Starting D-Bus User Message Bus Socket. Okt 09 20:16:59 debian systemd[2975]: Listening on GnuPG network certificate management daemon.
    Okt 09 20:16:59 debian systemd[2975]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
    Okt 09 20:16:59 debian systemd[2975]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
    Okt 09 20:16:59 debian systemd[2975]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
    Okt 09 20:16:59 debian systemd[2975]: Listening on GnuPG cryptographic agent and passphrase cache.
    Okt 09 20:16:59 debian systemd[2975]: Listening on Multimedia System.
    Okt 09 20:16:59 debian systemd[2975]: Listening on debconf communication socket.
    Okt 09 20:16:59 debian systemd[2975]: Listening on Sound System.
    Okt 09 20:16:59 debian systemd[2975]: Listening on D-Bus User Message Bus Socket.
    Okt 09 20:16:59 debian systemd[2975]: Reached target Sockets.
    Okt 09 20:16:59 debian systemd[2975]: Reached target Basic System.
    Okt 09 20:16:59 debian systemd[1]: Started User Manager for UID 117.
    Okt 09 20:16:59 debian systemd[2975]: Started Multimedia Service.
    Okt 09 20:16:59 debian systemd[1]: Started Session c3 of user lightdm.
    Okt 09 20:16:59 debian systemd[2975]: Starting Sound Service...
    Okt 09 20:16:59 debian rtkit-daemon[814]: Successfully made thread 2995 of process 2995 owned by '117' high priority at nice level -11.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 5 threads of 3 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 5 threads of 3 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 5 threads of 3 processes of 2 users.
    Okt 09 20:16:59 debian systemd[2975]: Started D-Bus User Message Bus.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Successfully made thread 2997 of process 2995 owned by '117' RT at priority 20.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 6 threads of 3 processes of 2 users.
    Okt 09 20:16:59 debian pipewire[2995]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
    Okt 09 20:16:59 debian rtkit-daemon[814]: Successfully made thread 3000 of process 3000 owned by '117' high priority at nice level -11.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 7 threads of 4 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Successfully made thread 3001 of process 3000 owned by '117' RT at priority 20.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 8 threads of 4 processes of 2 users.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Successfully made thread 2996 of process 2996 owned by '117' high priority at nice level -11.
    Okt 09 20:16:59 debian rtkit-daemon[814]: Supervising 9 threads of 5 processes of 2 users.
    Okt 09 20:16:59 debian org.kde.kdeconnect[2939]: Qt: Session management error: Could not open network socket
    Okt 09 20:16:59 debian dbus-daemon[2595]: [session uid=0 pid=2595] Successfully activated service 'org.kde.kdeconnect'
    Okt 09 20:16:59 debian org.kde.kdeconnect[2939]: The X11 connection broke (error 1). Did the X11 server die?
    Okt 09 20:16:59 debian dbus-daemon[2595]: [session uid=0 pid=2595] Activating service name='org.freedesktop.Notifications' requested by ':1.41' (uid=0 pid=2939 comm="/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd ")
    Okt 09 20:16:59 debian dbus-daemon[2999]: [session uid=117 pid=2999] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=117 pid=2998 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:16:59 debian systemd[2975]: Starting Accessibility services bus... Okt 09 20:16:59 debian dbus-daemon[2999]: [session uid=117 pid=2999] Successfully activated service 'org.a11y.Bus'
    Okt 09 20:16:59 debian systemd[2975]: Started Accessibility services bus.
    Okt 09 20:16:59 debian dbus-daemon[2999]: [session uid=117 pid=2999] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.6' (uid=117 pid=2998 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:16:59 debian systemd[2975]: Starting Virtual filesystem service... Okt 09 20:16:59 debian dbus-daemon[2999]: [session uid=117 pid=2999] Successfully activated service 'org.gtk.vfs.Daemon'
    Okt 09 20:16:59 debian systemd[2975]: Started Virtual filesystem service.
    Okt 09 20:17:00 debian at-spi-bus-launcher[3028]: dbus-daemon[3028]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=117 pid=2998 comm="/usr/sbin/lightdm-gtk-greeter ")
    Okt 09 20:17:00 debian at-spi-bus-launcher[3028]: dbus-daemon[3028]: Successfully activated service 'org.a11y.atspi.Registry'
    Okt 09 20:17:00 debian at-spi-bus-launcher[3054]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    Okt 09 20:17:00 debian rtkit-daemon[814]: Supervising 9 threads of 5 processes of 2 users.
    Okt 09 20:17:00 debian rtkit-daemon[814]: Successfully made thread 3057 of process 2996 owned by '117' RT at priority 5.
    Okt 09 20:17:00 debian rtkit-daemon[814]: Supervising 10 threads of 5 processes of 2 users.
    Okt 09 20:17:00 debian systemd[2975]: Started Sound Service.
    Okt 09 20:17:00 debian systemd[2975]: Reached target Main User Target.
    Okt 09 20:17:00 debian systemd[2975]: Startup finished in 783ms.
    Okt 09 20:17:01 debian CRON[3063]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
    Okt 09 20:17:01 debian CRON[3064]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
    Okt 09 20:17:01 debian CRON[3063]: pam_unix(cron:session): session closed for user root

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From luca.pedrielli@21:1/5 to All on Sat Oct 9 22:10:02 2021
    This is a multi-part message in MIME format.
    Happy to help you.

    https://lists.debian.org/debian-kde/2021/02/msg00006.html


    Il 09/10/21 20:43, Herbert Schwarzer ha scritto:
    Thank you for your replies. I have tested before a lot around i.e. to check logfiles - but there comes a heavy load of messages.
    So the first step for THIS answer I wrote journalctl-output to 2 files (attached) but I am worried about the many lines although I have started output only just in time if I LOGGED OUT from KDE and stopped when I returned to new login-window.
    Maybe YOU can recognize something .
    BUT @ Luca Podrelli --> the solution for me too has been deinstalling kdeconnect. Don't know WHY this troubles the logout.

    Thank you - so the problem is solved.
    Can anyone of the Debian KDE people eliminate this conflict within a next Debian 11 update ...

    Saluti a Luca et

    Am Samstag, 9. Oktober 2021, 15:35:37 CEST schrieb luca.pedrielli:
    Il 09/10/21 12:17, Herbert ha scritto:
    Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal >>> as
    under Buster logout passed immediately (login screen: sddm or lightdm,
    does not matter) appeared just in time. If I log in as root (only under
    lightdm possible) there is no delay in logging out. Even creating a fresh >>> new user same behavior.
    Any idea about the reason ?

    Herbert S.
    Hi Herbert,

    have you tried to compare the logs of the last session(root and user)
    using journalctl -b -1?

    you can also enable a debug-shell with |systemctl enable debug-shell
    (turn it on only as needed and disable it afterwards) and use it on logout| >>
    |||https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early >> |||_debug_shell|
    |||
    |||
    |||
    |||I had a similar problem ago, solved by removing Kdeconnect, but I

    don't think it's your same problem.|


    --
    Saluti, Luca Pedrielli


    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
    class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="0"><span>Happy
    to help you</span></span></span>.<br>
    <br>
    <a class="moz-txt-link-freetext" href="https://lists.debian.org/debian-kde/2021/02/msg00006.html">https://lists.debian.org/debian-kde/2021/02/msg00006.html</a><br>
    <br>
    <br>
    Il 09/10/21 20:43, Herbert Schwarzer ha scritto:<br>
    </div>
    <blockquote type="cite" cite="mid:1947429.pAWOAqGyVj@debian">
    <pre class="moz-quote-pre" wrap="">Thank you for your replies. I have tested before a lot around i.e. to check
    logfiles - but there comes a heavy load of messages.
    So the first step for THIS answer I wrote journalctl-output to 2 files (attached) but I am worried about the many lines although I have started
    output only just in time if I LOGGED OUT from KDE and stopped when I returned to new login-window.
    Maybe YOU can recognize something .
    BUT @ Luca Podrelli --&gt; the solution for me too has been deinstalling kdeconnect. Don't know WHY this troubles the logout.

    Thank you - so the problem is solved.
    Can anyone of the Debian KDE people eliminate this conflict within a next Debian 11 update ...

    Saluti a Luca et

    Am Samstag, 9. Oktober 2021, 15:35:37 CEST schrieb luca.pedrielli:
    </pre>
    <blockquote type="cite">
    <pre class="moz-quote-pre" wrap="">Il 09/10/21 12:17, Herbert ha scritto:
    </pre>
    <blockquote type="cite">
    <pre class="moz-quote-pre" wrap="">Hello to all readers
    Logout from KDE (Plasma 5.20.5) lasts more then 10 sec. This is abnormal
    as
    under Buster logout passed immediately (login screen: sddm or lightdm,
    does not matter) appeared just in time. If I log in as root (only under
    lightdm possible) there is no delay in logging out. Even creating a fresh
    new user same behavior.
    Any idea about the reason ?

    Herbert S.
    </pre>
    </blockquote>
    <pre class="moz-quote-pre" wrap="">
    Hi Herbert,

    have you tried to compare the logs of the last session(root and user)
    using journalctl -b -1?

    you can also enable a debug-shell with |systemctl enable debug-shell
    (turn it on only as needed and disable it afterwards) and use it on logout|

    |||<a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early">https://fedoraproject.org/wiki/Systemd_early_debug-shell?rd=Systemd_early</a>
    |||_debug_shell|
    |||
    |||
    |||
    |||I had a similar problem ago, solved by removing Kdeconnect, but I

    don't think it's your same problem.|
    </pre>
    </blockquote>
    <pre class="moz-quote-pre" wrap="">
    </pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">--
    Saluti, Luca Pedrielli </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)