Plasma 5 hanging on login after entering password

L1ghtmareI · 2016-12-20 19:43:47

Hi.

Just today this issue appeared seemingly out of the blue. The screen stops updating after pressing the login button or enter, after entering another terminal and going back to first theres black screen with only cursor.

I hadn't updated the system since the last successful reboot, the only change i remember is adding a script to xinitrc. In an attempt to fix the problem i checked the logs (x, pacman, system), not finding any new errors, updated with 'yaourt -Syua' and commented out the script in xinitrc, to no avail.

The succesful boot log from the first sddm line to the first plasma line

The failed boot log from the first sddm line till the last booting line

xinitrc:

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)



if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice

nvidia-settings --load-config-only
# /etc/X11/xinit/xinitrc.d/steam_autoaway.sh

Thanks in advance.

L1ghtmareI · 2016-12-20 22:45:11

Just to clarify, the issue seems to be with plasma specifically since the characteristic trait in logs is abscence of plasma messages (i cut them off in the first one). Other than that, i'm able to switch between ttys normally, but 1st seems to be completely dysfunctional (i tried to power off using alt+f2).

seth · 2016-12-21 08:19:06

You added "nvidia-settings --load-config-only"?
Assuming the file is actually sourced by the KDE start: tried to suspend the compositor (SHIFT+Alt+F12) after facing the black login?
There're also multiple reports about latest sddm being the problem (black)

And since you're on nvidia, ensure to not run an unsupported fb console ("dmesg | grep -i nvrm")

L1ghtmareI · 2016-12-21 09:28:24

I added the line so nvidia settings from a config file would get applied at login.
Shift+alt+f12 didn't work.
'dmesg | grep -i nvrm' returns only the well-known message about unsupported VGA console drivers that has been there forever.

I've found the issue on github too, strange that it's only surfaced now when the version has been released more than 3 months ago. Oddly enough, i haven't /var/log/sddm.log and 'find / sddm' didn't return anything for me.

seth · 2016-12-21 13:49:47

I added the line so nvidia settings from a config file would get applied at login.

...and did that maybe trigger the problem?

Shift+alt+f12 didn't work.

So it's not the GL context, but the framebuffer.

only the well-known message about unsupported VGA console drivers that has been there forever.

It may have been there forever and it may be well known, but it is certainly not "just". It states that you're running an unsupported setup which might cause framebuffer errors....

Try to get sdm out of the line (use startx or similar) to isolate or at least mitigate (in case it triggers issues handing on the framebuffer) the problem, but you should also get rid of the framebuffer console.

L1ghtmareI · 2016-12-21 15:45:14

No, the nvidia-settings line has been here forever as well and the settings themselves aren't anything critical.
Getting SDDM out of the way indeed didn't solve the problem.
Latest Xorg.0.log

That's the topic i went by when i first encountered the warning. Basically it says that nvidia with vesafb is not reliable, however removing vga from parameters entirely is inconvenient and it didn't cause anything but the warning, so i decided to leave it as was. I don't really understand what a framebuffer is and what it does though.

My kernel options are

nvidia-drm.modeset=1 rootfstype=xfs rootflags=rw,relatime,attr2,inode64,noquota quiet rw

Last edited by L1ghtmareI (2016-12-21 15:46:20)

L1ghtmareI · 2016-12-23 18:16:45

so these are the lines indicating the issue:

[    44.697] (**) Option "fd" "28"
[    44.697] (**) Option "fd" "31"
[    44.698] (**) Option "fd" "32"
[    44.698] (**) Option "fd" "33"
[    44.698] (**) Option "fd" "34"
[    44.698] (**) Option "fd" "35"
[    44.698] (**) Option "fd" "36"
[    44.698] (**) Option "fd" "37"
[    44.698] (**) Option "fd" "34"
[    44.699] (**) Option "fd" "36"
[    44.780] (II) systemd-logind: got pause for 13:67
[    44.780] (II) systemd-logind: got pause for 13:69
[    44.780] (II) systemd-logind: got pause for 13:65
[    44.780] (II) systemd-logind: got pause for 13:64
[    44.780] (II) systemd-logind: got pause for 13:68
[    44.780] (II) systemd-logind: got pause for 13:70
[    44.780] (II) systemd-logind: got pause for 13:66
[    44.780] (II) systemd-logind: got pause for 13:71

and according to this, this is caused by logind death.

I am currently trying various measures xorg/nvidia side but none of them have worked so far.

Just FYI i have nvidia KMS enabled.

edit: by now i have tried imo all relevant nvidia/xorg/framebuffer related workarounds, none have worked, moving onto logind

edit2: im not so sure anymore about logind, since it is still running when i have switched to another tty and the logind pause messages seem to appear simultaneously with the removal of xorg session i.e. xorg dies/pauses on vt switch which is not the original problem.

Last edited by L1ghtmareI (2016-12-23 19:19:31)

Arch Linux

#1 2016-12-20 19:43:47

Plasma 5 hanging on login after entering password

#2 2016-12-20 22:45:11

Re: Plasma 5 hanging on login after entering password

#3 2016-12-21 08:19:06

Re: Plasma 5 hanging on login after entering password

#4 2016-12-21 09:28:24

Re: Plasma 5 hanging on login after entering password

#5 2016-12-21 13:49:47

Re: Plasma 5 hanging on login after entering password

#6 2016-12-21 15:45:14

Re: Plasma 5 hanging on login after entering password

#7 2016-12-23 18:16:45

Re: Plasma 5 hanging on login after entering password

Board footer