Arch Linux

RicArch97

Member

Registered: 2020-09-24

Posts: 2

Unable to start a wayland session on Gnome

I'm running Gnome on X11 for a while now, and it's stable and everything works fine. However, I'm working with a 4K and ultrawide 1440p monitor, and heard Wayland supports per-monitor scaling. So i wanted to switch over.
I've read the Gnome wiki and trying to start a wayland session generates the following:

$ XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
dbus-daemon[7266]: [session uid=1000 pid=7266] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=7278 comm="flatpak --installations ")
dbus-daemon[7266]: [session uid=1000 pid=7266] Successfully activated service 'org.gtk.vfs.Daemon'
fusermount3: failed to access mountpoint /run/user/1000/gvfs: Permission denied

/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.
A connection to the bus can't be made

Tried starting from TTY as well by putting this in .bash_profile:

MOZ_ENABLE_WAYLAND=1 
QT_QPA_PLATFORM=wayland 
XDG_SESSION_TYPE=wayland 
exec dbus-run-session gnome-session

This generates this same output, but then looped. Conclusion: I'm unable to start Wayland at all.

• Gnome version: 3.36.6 (latest)

• Kernel: 5.8.10-zen1-1-zen (latest)

• GPU Driver: nvidia-455.23.04-1 (lastest)

I have enabled DRM by adding "nvidia-drm.modeset=1" to the kernel parameters.

I don't use GDM or any other display manager. I login and start display server from TTY.

Does anyone know the conflict? Am i missing something crucial? The "failed to access mountpoint" log points to no permissions to the file system, however I'm the only user on the system.
Any help or ideas would be appreciated.

Last edited by RicArch97 (2020-09-24 18:42:03)

jocheem67

Member

Registered: 2009-11-09

Posts: 250

Re: Unable to start a wayland session on Gnome

Tried starting from TTY as well by putting this in .bash_profile

Hi, You didn't put those lines in .xinitrc?
.xinitrc

Starting gnome? Then maybe it's wise to use GDM as display manager. I find that GDM is perhaps not the simplest DM, but I think it's preparing stuff once gnome starts. Never really looked into it though.Am just using it.
And..I'm not sure if I'm right about .xinitrc since that's probably just for starting Xorg based DE's. Someone with more knowledge could perhaps elaborate.
Well. You could try.

Last edited by jocheem67 (2020-09-25 04:27:08)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,361

Re: Unable to start a wayland session on Gnome

I'm fairly certain that the nvidia wayland integration in GNOME is/was broken (no hands on but it's just what I've read a while ago, might be off base anyway), but what happens if you don't run an additional dbus-run-session. You already have a valid dbus session after login, there shouldn't be an inherent need to start yet another one.

RicArch97

Member

Registered: 2020-09-24

Posts: 2

Re: Unable to start a wayland session on Gnome

I'm fairly certain that the nvidia wayland integration in GNOME is/was broken (no hands on but it's just what I've read a while ago, might be off base anyway), but what happens if you don't run an additional dbus-run-session. You already have a valid dbus session after login, there shouldn't be an inherent need to start yet another one.

When trying to start without dbus-run-session it just hangs. However, i just found out that i was able to launch a wayland session using

XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

when logging in as root.

It is likely that DBus doesn't not have the right permissions the access the filesystem from a user login. I'll do some research to see what i can find.