[SOLVED] MATE autologin - logging into empty black screen

buzzwallard · 2021-05-31 03:03:18

I have configured autologin following https://wiki.archlinux.org/title/LightDM

grep -v '#' lightdm.conf

[LightDM]
run-directory=/run/lightdm
[Seat:*]
session-wrapper=/etc/lightdm/Xsession
[LightDM]
run-directory=/run/lightdm
[Seat:*]
session-wrapper=/etc/lightdm/Xsession
autologin-user=buzz
autologin-session=/usr/share/xsessions/mate.desktop
autologin-user-timeout=0
`
[XDMCPServer]
[VNCServer]

From /var/log/lightdm/lightdm.log

DEBUG: Seat seat0: Failed to find session configuration /usr/share/xsessions/mate.desktop

But

# ls -l /usr/share/xsessions/mate.desktop
-rw-r--r-- 1 root root 8.4K 2021-05-07 00:09 /usr/share/xsessions/mate.desktop

Last edited by buzzwallard (2021-06-02 14:13:22)

seth · 2021-05-31 06:12:56

Do you meet

The linked wiki wrote:

You must be part of the autologin group to be able to login automatically without entering your password:

buzzwallard · 2021-06-02 01:15:04

seth wrote:

Do you meet
The linked wiki wrote:
You must be part of the autologin group to be able to login automatically without entering your password:

groups buzz
wheel users autologin nopasswdlogin buzz

ewaller · 2021-06-02 01:37:09

buzzwallard: If you were wondering what happened to your first post, you hit report instead of reply

Last edited by ewaller (2021-06-02 01:37:29)

holiday · 2021-06-02 04:58:59

ewaller wrote:

buzzwallard: If you were wondering what happened to your first post, you hit report instead of reply

Thanks. Sorry.

Bet I do that again though.

seth · 2021-06-02 07:22:21

https://wiki.archlinux.org/title/LightD … TTY_output
Otherwise please post the complete lightdm and xorg logs

buzzwallard · 2021-06-02 08:45:57

Ah thank you.
The dialog appears after I manually start lightdm. So would that be the greeter?

seth · 2021-06-02 13:25:23

Manually starting lightdm will still attempt to auto-login your user.
Please test a different session, post the lightdm log and link a screenshot so everyone and myself has a visual idea what you're talking about.

Last edited by seth (2021-06-02 13:25:33)

buzzwallard · 2021-06-02 14:12:22

seth wrote:

Manually starting lightdm will still attempt to auto-login your user.

Yes. I get that.

seth wrote:

Please test a different session, post the lightdm log and link a screenshot so everyone and myself has a visual idea what you're talking about.

There is nothing but happy news in the lightdm log and in the journalctl output.

The crucial piece we're missing is -- NVIDIA.

I had enabled 'Force Composition Pipeline" through nvidia-settings and then merged the config with the existing config. This put

Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"

into /etc/X11/xorg.conf

All was well until I rebooted -- or restarted lightdm.

Once I removed that line and restarted, I was back to working.

Thanks very much for your work on this site, Seth. I see you here a lot helping out. I am grateful for that.

seth · 2021-06-02 14:16:33

That sounds weird - did you invalidate the xorg config?
Or just no HDMI-0?
Do you still have or can you recreate the "bad" file?

Sidenote: you should™ not be using a static server config anyway. Certainly not the cruft that nvidia-xconfg/settings generates.

buzzwallard · 2021-06-02 14:47:09

seth wrote:

That sounds weird - did you invalidate the xorg config?,[
Do you still have or can you recreate the "bad" file?

Maybe? I'll regenerate it now. Hang on.

cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 390.143 (dvs-builder@U64-P10-14) Fri Mar 12 07:19:34 UTC 2021
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 390.143 (dvs-builder@U64-P10-14) Fri Mar 12 07:18:28 UTC 2021
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "DELL U2419H"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 560M"
EndSection
Section "Screen"
# Removed Option "metamodes" "HDMI-0: nvidia-auto-select +0+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth 24
EndSubSection
EndSection

seth wrote:

Or just no HDMI-0?

Both displays are affected.

seth wrote:

Sidenote: you should™ not be using a static server config anyway. Certainly not the cruft that nvidia-xconfg/settings generates.

Lesson learned! But why? How to regenerate the original?

seth · 2021-06-02 15:01:41

There's nothign relevant in that config - kbd and mouse drivers are dead anyway and will just cause errors in the xorg log.
The server layout is boring and will be autodetected.
The only thing non-standard is "Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"" which you could augment eg.
/etc/X11/xorg-conf.d/20-nvidia.conf

Section "Device"
    Identifier "Default nvidia Device"
    Driver	"nvidia"
    # Option       "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}
    Option       "ForceCompositionPipeline" "true" # try this instead
EndSection

I suspect that just

Option         "metamodes" "HDMI-0: nvidia-auto-select +0+0"

will get you the misbehavior?

buzzwallard · 2021-06-02 15:20:33

seth wrote:

The only thing non-standard is "Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"" which you could augment eg.
/etc/X11/xorg-conf.d/20-nvidia.conf

This broke it really bad. I didn't even see the password dialog

Adding

Option "metamodes" "HDMI-0: nvidia-auto-select +0+0"

does not cause a problem

seth · 2021-06-02 16:23:00

So it doesn't like the composition pipeline?
=> xorg log from such failure run?

buzzwallard · 2021-06-02 20:30:57

xorg.log

https://pastebin.com/1z3qyVrX

seth · 2021-06-02 20:34:53

That's the running server which "only" has (the functional)
[ 13.358] (**) NVIDIA(0): Option "MetaModes" "HDMI-0: nvidia-auto-select +0+0"

You probably need /var/log/Xorg.0.log.old?

buzzwallard · 2021-06-02 20:43:37

Ah !

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 15.316] Build Operating System: Linux Archlinux
[ 15.316] Current Operating System: Linux asgl 5.10.41-1-lts #1 SMP Fri, 28 May 2021 15:03:28 +0000 x86_64
[ 15.316] Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux-lts.img root=PARTUUID=9e3f593e-405c-fc42-a5d1-6be5608380ed rw
[ 15.316] Build Date: 13 April 2021 03:12:10PM
[ 15.316]
[ 15.316] Current version of pixman: 0.40.0
[ 15.316] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 15.316] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15.317] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 2 08:12:48 2021
[ 15.317] (==) Using config file: "/etc/X11/xorg.conf"
[ 15.317] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 15.317] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 15.317] Parse error on line 1 of section OutputClass in file /etc/X11/xorg.conf.d/20-nvidia.conf
"Option" is not a valid keyword in this section.
[ 15.317] (EE) Problem parsing the config file
[ 15.317] (EE) Error parsing the config file
[ 15.317] (EE)
Fatal server error:
[ 15.317] (EE) no screens found(EE)
[ 15.317] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 15.317] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 15.317] (EE)
[ 15.317] (EE) Server terminated with error (1). Closing log file.

seth · 2021-06-02 20:58:45

[ 15.317] Parse error on line 1 of section OutputClass in file /etc/X11/xorg.conf.d/20-nvidia.conf
"Option" is not a valid keyword in this section.

Who said something about OutputClass?
https://www.youtube.com/watch?v=T_x6QmuJdms

buzzwallard · 2021-06-02 22:27:01

Beats me, all I have is this:

[seth wrote:
The only thing non-standard is "Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"" which you could augment eg.
/etc/X11/xorg-conf.d/20-nvidia.conf

So being a good little fixer I added /etc/X11/xorg.conf.d/20-nvidia.conf

# cat /etc/X11/xorg.conf.d/20-nvidia.conf
"Option "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}"

Last edited by buzzwallard (2021-06-02 22:29:47)

seth · 2021-06-03 05:24:55

Yeah, but you can't just add it "somewhere", it has to be a proper section - try

Section "Device" # section header. mandatory. always.
    Identifier "Default nvidia Device" # section id - string doesn't matter but mandatory. always.
    Driver	"nvidia"  # match so we apply to the proper driver
    Option       "ForceCompositionPipeline" "true" # the option you want to set
EndSection # section footer. mandatory. always.

You'll notice that this is the file I suggested previously - only the comments changed

buzzwallard · 2021-06-03 12:16:33

Hey! That worked! And thanks for the comments to the file elements.

I was not suspecting you of giving bad information, Seth. Let that be clear.

This is the newb section after all. I know my place.

Last edited by buzzwallard (2021-06-03 12:17:03)

Arch Linux

#1 2021-05-31 03:03:18

[SOLVED] MATE autologin - logging into empty black screen

#2 2021-05-31 06:12:56

Re: [SOLVED] MATE autologin - logging into empty black screen

#3 2021-06-02 01:15:04

Re: [SOLVED] MATE autologin - logging into empty black screen

#4 2021-06-02 01:37:09

Re: [SOLVED] MATE autologin - logging into empty black screen

#5 2021-06-02 04:58:59

Re: [SOLVED] MATE autologin - logging into empty black screen

#6 2021-06-02 07:22:21

Re: [SOLVED] MATE autologin - logging into empty black screen

#7 2021-06-02 08:45:57

Re: [SOLVED] MATE autologin - logging into empty black screen

#8 2021-06-02 13:25:23

Re: [SOLVED] MATE autologin - logging into empty black screen

#9 2021-06-02 14:12:22

Re: [SOLVED] MATE autologin - logging into empty black screen

#10 2021-06-02 14:16:33

Re: [SOLVED] MATE autologin - logging into empty black screen

#11 2021-06-02 14:47:09

Re: [SOLVED] MATE autologin - logging into empty black screen

#12 2021-06-02 15:01:41

Re: [SOLVED] MATE autologin - logging into empty black screen

#13 2021-06-02 15:20:33

Re: [SOLVED] MATE autologin - logging into empty black screen

#14 2021-06-02 16:23:00

Re: [SOLVED] MATE autologin - logging into empty black screen

#15 2021-06-02 20:30:57

Re: [SOLVED] MATE autologin - logging into empty black screen

#16 2021-06-02 20:34:53

Re: [SOLVED] MATE autologin - logging into empty black screen

#17 2021-06-02 20:43:37

Re: [SOLVED] MATE autologin - logging into empty black screen

#18 2021-06-02 20:58:45

Re: [SOLVED] MATE autologin - logging into empty black screen

#19 2021-06-02 22:27:01

Re: [SOLVED] MATE autologin - logging into empty black screen

#20 2021-06-03 05:24:55

Re: [SOLVED] MATE autologin - logging into empty black screen

#21 2021-06-03 12:16:33

Re: [SOLVED] MATE autologin - logging into empty black screen

Board footer