Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. 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#65397 - GNOME Wayland doesn't start

Attached to Project: Arch Linux
Opened by Ivan Molodetskikh (YaLTeR) - Thursday, 06 February 2020, 04:55 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 06 February 2020, 14:02 GMT
Task Type Bug Report
Category Packages: Extra
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 0
Private No

Details

Description:
I've installed GNOME, but when logging into the GNOME session the screen flashes black and goes back to GDM. Logging into GNOME Classic and GNOME Xorg works fine. I'm normally using sway, so Wayland works on my machine. GDM can start the sway session fine. Attached is everything printed into journalctl when I try to log in and it fails.

Additional info:
* package version(s): GDM 3.34.1-1, mutter 3.34.3+30+g4959ae8bc-1, gnome-shell 1:3.34.3-1
* config and/or log files etc.: the only change to the GNOME install was adding [Service] Type=idle to the GDM service as described in https://wiki.archlinux.org/index.php/GDM#GDM_freezes_with_systemd because otherwise GDM would freeze instead of starting.
* link to upstream bug report, if any

Steps to reproduce:
1. sudo pacman -Syu gnome
2. sudo systemctl enable gdm.service
3. Restart and try to log in with GNOME selected.
   log (9 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 06 February 2020, 14:02 GMT
Reason for closing:  Not a bug
Comment by Ivan Molodetskikh (YaLTeR) - Thursday, 06 February 2020, 06:31 GMT
I tried launching mutter --wayland on its own and it runs successfully.
Comment by Ivan Molodetskikh (YaLTeR) - Thursday, 06 February 2020, 06:40 GMT
I solved the issue. The culprit was an `exec fish` line in my `.bash_profile`. Very strange that it broke only GNOME Wayland of all the things.

Loading...