• plasma slow logout due to kdeconnect

    From luca.pedrielli@21:1/5 to All on Mon Feb 8 09:30:01 2021
    This is a multi-part message in MIME format.
    In a fresh debian testing installation(full updated) i noticed an
    annoying delay of a few seconds in the plasma logout.
    Removing kdeconnect (strange that it can't be disabled) solved the problem.

    I found this in the logs when I logged out: -----------------------------------------------------------------------------------------------------------------------------
    feb 07 09:56:13 ilprof5 org.kde.kdeconnect[8388]: kdeconnect.core: Could
    not query capabilities from notifications server
    feb 07 09:56:23 ilprof5 org.kde.kdeconnect[8388]: ICE default IO error
    handler doing an exit(), pid = 8388, errno = 11
    feb 07 09:58:14 ilprof5 org.kde.kdeconnect[9385]: kdeconnect.core: Could
    not query capabilities from notifications server
    feb 07 09:58:24 ilprof5 org.kde.kdeconnect[9385]: ICE default IO error
    handler doing an exit(), pid = 9385, errno = 11
    feb 07 09:58:43 ilprof5 org.kde.kdeconnect[10333]: kdeconnect.core:
    Could not query capabilities from notifications server
    feb 07 09:58:53 ilprof5 org.kde.kdeconnect[10333]: ICE default IO error
    handler doing an exit(), pid = 10333, errno = 11 -----------------------------------------------------------------------------------------------------------------------------

    --
    Saluti, Luca Pedrielli


    <html>
    <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-15">
    </head>
    <body>
    <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>In
    a fresh debian testing installation(full updated) i noticed an
    annoying delay of a few seconds in the plasma logout.</span></span><span
    class="JLqJ4b" data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="1"><span>
    </span></span><span class="JLqJ4b ChMk0b"
    data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="2"><span><br>
    Removing kdeconnect (strange that it can't be disabled) solved
    the problem.<br>
    <br>
    </span></span></span><span class="VIiyi" lang="en"><span
    class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="4"><span>I
    found this in the logs when I logged out</span></span></span>:<br>
    <font face="monospace">-----------------------------------------------------------------------------------------------------------------------------<br>
    feb 07 09:56:13 ilprof5 org.kde.kdeconnect[8388]: kdeconnect.core:
    Could not query capabilities from notifications server<br>
    feb 07 09:56:23 ilprof5 org.kde.kdeconnect[8388]: ICE default IO
    error handler doing an exit(), pid = 8388, errno = 11<br>
    feb 07 09:58:14 ilprof5 org.kde.kdeconnect[9385]: kdeconnect.core:
    Could not query capabilities from notifications server<br>
    feb 07 09:58:24 ilprof5 org.kde.kdeconnect[9385]: ICE default IO
    error handler doing an exit(), pid = 9385, errno = 11<br>
    feb 07 09:58:43 ilprof5 org.kde.kdeconnect[10333]:
    kdeconnect.core: Could not query capabilities from notifications
    server<br>
    feb 07 09:58:53 ilprof5 org.kde.kdeconnect[10333]: ICE default IO
    error handler doing an exit(), pid = 10333, errno = 11<br>
    </font><font face="monospace">-----------------------------------------------------------------------------------------------------------------------------</font><br>
    <span class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
    data-language-for-alternatives="en"
    data-language-to-translate-into="it" data-phrase-index="2"><span></span></span></span>
    <pre class="moz-signature" cols="72">--
    Saluti, Luca Pedrielli </pre>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Malvin Gattinger@21:1/5 to All on Mon Jun 27 17:30:01 2022
    Hello Debian KDE team,

    As previously discussed on this mailing list, in Bullseye the
    logout from Plasma is delayed by around 10 seconds as long as KDE
    connect is installed:

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

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

    One workaround is to remove KDE connect, but I would like to keep
    using it in Debian bullseye. Also, as far as I know kdeconnect is
    installed by default when selecting KDE in the Debian installer.

    According to the following the bug is actually in ksmserver (in
    package plasma-workspace) and it has been fixed in version 5.24: https://bugs.kde.org/show_bug.cgi?id=432643

    Is there any chance to backport this fix to 5.20 and into Debian
    bullseye?

    Could/should I submit this as a Debian bug? Would this then be
    against the ksmserver or the kdeconnect package?

    thank you for your time and best wishes,
    Malvin

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