Arch Linux

altermetax

Member

Registered: 2016-03-19

Posts: 73

GNOME Wayland crashing on startup

Hello everyone, I'm running GNOME 3.22.2 (extra/gnome-shell 3.22.2+18+gdf7727a-1 in pacman, latest version). It crashes if I start the "GNOME" session, but doesn't when starting "GNOME Classic" or "GNOME Xorg". If I select "GNOME", insert the password and hit the Login button, I just get the display manager to disappear for a second and reappear, letting me choose a user.
Should I install something? Why is this happening?

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 395

Re: GNOME Wayland crashing on startup

It happens because Wayland is not yet ready for general use. This is not news.

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

Omar007

Member

Registered: 2015-04-09

Posts: 368

Re: GNOME Wayland crashing on startup

It happens because Wayland is not yet ready for general use. This is not news.

That's mostly a matter of personal opinion. Imo Wayland is perfectly fine for general use.
Only some weird edge cases may present some problems but I can't think of any atm, nor can I think of any problems I have personally experienced with Wayland.
(personally I have plenty to name on Xorg...)

Opinions aside, to use Wayland you need a driver that supports KMS as well as a compositor that supports the API that the driver used. The compositor being Gnome (mutter) in this case.
For now that leaves you with basically only the open-source drivers as an option.
With the release of Gnome 3.24 it should also support the nVidia driver (which uses EGL Streams instead of GBM) but I have personally not yet been able to get that to work in the few times I have tried.

Last edited by Omar007 (2017-02-09 16:19:56)

c00ter

Member

From: Alaskan in Washington State

Registered: 2014-08-28

Posts: 395

Re: GNOME Wayland crashing on startup

It happens because Wayland is not yet ready for general use. This is not news.

That's mostly a matter of personal opinion. Imo Wayland is perfectly fine for general use.

I am not stating that Wayland--when it is indeed ready--won't be superior to old, strung-out Xorg. I'm sure it will be from what I have read. What I am stating is that for at least the past three months the most common complaint on these boards regarding GNOME has been Wayland-related, and the most common remedy has been to use tried and true Xorg. This is all anecdotal, based solely on my recollection of reading these forums daily. Accept it or not, as you wish.

In the meantime--how 'bout them Cubs?

Regards

---

UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

loqs

Member

Registered: 2014-03-06

Posts: 17,369

Re: GNOME Wayland crashing on startup

What is the output from the journal for gdm.service from a boot where the issue occurs?

hpstg

Member

Registered: 2007-06-09

Posts: 46

Re: GNOME Wayland crashing on startup

I have the exact same issue. Unless I disable wayland in GDM and login to a Xorg session, everything freezes seconds after logging in. It does the same with the stock kernel, the ck kernel, and both the open source radeon and amdgpu drivers. It has been like this until at least Gnome 3.18. This is what I get.

/usr/lib/gdm/gdm-x-session[2776]: (WW) xf86CloseConsole: KDSETMODE failed: Operation not permitted
/usr/lib/gdm/gdm-x-session[2776]: (WW) xf86CloseConsole: VT_SETMODE failed: Operation not permitted
/usr/lib/gdm/gdm-x-session[2776]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Operation not permitted
/usr/lib/gdm/gdm-x-session[2776]: (EE) Server terminated with error (1). Closing log file.
acpid[1008]: 1 client rule loaded