If you want to start gnome from the console as a wayland session then this script works for me:

I also have no problem starting both gnome and xfce using lightdm as a DM with the lightdm-gtk-greeter front end. You can also start gnome with SDDM.

Ok, good to hear that. I just tried it manually and it does not work for me here. I would be curious to see other configurations and packages which you have installed, especially the pam and elogind configs. Is that all without modifications ?

What errors do you get? I cannot see how the wayland script I mentioned could fail to work if wayland works when nested in X11.

Having said that, I don't use dropline (I have my own guile scripts which compile and install gnome for me). I had to patch mutter-3.36.0 to get it to work well with wayland but mutter-3.36.2 should be OK. I also had to patch cogl-1.22.6 to deal with a header issue I think brought about by slackware's introduction of libglvnd, and patch gnome-control-center-3.36 to keep it compiling with udisks-2.6.5 (if unpatched it now requires udisks-2.8 or greater). For PAM I use slackware-current's stock installation.

How do the wayland problems manifest themselves?

I get the following error:
mutter-WARNING **: Failed to create backend: Could not get session ID: User 1001 has no sessions.

That looks like an elogind issue, and that the daemon hasn't started. In that case, I wonder how it is that startx works for a X11 session? On looking at my PAM configuration I see that I have added '-session optional pam_elogind.so' to system-auth but I cannot see how that would be relevant to your issue. Try also forcing a new session with 'su [loginname]' before calling the script (yes I know you have already logged in, but ...) .

Thanks for the suggestions, su did not worked. I will have to work that on the pam / elogind side. But I also think that maybe the patch you are using for mutter could be the thing. Can you post that patch please ?

Oh well. That is rather odd.

I attach two patches for mutter-3.36.0. However these are not needed (and will not apply) for mutter-3.36.2. mutter-3.36.2 should work OK as is.

However you will need the cogl patch which I also attach. Although prepared for cogl-1.22.4, it is also required by cogl-1.22.6, and is brought about by slackware's libglvnd.

Attached Files

	mutter-3.36.0.crash.txt (490 Bytes, 5 views)
	mutter-3.36.0.wayland.txt (980 Bytes, 7 views)
	cogl-1.22.4.wayland.txt (1.5 KB, 3 views)

By the way, if you want to test your mutter compositor for wayland without invoking the whole of gnome, you can start a wayland desktop under mutter from the console with:
and then go to a different console and enter
and then start wayland aware applications from the xfce4-terminal.

You can also start X11 clients on this wayland session via Xwayland by defining DISPLAY as :0.

You have to do 'killall mutter' from the second console to kill the mutter desktop.

Edit I should also mention that all GTK-3 programs in slackware-current are now "wayland aware" for this purpose, including most of xfce (but not the window manager).

Thanks, mutter starting from within gnome x11 session from terminal gives me the same error. So it does not see that my user has a session. I will try to apply yor patches , by the way cogl has a new version out today so I will try to build it with the patch you supply here. Will see if I have some time to play with this during this weekend.

Thanks for now.

With the new cogl-1.22.8 you don't need the patch I gave you - it has been incorporated upstream and is now already applied. So both the latest mutter and cogl should work for you without patching.

Perfect, many thanks !

Hi Saxa,

I'm building Gnome myself using the BLFS instructions. I've managed to compile almost everything, except GDM. I can't get GDM to build and configure without systemd. How did you manage to do that? The Arch/Gentoo build scripts for GDM also give me zilch. I can't seem to turn of the systemd component for GDM.

Thanks for your great work, really looking forward to the new Dropline Gnome version!

Hi, you have to use elogind and set the SYSTEMD_LIBS and other flags to think it uses systemd. Take a look at the build scripts on sf.net
in the DLG_3_36 branch.

1 members found this post helpful.

Thanks Saxa,

I'll dig into it with your buildscripts and keep you posted.

Cheers,

Laurens

You might also want to look at the GUIX build for gdm at https://git.savannah.gnu.org/cgit/gu...ages/gnome.scm (search for "gdm"). Look in particular for "substitute*". Even so I've not got it to work under elogind, only under systemd, but clearly it can be done because GUIX manage it.

1 members found this post helpful.