Can't log in with X11 on GNOME

Desktop Environments Gnome
1

Hello there! I’m using EndeavourOS with GNOME on my laptop, and I sometimes want to switch to X.Org to share my screen. I click on the little gear on the bottom right in the login screen and enter my password, but then it just kicks me back to the previous login screen. My hardware info and boot logs are:
https://clbin.com/pmkOj
https://clbin.com/BlZvZ

I checked the logs:

[norm@skotos ~]$ cat /home/norm/.local/share/xorg/Xorg.0.log
[    27.114] (--) Log file renamed from "/home/norm/.local/share/xorg/Xorg.pid-734.log" to "/home/norm/.local/share/xorg/Xorg.0.log"
[    27.115] 
X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
[    27.115] Current Operating System: Linux skotos 5.17.4-arch1-1 #1 SMP PREEMPT Wed, 20 Apr 2022 18:29:28 +0000 x86_64
[    27.115] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8e9cf6d7-72b5-4675-942a-007e6aad35a1 rw quiet loglevel=3 nowatchdog nvme_load=YES
[    27.115]  
[    27.115] Current version of pixman: 0.40.0
[    27.115] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    27.115] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    27.115] (==) Log file: "/home/norm/.local/share/xorg/Xorg.0.log", Time: Sun Apr 24 01:44:30 2022
[    27.115] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    27.115] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    27.115] Parse error on line 1 of section InputClass in file /etc/X11/xorg.conf.d/70-synaptics.conf
	"Identifier" is not a valid keyword in this section.
[    27.115] (EE) Problem parsing the config file
[    27.115] (EE) Error parsing the config file
[    27.115] (EE) 
Fatal server error:
[    27.115] (EE) no screens found(EE) 
[    27.115] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    27.115] (EE) Please also check the log file at "/home/norm/.local/share/xorg/Xorg.0.log" for additional information.
[    27.115] (EE) 
[    27.115] (EE) Server terminated with error (1). Closing log file.

and:

[norm@skotos ~]$ cat /home/norm/.local/share/xorg/Xorg.0.log.old
[    17.204] (--) Log file renamed from "/home/norm/.local/share/xorg/Xorg.pid-719.log" to "/home/norm/.local/share/xorg/Xorg.0.log"
[    17.205] 
X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
[    17.205] Current Operating System: Linux skotos 5.17.4-arch1-1 #1 SMP PREEMPT Wed, 20 Apr 2022 18:29:28 +0000 x86_64
[    17.205] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8e9cf6d7-72b5-4675-942a-007e6aad35a1 rw quiet loglevel=3 nowatchdog nvme_load=YES
[    17.205]  
[    17.205] Current version of pixman: 0.40.0
[    17.205] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    17.205] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    17.206] (==) Log file: "/home/norm/.local/share/xorg/Xorg.0.log", Time: Sun Apr 24 01:44:21 2022
[    17.206] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    17.206] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    17.207] Parse error on line 1 of section InputClass in file /etc/X11/xorg.conf.d/70-synaptics.conf
	"Identifier" is not a valid keyword in this section.
[    17.207] (EE) Problem parsing the config file
[    17.207] (EE) Error parsing the config file
[    17.207] (EE) 
Fatal server error:
[    17.207] (EE) no screens found(EE) 
[    17.207] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    17.207] (EE) Please also check the log file at "/home/norm/.local/share/xorg/Xorg.0.log" for additional information.
[    17.207] (EE) 
[    17.207] (EE) Server terminated with error (1). Closing log file.

And the file with the apparent parsing problem:

[norm@skotos ~]$ cat /etc/X11/xorg.conf.d/70-synaptics.conf
   Identifier "touchpad"
    Driver "synaptics"
    MatchIsTouchpad "on"
        Option "TapButton1" "1"
        Option "TapButton2" "3"
        Option "TapButton3" "2"
        Option "VertEdgeScroll" "on"
        Option "VertTwoFingerScroll" "on"
        Option "HorizEdgeScroll" "on"
        Option "HorizTwoFingerScroll" "on"
        Option "CircularScrolling" "on"
        Option "CircScrollTrigger" "2"
        Option "EmulateTwoFingerMinZ" "40"
        Option "EmulateTwoFingerMinW" "8"
        Option "CoastingSpeed" "0"
        Option "FingerLow" "30"
        Option "FingerHigh" "50"
        Option "MaxTapTime" "125"
        Option "VertScrollDelta" "1000"
EndSection

I notice the Identifier keyword has wonky indentation, so that might be the problem? I didn’t mess with it because I’m a newbie and didn’t want to break anything even more.

I also wanna note that on the surface, this problem is the same as one I found of a manjaro user here:

but I don’t think it’s for the same reason.

Thank you in advance for your help!

2

Maybe this would get more views in Gnome 42 Bugs

Oh, welcome to the :enos: forum @meme_value_theorem

1 Like
3

Don’t know but there is only one way to find out.

Don’t think it will break anything even more.

Welcome to EnOS’ forum @meme_value_theorem!

2 Likes
4

Welcome to the forum @meme_value_theorem :enos_flag: :enos: :partying_face:

1 Like
5

So I tried giving it one more space of indentation, as well as no indentation, both yielded the same problem and the same log message as before

Thank you for having me!

1 Like
6

libinput

" https://wiki.archlinux.org/title/Libinput "

7

Note there’s an EndSection, but no opening Section.

2 Likes
8

This is the symptom :wink: that breaks Xorg (@meme_value_theorem has to add a Section "InputClass" at the start of the file. Indentation does not matter.)

The real issue is how was this file created and which process/hook creates/edits it.

9

This fixed it, thanks a lot!

And you’re right, though I don’t know what caused it. And as far as I can see, no one else has had this problem : /

1 Like