You are not logged in.

#1 2017-04-25 08:55:47

gkun
Member
Registered: 2016-06-11
Posts: 91

Gnome wayland not starting

I am using an Nvidia Geforce with proprietary drivers and Gnome 3.24 as just updated by Arch. I had read it was supposed to contain patches to make Wayland work on Nvidia drivers, and I thought I had it since choosing Gnome instead of Gnome on Xorg at login loaded the interface... but:

apr 25 10:20:04 Giankun gnome-session[406]: gnome-session-binary[406]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
apr 25 10:20:04 Giankun gnome-session-binary[406]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
apr 25 10:20:05 Giankun gnome-shell[413]: Can't initialize KMS backend: could not find drm kms device
apr 25 10:20:05 Giankun gnome-session[406]: gnome-session-binary[406]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
apr 25 10:20:05 Giankun gnome-session-binary[406]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
apr 25 10:20:05 Giankun gnome-session-binary[406]: Unrecoverable failure in required component org.gnome.Shell.desktop
apr 25 10:20:05 Giankun systemd-logind[353]: Removed session c1.
apr 25 10:20:05 Giankun gdm[371]: Child process -402 was already dead.
apr 25 10:20:05 Giankun gdm[371]: Child process 391 was already dead.
apr 25 10:20:05 Giankun gdm[371]: Unable to kill session worker process
apr 25 10:20:05 Giankun systemd[1]: Stopping User Manager for UID 120...
apr 25 10:20:05 Giankun systemd[395]: Stopped target Default.
apr 25 10:20:05 Giankun systemd[395]: Stopping D-Bus User Message Bus...
apr 25 10:20:05 Giankun systemd[395]: Stopped D-Bus User Message Bus.
apr 25 10:20:05 Giankun systemd[395]: Stopped target Basic System.
apr 25 10:20:05 Giankun systemd[395]: Stopped target Paths.
apr 25 10:20:05 Giankun systemd[395]: Stopped target Sockets.
apr 25 10:20:05 Giankun systemd[395]: Closed Sound System.
apr 25 10:20:05 Giankun systemd[395]: Stopped target Timers.
apr 25 10:20:05 Giankun systemd[395]: Closed D-Bus User Message Bus Socket.
apr 25 10:20:05 Giankun systemd[395]: Reached target Shutdown.
apr 25 10:20:05 Giankun systemd[395]: Starting Exit the Session...
apr 25 10:20:05 Giankun systemd[395]: Received SIGRTMIN+24 from PID 422 (kill).
apr 25 10:20:05 Giankun systemd[396]: pam_unix(systemd-user:session): session closed for user gdm
apr 25 10:20:05 Giankun systemd[1]: Stopped User Manager for UID 120.
apr 25 10:20:05 Giankun systemd[1]: Removed slice User Slice of gdm.
apr 25 10:20:05 Giankun systemd[1]: Created slice User Slice of gdm.
apr 25 10:20:05 Giankun systemd[1]: Starting User Manager for UID 120...
apr 25 10:20:05 Giankun systemd-logind[353]: New session c2 of user gdm.
apr 25 10:20:05 Giankun systemd[1]: Started Session c2 of user gdm.
apr 25 10:20:05 Giankun systemd[428]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
apr 25 10:20:05 Giankun systemd[428]: Starting D-Bus User Message Bus Socket.
apr 25 10:20:05 Giankun systemd[428]: Reached target Timers.
apr 25 10:20:05 Giankun systemd[428]: Reached target Paths.
apr 25 10:20:05 Giankun systemd[428]: Listening on Sound System.
apr 25 10:20:05 Giankun systemd[428]: Listening on D-Bus User Message Bus Socket.
apr 25 10:20:05 Giankun systemd[428]: Reached target Sockets.
apr 25 10:20:05 Giankun systemd[428]: Reached target Basic System.
apr 25 10:20:05 Giankun systemd[428]: Starting Update XDG user dir configuration...
apr 25 10:20:05 Giankun systemd[428]: Started Update XDG user dir configuration.
apr 25 10:20:05 Giankun systemd[428]: Reached target Default.
apr 25 10:20:05 Giankun systemd[428]: Startup finished in 36ms.
apr 25 10:20:05 Giankun systemd[1]: Started User Manager for UID 120.
apr 25 10:20:05 Giankun systemd[428]: Started D-Bus User Message Bus.
apr 25 10:20:06 Giankun gnome-session[440]: gnome-session-binary[440]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
apr 25 10:20:06 Giankun gnome-session-binary[440]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
apr 25 10:20:06 Giankun gnome-shell[447]: Can't initialize KMS backend: could not find drm kms device
apr 25 10:20:06 Giankun gnome-session[440]: gnome-session-binary[440]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
apr 25 10:20:06 Giankun gnome-session-binary[440]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
apr 25 10:20:06 Giankun gnome-session-binary[440]: Unrecoverable failure in required component org.gnome.Shell.desktop
apr 25 10:20:06 Giankun gdm[371]: GdmDisplay: display lasted 0,331225 seconds
apr 25 10:20:06 Giankun gdm[371]: Child process -436 was already dead.
apr 25 10:20:06 Giankun gdm[371]: Child process 418 was already dead.
apr 25 10:20:06 Giankun gdm[371]: Unable to kill session worker process
apr 25 10:20:06 Giankun systemd-logind[353]: Removed session c2.
apr 25 10:20:06 Giankun systemd[1]: Stopping User Manager for UID 120...
apr 25 10:20:06 Giankun systemd[428]: Stopping D-Bus User Message Bus...
apr 25 10:20:06 Giankun systemd[428]: Stopped target Default.
apr 25 10:20:06 Giankun systemd[428]: Stopped D-Bus User Message Bus.

What is happening? Can I make it work?

Offline

#2 2017-04-25 12:08:37

Omar007
Member
Registered: 2015-04-09
Posts: 368

Re: Gnome wayland not starting

Did you enable nVidia KMS?
https://wiki.archlinux.org/index.php/NV … de_setting

Though do note that there is currently an open bug related to Wayland and the proprietary drivers. Iirc it does start up but it's not really useable at all.

Last edited by Omar007 (2017-04-25 12:09:30)

Offline

#3 2017-04-25 17:17:42

gkun
Member
Registered: 2016-06-11
Posts: 91

Re: Gnome wayland not starting

Yes, I knew of the bugs, but I thought those would have been solved with the 3.24 update because of redhat code getting to the package.

In particular I was referring to the patches which were expected to get into the 3.24 package for supporting NVIDIA's EGLStreams, which I read about in this topic:

https://bbs.archlinux.org/viewtopic.php?id=221512

So what happened? Are the patches inside the package I am using or it's not even worth trying? Or worse yet the patches are there, but they don't solve things?

Last edited by gkun (2017-04-25 17:43:49)

Offline

#4 2017-04-26 04:03:06

guerch
Member
Registered: 2014-09-11
Posts: 31

Re: Gnome wayland not starting

The patches are there, but its not working properly, and even when they fix the issues, there is a gigantic gap that is not yet filled,  there is no xwayland support,  that translates into software rendering only for xwayland apps,  no acceleration on chrome (chrome://gpu) will show software only everywhere and anything else that is not native wayland will be software only. I am curious if fedora will enable kms on nvidia blob and make their users have by default a slow ass desktop.

Offline

#5 2017-04-26 09:43:02

gkun
Member
Registered: 2016-06-11
Posts: 91

Re: Gnome wayland not starting

Oh my... this Wayland issue is frustrating. I think I may try it again one year from now. Maybe.

Offline

#6 2017-04-26 22:30:19

igalmarino
Member
From: San Jose, Costa Rica
Registered: 2008-09-19
Posts: 5
Website

Re: Gnome wayland not starting

If you have more than one graphic card you need to disable KMS on the discrete one.

For example if you have an nvidia card add this to your bootloader

nouveau.modeset=0

Ignacio

Last edited by igalmarino (2017-04-26 22:30:48)

Offline

#7 2017-04-27 15:48:59

Omar007
Member
Registered: 2015-04-09
Posts: 368

Re: Gnome wayland not starting

igalmarino wrote:

If you have more than one graphic card you need to disable KMS on the discrete one.

I don't know where you're getting that from but out of all the things you could do, disabling KMS is the most counter-productive one of all if you want to use Wayland...

Last edited by Omar007 (2017-04-27 15:51:03)

Offline

#8 2017-04-30 20:50:10

Omar007
Member
Registered: 2015-04-09
Posts: 368

Re: Gnome wayland not starting

So I gave this a shot myself to see what the current state is.

First, since I was running 2 nVidia GPU's (no iGPU present), I had to take out one of them otherwise it would try to set KMS on both cards which would just make them both unusable and I would have to SSH into the system to disable KMS and reboot...
After removing the second GPU, I could enable KMS normally (see WIKI) and boot Gnome in Wayland normally.
However, at this point we've reached the point I mentioned earlier. While it does work, it's not really useable (it's very laggy).
I believe the bug that is open for this is 53284 so it seems we need a glvnd and/or mesa update.

On the positive side, a bunch of stuff that didn't work under Xorg works perfectly fine under Wayland big_smile
(such as VT switching with my n-key rollover keyboard)


EDIT: I gave mesa-git a try (17.2.0_devel.91510.a5c6ca9602-1 at the time of writing) and this actually seems to solve things yikes
So I guess the only thing blocking me from using this now is the fact that I have to take out the second GPU hmm

Last edited by Omar007 (2017-04-30 21:48:49)

Offline

#9 2017-05-01 06:16:01

guerch
Member
Registered: 2014-09-11
Posts: 31

Re: Gnome wayland not starting

@Omar007,  my biggest gripe is that  all Xwayland apps will run on software,  no accelerated openGL

Offline

Board footer

Powered by FluxBB