Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53147 - Stuck in login loop with standard GNOME Wayland session after upgrading GDM

Attached to Project: Arch Linux
Opened by Deactivated account (TechnicalTotoro) - Thursday, 02 March 2017, 18:19 GMT
Last edited by Jan de Groot (JGC) - Sunday, 05 March 2017, 06:22 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

After doing a `sudo pacman -Syu` just now and upgrading the following packages:

- libgdm (3.22.1-1 -> 3.22.2-1)
- gdm (3.22.1-1 -> 3.22.2-1)
- vala (0.34.4-1 -> 0.34.5-1)

I have found that when I try to log in, even though I have done a restart twice already, I just enter into a login loop where if I get the password correct login screen disappears at the moment leaving only that gray background, and then in a few seconds when normally my desktop would it appear, I just get brought back to the login screen. So I am unable to log into GNOME, however if I select GNOME Classic from the list for some reason all works fine. My system runs Wayland 1.13.0-1 so I haven't tested the Xorg option to see how it behaves because I don't have that installed. All was working fine before the upgrade of GDM.

This is really annoying as I am unable to get into the nice DE session I like.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 05 March 2017, 06:22 GMT
Reason for closing:  Fixed
Comment by Jörg Krause (jkrause) - Friday, 03 March 2017, 06:22 GMT
I have the same problem. "GNOME on Xorg" still works. The followin packages were updated since the last successful Wayland login:

[2017-03-02 22:12] [ALPM] upgraded libgdm (3.22.1-1 -> 3.22.2-1)
[2017-03-02 22:12] [ALPM] upgraded gdm (3.22.1-1 -> 3.22.2-1)
[2017-03-02 22:12] [ALPM] upgraded graphene (1.4.0-1 -> 1.6.0-1)
[2017-03-02 22:12] [ALPM] upgraded nodejs (7.6.0-1 -> 7.7.1-1)
[2017-03-02 22:12] [ALPM] upgraded python2-sphinx-alabaster-theme (0.7.9-2 -> 0.7.10-1)
[2017-03-02 22:12] [ALPM] upgraded python2-sphinx_rtd_theme (0.1.9-3 -> 0.2.0-1)
[2017-03-02 22:12] [ALPM] upgraded screen (4.5.1-1 -> 4.5.1-2
Comment by Jörg Krause (jkrause) - Friday, 03 March 2017, 08:16 GMT
I have the same problem. "GNOME on Xorg" still works. The followin packages were updated since the last successful Wayland login:

[2017-03-02 22:12] [ALPM] upgraded libgdm (3.22.1-1 -> 3.22.2-1)
[2017-03-02 22:12] [ALPM] upgraded gdm (3.22.1-1 -> 3.22.2-1)
[2017-03-02 22:12] [ALPM] upgraded graphene (1.4.0-1 -> 1.6.0-1)
[2017-03-02 22:12] [ALPM] upgraded nodejs (7.6.0-1 -> 7.7.1-1)
[2017-03-02 22:12] [ALPM] upgraded python2-sphinx-alabaster-theme (0.7.9-2 -> 0.7.10-1)
[2017-03-02 22:12] [ALPM] upgraded python2-sphinx_rtd_theme (0.1.9-3 -> 0.2.0-1)
[2017-03-02 22:12] [ALPM] upgraded screen (4.5.1-1 -> 4.5.1-2
Comment by PF (greyeye) - Friday, 03 March 2017, 11:14 GMT
Same thing here, stuck in the login loop. The following packages were updated since the last successful Wayland login:

[2017-03-03 10:31] [ALPM] upgraded libgdm (3.22.1-1 -> 3.22.2-1)
[2017-03-03 10:31] [ALPM] upgraded libepoxy (1.4.0-1 -> 1.4.1-1)
[2017-03-03 10:31] [ALPM] upgraded gdm (3.22.1-1 -> 3.22.2-1)
[2017-03-03 10:31] [ALPM] upgraded graphene (1.4.0-1 -> 1.6.0-1)
[2017-03-03 10:31] [ALPM] upgraded lib32-libx11 (1.6.4-1 -> 1.6.5-1)
[2017-03-03 10:31] [ALPM] upgraded zeitgeist (1.0-1 -> 1.0+1+g1bcc8585-1)

I downgraded both libgdm and gdm back to version 3.22.1-1 and it does not loop anymore.
Comment by Luca Monti (Mons1990) - Friday, 03 March 2017, 11:28 GMT
Confirm this bug. Downgrading gdm and libgdm it works flawlessly.
Comment by Erick Will (erickwill) - Friday, 03 March 2017, 12:19 GMT
Same bug here. Any workaround besides downgrading?
Comment by James Valenzuela (Ogashi) - Friday, 03 March 2017, 14:57 GMT
Same happening here. Packages updated:
[2017-03-02 19:39] [ALPM] upgraded bluez (5.43-2 -> 5.44-1)
[2017-03-02 19:39] [ALPM] upgraded bluez-libs (5.43-2 -> 5.44-1)
[2017-03-02 19:39] [ALPM] upgraded kmod (23-1 -> 24-1)
[2017-03-02 19:39] [ALPM] upgraded harfbuzz (1.4.2-1 -> 1.4.3-1)
[2017-03-02 19:39] [ALPM] upgraded libwacom (0.22-1 -> 0.24-1)
[2017-03-02 19:39] [ALPM] upgraded libx11 (1.6.4-1 -> 1.6.5-1)
[2017-03-02 19:39] [ALPM] upgraded nvidia-utils (378.13-1 -> 378.13-3)
[2017-03-02 19:39] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-mo$
[2017-03-02 19:39] [ALPM] upgraded nvidia-libgl (378.13-1 -> 378.13-3)
[2017-03-02 19:39] [ALPM] warning: /etc/cups/cups-pdf.conf installed as /etc/cups/cups-pdf.conf.pacnew
[2017-03-02 19:39] [ALPM] upgraded cups-pdf (3.0.0-1 -> 3.0.1-1)
[2017-03-02 19:39] [ALPM] upgraded curl (7.52.1-2 -> 7.53.1-1)
[2017-03-02 19:39] [ALPM] upgraded wayland (1.12.0-1 -> 1.13.0-1)
[2017-03-02 19:39] [ALPM] upgraded pango (1.40.3-2 -> 1.40.4-1)
[2017-03-02 19:39] [ALPM] upgraded gtk-update-icon-cache (3.22.8-1 -> 3.22.9-1)
[2017-03-02 19:39] [ALPM] upgraded gtk3 (3.22.8-1 -> 3.22.9-1)
[2017-03-02 19:39] [ALPM] upgraded gstreamer (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded gtk3-print-backends (3.22.8-1 -> 3.22.9-1)
[2017-03-02 19:39] [ALPM] upgraded gst-plugins-base-libs (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded harfbuzz-icu (1.4.2-1 -> 1.4.3-1)
[2017-03-02 19:39] [ALPM] upgraded gdm (3.22.1-1 -> 3.22.2-1)
[2017-03-02 19:39] [ALPM] upgraded git (2.11.1-1 -> 2.12.0-1)
[2017-03-02 19:39] [ALPM] upgraded gst-libav (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded gst-plugins-bad (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded gst-plugins-base (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded gst-plugins-good (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded gst-plugins-ugly (1.10.3-1 -> 1.10.4-1)
[2017-03-02 19:39] [ALPM] upgraded iproute2 (4.10.0-1 -> 4.10.0-2)
[2017-03-02 19:39] [ALPM] upgraded lib32-libglvnd (0.1.1.20161028-1 -> 0.1.1.20161028-1.1)
[2017-03-02 19:39] [ALPM] upgraded libarchive (3.3.0-1 -> 3.3.1-4)
[2017-03-02 19:39] [ALPM] upgraded libfbclient (2.5.6.27020-2 -> 2.5.7.27050-1)
[2017-03-02 19:39] [ALPM] upgraded libtracker-sparql (1.10.4-2 -> 1.10.5-1)
[2017-03-02 19:39] [ALPM] upgraded linux-firmware (20170217.12987ca-1 -> 20170217.12987ca-2)
[2017-03-02 19:39] [ALPM] upgraded nano (2.7.4-1 -> 2.7.5-1)
[2017-03-02 19:39] [ALPM] upgraded python-appdirs (1.4.1-1 -> 1.4.2-1)
[2017-03-02 19:39] [ALPM] upgraded python-setuptools (1:34.2.0-1 -> 1:34.3.0-1)
[2017-03-02 19:39] [ALPM] upgraded tracker (1.10.4-2 -> 1.10.5-1)
[2017-03-02 19:39] [ALPM] upgraded xine-lib (1.2.6-13 -> 1.2.8-1)
[2017-03-02 19:39] [ALPM] upgraded zeitgeist (1.0-1 -> 1.0+1+g1bcc8585-1)
Comment by Stefan J. Betz (encbladexp) - Friday, 03 March 2017, 16:46 GMT
I can confirm this bug, using startx gnome-session works fine as a alternative for people wo don't need gdm temporary. Downgrading libgdm and gdm also solves this Issue.
Comment by Tom (tomhah) - Friday, 03 March 2017, 21:19 GMT
Same issue, temporarily solved by downgrading libgdm and gdm.
Comment by Deactivated account (TechnicalTotoro) - Friday, 03 March 2017, 22:29 GMT
I have attached some sample output from journalctl which may prove somewhat useful as it has errors related to this.
Comment by Deactivated account (TechnicalTotoro) - Friday, 03 March 2017, 22:52 GMT
Should this issue be reported in the upstream GNOME bugtracker?
Comment by Sunny Wong (ArchDoctor_needed) - Saturday, 04 March 2017, 06:17 GMT
+1 Same issue. "Gnome on Xorg" and "Gnome Classic" works as workaround.
Comment by vaibhav (captJrod) - Saturday, 04 March 2017, 18:43 GMT
This latest updates for xorg-server and xorg-server-xwayland didn't solve the looping issue.

Amazingly downgrading of libgdm and gdm (3.22.2-1 -> 3.22.1-1) is working with this new xorg-server updates.

[2017-03-04 19:26] [ALPM] upgraded tzdata (2016j-1 -> 2017a-1)
[2017-03-04 19:26] [ALPM] upgraded libutil-linux (2.29.1-1 -> 2.29.2-1)
[2017-03-04 19:26] [ALPM] upgraded xorg-server-common (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:26] [ALPM] upgraded libgpg-error (1.26-1 -> 1.27-1)
[2017-03-04 19:26] [ALPM] upgraded util-linux (2.29.1-1 -> 2.29.2-1)
[2017-03-04 19:26] [ALPM] upgraded xorg-server (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:26] [ALPM] upgraded xorg-server-xwayland (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:26] [ALPM] upgraded libgdm (3.22.1-1 -> 3.22.2-1)
[2017-03-04 19:26] [ALPM] upgraded gdm (3.22.1-1 -> 3.22.2-1)
[2017-03-04 19:26] [ALPM] upgraded gnupg (2.1.18-2 -> 2.1.19-1)
[2017-03-04 19:26] [ALPM] upgraded lib32-util-linux (2.29.1-1 -> 2.29.2-1)
[2017-03-04 19:27] [ALPM] upgraded python-setuptools (1:34.3.0-1 -> 1:34.3.1-1)
[2017-03-04 19:27] [ALPM] upgraded python2-setuptools (1:34.3.0-1 -> 1:34.3.1-1)
[2017-03-04 19:27] [ALPM] upgraded totem (3.22.0+5+ge0bf46e-1 -> 3.22.1-1)
[2017-03-04 19:27] [ALPM] upgraded xf86-video-ati (1:7.8.99.r24.g80fc7863-1 -> 1:7.8.99.r38.g9035b6ab-1)
[2017-03-04 19:27] [ALPM] upgraded xf86-video-intel (1:2.99.917+757+g93942b7d-1 -> 1:2.99.917+760+ge9cd8c21-1)
[2017-03-04 19:27] [ALPM] upgraded xorg-server-devel (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:27] [ALPM] upgraded xorg-server-xdmx (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:27] [ALPM] upgraded xorg-server-xephyr (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:27] [ALPM] upgraded xorg-server-xnest (1.19.1-5 -> 1.19.2-1)
[2017-03-04 19:27] [ALPM] upgraded xorg-server-xvfb (1.19.1-5 -> 1.19.2-1)
Comment by Jan de Groot (JGC) - Saturday, 04 March 2017, 21:55 GMT
Please try gdm-3.22.2+6+g4c7af60f-1 / libgdm-3.22.2+6+g4c7af60f-1.
Comment by Kelvyn Tesoro (princealohurr) - Sunday, 05 March 2017, 06:21 GMT
gdm-3.22.2+6+g4c7af60f-1 & libgdm-3.22.2+6+g4c7af60f-1.

Wayland login via GDM now works with updated packages.

Loading...