[SOLVED] can't start wayland session

downey · 2023-02-16 19:30:41

when i login the option to login to a wayland session is not available

when i execute this command i get this at the output:

sudo XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
dbus-daemon[2955]: [session uid=0 pid=2955] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=0 pid=2982 comm="/usr/lib/gnome-session-check-accelerated")
dbus-daemon[2955]: [session uid=0 pid=2955] Successfully activated service 'org.gtk.vfs.Daemon'
dbus-daemon[2955]: [session uid=0 pid=2955] Activating service name='ca.desrt.dconf' requested by ':1.5' (uid=0 pid=2956 comm="/usr/lib/gnome-session-binary")
dbus-daemon[2955]: [session uid=0 pid=2955] Successfully activated service 'ca.desrt.dconf'
A connection to the bus can't be made

the output of journalctl
pastebin journalctl

i'm not sure what to do any ideas?
these are my specs:

OS: Arch Linux x86_64 
Host: X580VD 1.0 
Kernel: 5.15.94-1-lts 
Shell: bash 5.1.16 
Resolution: 1920x1080 
DE: GNOME 43.3
CPU: Intel i7-7700HQ (8) @ 3.800GHz 
GPU: NVIDIA GeForce GTX 1050 Mobile 
GPU: Intel HD Graphics 630 
Memory: 2943MiB / 15886MiB

i use GDM with an igpu as my gpu

Last edited by downey (2023-02-18 15:00:19)

Trilby · 2023-02-16 19:35:30

Be glad it failed. Do not run gnome (or any full gui session) as root. Use the command as documented in the wiki, without adding 'sudo'.

EDIT: though there are also seg faults from appimagelauncher which might remain even without sudo, but really try starting it right first, and report any errors from that.

Last edited by Trilby (2023-02-16 19:38:02)

downey · 2023-02-16 19:37:23

this is the output without sudo

[downey@archLappy ~]$ XDG_SESSION_TYPE=wayland dbus-run-session gnome-session
dbus-daemon[5263]: [session uid=1000 pid=5263] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=5287 comm="/usr/lib/gnome-session-check-accelerated")
dbus-daemon[5263]: [session uid=1000 pid=5263] Successfully activated service 'org.gtk.vfs.Daemon'
fusermount3: failed to access mountpoint /run/user/1000/gvfs: Permission denied
dbus-daemon[5263]: [session uid=1000 pid=5263] Activating service name='ca.desrt.dconf' requested by ':1.4' (uid=1000 pid=5264 comm="/usr/lib/gnome-session-binary")
[downey@archLappy ~]$ A connection to the bus can't be made

Last edited by downey (2023-02-16 19:37:34)

downey · 2023-02-16 19:45:43

this is the journalctl of that command
https://pastebin.com/hsH9h2qU

downey · 2023-02-17 20:36:41

it has something to do with my nvidia drivers.
i did a fresh install f arch. wayland was working fine up until i installed the nvidia drivers.

i followed all the directions on the wiki (which were inconsistent) but still couldn't get it to work.

i added the "nvidia_drm.modeset=1" to the kernel params but this didn't do anything.
then i added the modules "nvidia nvidia_modeset nvidia_uvm nvidia_drm" to "/etc/mkinitcpio.conf" this also didn't seem to change much

this page told me to remove kms
while this page told me to add kms too the hooks array.
i tried both neither did anything. i don't really know what to do now.

Zod · 2023-02-17 23:11:02

What version of the nvidia drivers are you using?

Without looking at the nvidia wiki page (because that's your job) anything under 490 (or whatever) doesn't do wayland.

My gpu uses 390 if I choose to use the proprietary drivers.

Since I'm trying to have fun with wayland I have to use nouveau.

Trilby · 2023-02-18 01:17:06

Zod wrote:

... anything under 490 (or whatever) doesn't do wayland.

That's not quite true, that should say "doesn't do wayland except for gnome (and weston)". Given that the OP is trying to run gnome, the EGLStreams / GBM distinction ~~isn't~~ edit: shouldn't be relevant.

EDIT: I suppose I wouldn't put much past either nvidia or gnome, so when the two are mixed, you never can be sure. It's possible that as new versions of nvidia started supporting GBM, gnome maintenance of their EGLStreams support may be declining - but that's wild speculation and gnome should run fine on wayland on any nvidia version.

Last edited by Trilby (2023-02-18 01:19:51)

seth · 2023-02-18 06:29:15

but that's wild speculation and gnome should

So to see whether I need to link the video,
@downey, please post your complete system journal for the boot after trying to start the gnome wayland session:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

downey · 2023-02-18 09:43:34

Zod wrote:

What version of the nvidia drivers are you using?
Without looking at the nvidia wiki page (because that's your job) anything under 490 (or whatever) doesn't do wayland.
My gpu uses 390 if I choose to use the proprietary drivers.
Since I'm trying to have fun with wayland I have to use nouveau.

i'm using 525 acording to nvidia-smi

-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.89.02    Driver Version: 525.89.02    CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   45C    P8    N/A /  N/A |      4MiB /  2048MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1799      G   /usr/lib/Xorg                       4MiB |
+-----------------------------------------------------------------------------+

the output of the journal here

seth · 2023-02-18 12:10:56

Feb 18 10:34:01 archlinux systemd[1775]: Starting GNOME Shell on Wayland...
Feb 18 10:34:01 archlinux systemd[1775]: Starting GNOME Shell on X11...
Feb 18 10:34:01 archlinux systemd[1775]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
Feb 18 10:34:01 archlinux systemd[1775]: Condition check resulted in GNOME Shell on Wayland being skipped.

This is a hybrid-graphics system, GDM is running

Feb 18 10:33:49 archlinux systemd[1]: Started Session 1 of User gdm.

so we're at https://bbs.archlinux.org/viewtopic.php … 9#p2083239

https://bbs.archlinux.org/viewtopic.php … 8#p2083188 suggests that running gnome on wayland from the multi-user.target still works, though.

You're btw. also running on the intel chip, there're no outputs attached the the nvidia GPU.

downey · 2023-02-18 14:19:00

should i be editing the gdm.rule file? it seems like those rules are there for a reason. is it not recommended to use Wayland on a hybrid-graphics system?

edit: also what d you mean by "there is no outputs attached the the nvidia GPU"?
when i do run-prime it seems to work like expected.

Last edited by downey (2023-02-18 14:21:59)

seth · 2023-02-18 14:21:40

Boot the multi-user.target (2nd link below) and see whether you can launch gnome from there.

downey · 2023-02-18 14:54:51

launching gnome on wayland seems to work through that method.
somethings are terribly slow however. my shortcut to launch a terminal takes 20 seconds to execute the command for example.
prime-run doesn't seem to do anything. well... it launches the application but running NVIDIA-smi doesn't show the application being run in there.

also noticed that some application i own don't even support wayland. i think I'll just stick with xorg11 for now.

i really appreciate that you guys took the time and effort to help me with this issue.
i will mark the thread as solved. again thank you.

Arch Linux

#1 2023-02-16 19:30:41

[SOLVED] can't start wayland session

#2 2023-02-16 19:35:30

Re: [SOLVED] can't start wayland session

#3 2023-02-16 19:37:23

Re: [SOLVED] can't start wayland session

#4 2023-02-16 19:45:43

Re: [SOLVED] can't start wayland session

#5 2023-02-17 20:36:41

Re: [SOLVED] can't start wayland session

#6 2023-02-17 23:11:02

Re: [SOLVED] can't start wayland session

#7 2023-02-18 01:17:06

Re: [SOLVED] can't start wayland session

#8 2023-02-18 06:29:15

Re: [SOLVED] can't start wayland session

#9 2023-02-18 09:43:34

Re: [SOLVED] can't start wayland session

#10 2023-02-18 12:10:56

Re: [SOLVED] can't start wayland session

#11 2023-02-18 14:19:00

Re: [SOLVED] can't start wayland session

#12 2023-02-18 14:21:40

Re: [SOLVED] can't start wayland session

#13 2023-02-18 14:54:51

Re: [SOLVED] can't start wayland session

Board footer