Qt 5.9.1 Transition started

[ReinerS]

How do you start the xserver? with startx?

regards

Reiner

[zash1958]

Yes, I tried with startx after logging in to a terminal session

[devil]

What does apt policy sddm say? What is the output of apt -f install ?

[ReinerS]

When the session hangs, can you switch back to the console where you started with "startx"
Maybe some error messages there?

regards

Reiner

[dibl]

List all the files and folders in the user's home directory, and make sure none are owned by root.

[zash1958]

Also if I start the session as ROOT KDE fails......

[piper]

Do you use a custom  /.xsession ?

wayland ?

Should post the output of

Code Select Expand

journalctl -u sddm.service

Have you tried

Code Select Expand

dpkg-reconfigure sddm

Like to see this also

Code Select Expand

apt policy xserver-xorg-core

and

Code Select Expand

apt policy

Code Select Expand

lspci | grep VGA

won't hurt either

[unklarer]

piper, he can too

when

Code Select Expand

systemctl status sddm.service enabled is

try

Code Select Expand

systemctl set-default graphical.target

[zash1958]

journalctl -u sddm.service:

Code Select Expand


Aug 28 20:17:26 hugin systemd[1]: Starting Simple Desktop Display Manager...
Aug 28 20:17:26 hugin systemd[1]: Started Simple Desktop Display Manager.
Aug 28 20:17:27 hugin sddm[1500]: Auth: sddm-helper exited with 127
Aug 28 20:19:10 hugin sddm[1500]: Signal received: SIGTERM
Aug 28 20:19:10 hugin systemd[1]: Stopping Simple Desktop Display Manager...
Aug 28 20:19:10 hugin systemd[1]: Stopped Simple Desktop Display Manager.
Aug 28 20:19:10 hugin systemd[1]: Starting Simple Desktop Display Manager...
Aug 28 20:19:10 hugin systemd[1]: Started Simple Desktop Display Manager.
Aug 28 20:19:11 hugin sddm[8645]: Auth: sddm-helper exited with 127
Aug 28 20:20:47 hugin sddm[8645]: Signal received: SIGTERM
Aug 28 20:20:47 hugin systemd[1]: Stopping Simple Desktop Display Manager...
Aug 28 20:20:47 hugin systemd[1]: Stopped Simple Desktop Display Manager.
Aug 28 20:20:47 hugin systemd[1]: Starting Simple Desktop Display Manager...
Aug 28 20:20:47 hugin systemd[1]: Started Simple Desktop Display Manager.
Aug 28 20:20:48 hugin sddm[15329]: Auth: sddm-helper exited with 127
Aug 28 20:22:36 hugin sddm[15329]: Signal received: SIGTERM
Aug 28 20:22:36 hugin systemd[1]: Stopping Simple Desktop Display Manager...
Aug 28 20:22:36 hugin systemd[1]: Stopped Simple Desktop Display Manager.
[code]

Looks strange ... crashing sddm-helper ?????


[tommy2]

I experienced a similar problem a short while back where sddm was removed during an full-upgrade, ended up reinstalling it and everything was back to normal. Why sddm was removed I have no idea, I did not catch it in the upgrade information and ended up having to correct my mistake, maybe the same thing transpired??


t2

[devil]

Try to reinstall sddm

[zash1958]

OK, today evening I will reinstall sddm completely and give an answer - works or not ;-)

[samoht]

This morning fully dued - no suspicious package removed or installed.
Same behavior on my machine - no Plasma desktop.
Nvidia - KMS controlled.
Reinstalled sddm to no avail.
Same error message:

Code Select Expand

...
Auth: sddm-helper exited with ...

[piper]

unklarer

piper, he can too

when

Code Select Expand

systemctl status sddm.service enabled is

try

Code Select Expand

systemctl set-default graphical.target

Yes, thanks, that would have helped also

[zash1958]

No way,

system hangs - maybe in the state sddm is starting.

If I open a terminal session and the start the xserver via "startx" the backgroud of KDE appears but not the desktop itself. Maybe something more complicated is broken. And I think in this state sddm is no more used/needed?

Today I will make a test installation of a fresh system on a separate harddisk, run all updates and have a look if this works

There must be a bigger problem with KDE update itself. Maybe it happens only on some special environments.

I will report....