Bug#1142038: More informations on the bug

Hello,

You are right, the socket stays alive during the whole session, but as 
soon as I close it (corresponds to the state "lc-logged-out-early.txt"),
the socket disappears (no longer present in as /tmp/sddm-:0-ffVDPB)
Also, sudo systemctl restart sddm.service does work and make SDDM usable 
again.
I am using systemd and loginctl

About this:

> some thing is still
> dangling around.
I created a new account "readertest" from which I did ps -edalf after 
having logged out from my account that we will call "myaccount". No 
processes are left on average. However if I launch a big quantity of 
stuff, there will still be processes listed by ps -edalf dangling around 
and the session will still be shown as open in loginctl (whatever time I 
wait)

However, about this:
> Maybe LXQT does not finish its session fast enough and some thing is still
> dangling around.
Your hypothesis seems like it's exactly what happens.
Using the same "readertest" account I ran loginctl at few key moments
- When the system started "lc-startup.txt"
- When I logged in "lc-logged.txt"
- Quickly after logging out "lc-logged-out-early(/2/3).txt" (did run it 
many times just to capture the advance of the log out process)
- Another time after logging out, but later (around 10 seconds 
later) "lc-logged-out-early4.txt"

As you can see, even though sddm started back agai    n my session is 
still running, for a long time. But even if my session is still running, 
the socket disappeared.

Unfortunately, I don't know any version of sddm when it worked before.

Regards.
> Hey,
>
> from the logs the problem is that the greeter cannot connect to the socket.
> " Socket error:  "QLocalSocket::connectToServer: Invalid name"
> Cannot connect to the daemon - is it running?"
>
> You can see the socketname in the logs /tmp/sddm-:0-ffVDPB
> Tht is the same as in the normal-sddm.log - so it seems like this socket stays
> alave while you are logged in. Is this the case?
> Does restart sddm service helps? (as root: systemctl restart sddm.service)
> Maybe LXQT does not finish its session fast enough and some thing is still
> dangling around.  ( search for processes that are created by you user)
> Do you know that a previous version of sddm that worked?
> Do you use systemd and loginctl?
>
> Regards,
>
> hefee
>
> --
>
> On Dienstag, 14. Juli 2026 09:55 Anonymous wrote:
>> Under normal circumstances, when sddm starts up properly, I get in
>> journalctl the log linked as "normal-sddm.txt"
>>
>> After logging out, I get in journalctl (only for sddm) the log contained
>> in "broken-sddm.txt"
>>
>> I am also the log of sddm in jounalctl directly after starting to login
>> in the file "login-sddm.txt"
>>
>> For this last log file I decided to include not only lines containing
>> sddm, but rather all the lines in the journal until the full session opened.

SESSION  UID USER       SEAT  LEADER CLASS   TTY  IDLE SINCE
      3 1001 readertest seat0 1004   user    tty3 no   -
      4 1001 readertest -     1291   manager -    no   -
      5 1000 myaccount     seat0 1409   user    tty2 no   -
      6 1000 myaccount     -     1442   manager -    no   -

4 sessions listed.

SESSION  UID USER       SEAT  LEADER CLASS         TTY  IDLE SINCE
      3 1001 readertest seat0 1004   user          tty3 no   -
      4 1001 readertest -     1291   manager       -    no   -
      6 1000 myaccount     -     1442   manager       -    no   -
      8  983 sddm       -     2040   manager-early -    no   -

4 sessions listed.

SESSION  UID USER       SEAT  LEADER CLASS         TTY  IDLE SINCE
      3 1001 readertest seat0 1004   user          tty3 no   -
      4 1001 readertest -     1291   manager       -    no   -
      6 1000 myaccount     -     1442   manager       -    no   -
      8  983 sddm       -     2040   manager-early -    no   -

4 sessions listed.

SESSION  UID USER       SEAT  LEADER CLASS         TTY  IDLE SINCE
      3 1001 readertest seat0 1004   user          tty3 no   -
      4 1001 readertest -     1291   manager       -    no   -
      6 1000 myaccount     -     1442   manager       -    no   -
      8  983 sddm       -     2040   manager-early -    no   -

4 sessions listed.

SESSION  UID USER       SEAT  LEADER CLASS   TTY  IDLE SINCE
      3 1001 readertest seat0 1004   user    tty3 no   -
      4 1001 readertest -     1291   manager -    no   -

2 sessions listed.

SESSION  UID USER       SEAT  LEADER CLASS         TTY  IDLE SINCE
      1  983 sddm       seat0 867    greeter       tty2 no   -
      2  983 sddm       -     890    manager-early -    no   -
      3 1001 readertest seat0 1004   user          tty3 no   -
      4 1001 readertest -     1291   manager       -    no   -

4 sessions listed.