You are not logged in.
I was afk for a week, and now I can't login to X, it just kicks me back to GDM. the few related posts I found had to do with flatpak which I dont have installed, /var/log/Xorg.0.log just shows an unable to connect to ACPI error.
There's no .xsession-errors log and no wayland.
Please let me know what logs I could post to troubleshoot this.
GDM log - https://paste.ubuntu.com/p/DR3X7hgp5Y/
Last edited by Strykar (2019-04-22 07:15:18)
Offline
I have also been experiencing this problem for 2 weeks now. There was another thread of people having a similar problem to me, except they seemingly fixed their problem by downgrading gtk3 (https://bbs.archlinux.org/viewtopic.php?id=245097)
Downgrading gtk3 has not solved this problem for me.
I have tried logging into gdm with the latest gtk3:
https://termbin.com/udjj
With gtk3 downgraded to 3.24.2+7+g43aeb52b72-1:
https://termbin.com/rk67
With gtk3 downgraded, and logging into Gnome on Xorg:
https://termbin.com/jpzf
I just get kicked back onto the GDM screen
Offline
Update your entire system, then disable your extensions. your extensions@abteil.org extension is crashing, you'll have to update it. https://wiki.archlinux.org/index.php/GN … _the_shell
@Stryker post more of your journal.
Online
@V1del - https://paste.ubuntu.com/p/Md3n7C6y2v/
Oddly, I see nothing under Gnome extensions -
$ ls -al ~/.local/share/gnome-shell/extensions/
total 8
drwxr-xr-x 2 strykar strykar 4096 Mar 31 02:40 .
drwx------ 3 strykar strykar 4096 Apr 1 00:30 ..
$ sudo ls -al /usr/share/gnome-shell/extensions/
total 8
drwxr-xr-x 2 root root 4096 Apr 1 11:34 .
drwxr-xr-x 6 root root 4096 Mar 21 00:42 ..
Last edited by Strykar (2019-04-01 06:13:42)
Offline
That log clearly shows an extension being problematic, but it also looks like it's quite dated (Feb 01). Post a complete untruncated
sudo journalctl -b > journal.txt #If you are being truncated by the pager
directly after reproducing the issue.
Online
But I've deleted all the extensions, and another thing I came across yesterday, other users cannot login via startx.
Here's today's log right after reproducing the issue - https://paste.ubuntu.com/p/ftTwhGCgCD/
Offline
@V1del If there's something in the log above, it's not clear to me.
Offline
Apr 02 14:43:04 i-5 /usr/lib/gdm-x-session[1298]: /etc/gdm/Xsession: Beginning session setup...
Apr 02 14:43:04 i-5 /usr/lib/gdm-x-session[1298]: Invalid MIT-MAGIC-COOKIE-1 keyxhost: unable to open display ":1"
Apr 02 14:43:04 i-5 /usr/lib/gdm-x-session[1298]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Apr 02 14:43:04 i-5 gnome-session[1304]: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Apr 02 14:43:04 i-5 gnome-session-c[1316]: cannot open display: :1
Apr 02 14:43:04 i-5 gnome-session[1304]: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Apr 02 14:43:04 i-5 gnome-session-c[1317]: cannot open display: :1
Apr 02 14:43:04 i-5 gnome-session[1304]: gnome-session-binary[1304]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 02 14:43:04 i-5 gnome-session-binary[1304]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 02 14:43:04 i-5 gnome-session[1304]: Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Apr 02 14:43:04 i-5 gnome-session-f[1318]: Cannot open display:
Offline
Thanks @loqs
I'd setup GDM as suggested by https://wiki.archlinux.org/index.php/Xi … X_at_login
$ xhost
access control enabled, only authorized clients can connect
$ cat .xinitrc
export GDK_BACKEND=x11
exec gnome-session
$ cat .xserverrc
#!/bin/sh
exec /usr/bin/Xorg -nolisten tcp "$@" vt$XDG_VTNR
$ echo $DISPLAY
:1
GDM config -
$ cat /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
$ cat /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
$ cat /usr/lib/systemd/system/gdm.service
[Unit]
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=
After=
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service
[Service]
ExecStart=/usr/bin/gdm
KillMode=mixed
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
StandardOutput=syslog
StandardError=inherit
EnvironmentFile=-/etc/locale.conf
ExecReload=/bin/kill -SIGHUP $MAINPID
KeyringMode=shared
[Install]
Alias=display-manager.service
$ cat /etc/locale.conf
LANG=en_US.UTF-8
I have tried deleting ~/.Xauthority
I have not set custom exports as suggested in other people's issues I looked up -
$ export -p
declare -x CLOUDSDK_PYTHON="python2"
declare -x CLOUDSDK_PYTHON_ARGS="-S"
declare -x CLOUDSDK_ROOT_DIR="/opt/google-cloud-sdk"
declare -x COLORTERM="truecolor"
declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
declare -x DISPLAY=":1"
declare -x GDK_BACKEND="x11"
declare -x GJS_DEBUG_OUTPUT="stderr"
declare -x GJS_DEBUG_TOPICS="JS ERROR;JS LOG"
declare -x GNOME_TERMINAL_SCREEN="/org/gnome/Terminal/screen/5a7d1f67_6762_4f91_90a7_955a68e70bc3"
declare -x GNOME_TERMINAL_SERVICE=":1.88"
declare -x GOOGLE_CLOUD_SDK_HOME="/opt/google-cloud-sdk"
declare -x HG="/usr/bin/hg"
declare -x HOME="/home/strykar"
declare -x INVOCATION_ID="fbdb6d6b401b415899c4041a40c1e770"
declare -x JOURNAL_STREAM="9:25251"
declare -x LANG="en_US.UTF-8"
declare -x LC_MEASUREMENT="en_US.UTF-8"
declare -x LC_MONETARY="en_US.UTF-8"
declare -x LC_NUMERIC="en_US.UTF-8"
declare -x LC_PAPER="en_US.UTF-8"
declare -x LC_TIME="en_US.UTF-8"
declare -x LOGNAME="strykar"
declare -x MAIL="/var/spool/mail/strykar"
declare -x MOZ_PLUGIN_PATH="/usr/lib/mozilla/plugins"
declare -x OLDPWD
declare -x PATH="/opt/google-cloud-sdk/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl"
declare -x PWD="/home/strykar"
declare -x SESSION_MANAGER="local/i-5:@/tmp/.ICE-unix/1270,unix/i-5:/tmp/.ICE-unix/1270"
declare -x SHELL="/bin/bash"
declare -x SHLVL="3"
declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"
declare -x TERM="xterm-256color"
declare -x USER="strykar"
declare -x VTE_VERSION="5600"
declare -x WINDOWPATH="2"
declare -x XAUTHORITY="/home/strykar/.Xauthority"
declare -x XDG_CURRENT_DESKTOP="GNOME"
declare -x XDG_MENU_PREFIX="gnome-"
declare -x XDG_RUNTIME_DIR="/run/user/1000"
declare -x XDG_SEAT="seat0"
declare -x XDG_SESSION_CLASS="user"
declare -x XDG_SESSION_ID="4"
declare -x XDG_SESSION_TYPE="tty"
declare -x XDG_VTNR="2"
This issue started after I remotely enabled xrdp and was afk for a week.
What am I missing here?
Offline
GDM is unrelated to xinitrc.
If you're using GDM (as :1 would suggest), try https://wiki.archlinux.org/index.php/GD … rg_backend
Online
@seth Thanks, uncommenting "WaylandEnable=True" changes the error to "No Protocol specified" but the issue persists -
Apr 06 22:30:53 i-5 /usr/lib/gdm-x-session[1195]: /etc/gdm/Xsession: Beginning session setup...
Apr 06 22:30:53 i-5 /usr/lib/gdm-x-session[1195]: No protocol specified
Apr 06 22:30:53 i-5 /usr/lib/gdm-x-session[1195]: xhost: unable to open display ":1"
Apr 06 22:30:53 i-5 /usr/lib/gdm-x-session[1195]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Apr 06 22:30:53 i-5 NetworkManager[420]: <info> [1554570053.2625] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 06 22:30:53 i-5 nm-dispatcher[1200]: req:2 'connectivity-change': new request (0 scripts)
Apr 06 22:30:53 i-5 nm-dispatcher[1200]: req:2 'connectivity-change': completed: no scripts
Apr 06 22:30:53 i-5 gnome-session[1206]: No protocol specified
Apr 06 22:30:53 i-5 gnome-session[1206]: Unable to init server: Could not connect: Connection refused
Apr 06 22:30:53 i-5 gnome-session-c[1218]: cannot open display: :1
Apr 06 22:30:53 i-5 gnome-session[1206]: No protocol specified
Apr 06 22:30:53 i-5 gnome-session[1206]: Unable to init server: Could not connect: Connection refused
Apr 06 22:30:53 i-5 gnome-session-c[1219]: cannot open display: :1
Apr 06 22:30:53 i-5 gnome-session[1206]: gnome-session-binary[1206]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 06 22:30:53 i-5 gnome-session-binary[1206]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 06 22:30:53 i-5 gnome-session[1206]: No protocol specified
Apr 06 22:30:53 i-5 gnome-session[1206]: Unable to init server: Could not connect: Connection refused
Apr 06 22:30:53 i-5 gnome-session-f[1220]: Cannot open display:
Logging to another console and startx still works with it uncommented.
Here's the whole log - https://paste.ubuntu.com/p/YgYspVBPsv/
Offline
Can you please upload that to some pastebin service that does not completely suck (seriously, light gray on somewhat lighter gray…) and/or require one to have a ubuntu account in order to download the text?
Online
Done, see - https://bpaste.net/show/28ccecca6ff9
Offline
Thanks.
The bad cookie is gone, but the conneciotn fails though the server starts (and terminates) fine.
Wild guess: Does it work if you disable the networkmanager & dnsmasq services?
Online
Isn't it weird that enabling "WaylandEnable=True" removes the bad cookie error?
I disabled NetworkManager and dnsmasq services, rebooted and tried logging in again, the issue persists.
I also tried disabling xrdp, no change.
Full log with services disabled - https://bpaste.net/show/8a5c26b0e3c5
Last edited by Strykar (2019-04-07 08:16:24)
Offline
Does the bad cookie re-show when you allow GDM to try wayland?
Can you start other sessions (eg. openbox) from GDM?
Online
No Cookie errors after commenting "WaylandEnable=True" -
$ grep Wayland /etc/gdm/custom.conf
#WaylandEnable=false
Apr 08 19:41:35 i-5 systemd[1191]: Started D-Bus User Message Bus.
Apr 08 19:41:35 i-5 /usr/lib/gdm-x-session[1205]: /etc/gdm/Xsession: Beginning session setup...
Apr 08 19:41:35 i-5 /usr/lib/gdm-x-session[1205]: No protocol specified
Apr 08 19:41:35 i-5 /usr/lib/gdm-x-session[1205]: xhost: unable to open display ":1"
Apr 08 19:41:35 i-5 /usr/lib/gdm-x-session[1205]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Apr 08 19:41:35 i-5 gnome-session[1212]: No protocol specified
Apr 08 19:41:35 i-5 gnome-session[1212]: Unable to init server: Could not connect: Connection refused
Apr 08 19:41:35 i-5 gnome-session-c[1224]: cannot open display: :1
Apr 08 19:41:35 i-5 gnome-session[1212]: No protocol specified
Apr 08 19:41:35 i-5 gnome-session[1212]: Unable to init server: Could not connect: Connection refused
Apr 08 19:41:35 i-5 gnome-session-c[1225]: cannot open display: :1
Apr 08 19:41:35 i-5 gnome-session[1212]: gnome-session-binary[1212]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 08 19:41:35 i-5 gnome-session-binary[1212]: WARNING: software acceleration check failed: Child process exited with code 1
Apr 08 19:41:35 i-5 gnome-session[1212]: No protocol specified
Apr 08 19:41:35 i-5 gnome-session[1212]: Unable to init server: Could not connect: Connection refused
Apr 08 19:41:35 i-5 gnome-session-f[1226]: Cannot open display:
The only options shown in GDM are "GNOME" and "GNOME Classic", should I install Openbox to test?
Last edited by Strykar (2019-04-08 14:24:26)
Offline
should I install Openbox to test?
I doubt there's another way to run it…
You can also try icewm or e16 if you like.
Online
Choosing Openbox doesn't work either -
Apr 08 20:03:18 i-5 systemd[1205]: Started D-Bus User Message Bus.
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: /etc/gdm/Xsession: Beginning session setup...
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: No protocol specified
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: xhost: unable to open display ":1"
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/openbox-session
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: No protocol specified
Apr 08 20:03:18 i-5 /usr/lib/gdm-x-session[1218]: Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Offline
Any ideas? I'm not even sure what the issue is, since it's not the cookie error..
Offline
Do you have 'xorg-xinit' installed?
Offline
@subwaypassenger Yes I do.
$ sudo pacman -Ss xorg-xinit
extra/xorg-xinit 1.4.1-1 [installed]
X.Org initialisation program
Offline
Any more ideas before I reinstall Arch?
Offline
Don't use GDM. It's apparently the cause.
Whether that's because of some local config or because of some GDM bug is everyones guess :-(
In any event it seems to fail to access the second X11 server (which however starts up)
Maybe it doesn't like the ~/.Xauthority permissions, you could try to attach "strace -f" to the GDM process before attempting to log in. *shrug*
Don't use GDM.
pacman -Qkk gdm libgdm
might reveal some deviation from the vanilla packages.
Online
Thanks, gonna try removing GDM and test LightDM instead.
$ sudo pacman -Qkk gdm libgdm
backup file: gdm: /etc/gdm/custom.conf (Modification time mismatch)
backup file: gdm: /etc/gdm/custom.conf (Size mismatch)
gdm: 499 total files, 0 altered files
libgdm: 23 total files, 0 altered files
Offline