Bug#1142038: More informations on the bug

Hefee <[email protected]> Wed, 15 Jul 2026 13:17:24 +0200

Newsgroups	gmane.linux.debian.devel.qt-kde
Message-ID	<3053860.e9J7NaK4W3__20722.082937003$1784114387$gmane$org@tuxin>

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.

signature.asc (application/pgp-signature, 833 B)