Can't get Wayland to start

[GlenH]

Hi all-

Yesterday I finally got tired of Ubuntu's broken upgrade system and installed FreeBSD on my home server. I used FreeBSD twenty years ago but not since, so I'm a newbie.

It's mostly all good, except that I can't get a Wayland session to start (X11 sessions work fine).

I've installed the Wayland packages. I've read the docs, followed the steps, enabled dbus and seatd and linux in my rc.conf, and verified that I have a correctly configured /var/run/user/($id -u) directory. I have drm-61-kmod installed.

I'm trying to run plasma6. I have sddm installed. I can select a Wayland session, but when I log in my screen goes black for a few seconds and then it kicks me back to the login screen.

I'm running an NVIDIA GT 1030 graphics card. As I said, X11 works fine (except that I get a low resolution screen, and can't negotiate the correct screen resolution. Not sure if that's related.

Any tips?

 

[it-people]

Try and disable sddm, and start it from the console with this:
dbus-launch --exit-with-session ck-launch-session startplasma-wayland

 

[USerID]

... and verified that I have a correctly configured /var/run/user/($id -u) directory.

chown your_user_name /var/run/user/1001
chmod 700 /var/run/user/1001
XDG_RUNTIME_DIR=/var/run/user/1001

 

[scottro]

One question--is that an old Nvidia card? I wasn't able to get Wayland to work until an NVidia driver upgrade. I think it's all be fixed, but I'm not sure about the older cards.
Ah, I see I'm using a 1030 as well. I don't think you have to do anything with the /var/run/user anymore. It just works automagically. For the heck of it you might try with a simple window manager like dwl. But as it-people said you might get better results with dbus-launch --exit-with-session. I use that with dwl, but not with labwc which I just launch with a simple labwc.
Other stupid question--you said you followed the handbook but is seatd definitely running?

Also I have no trouble with resolution (in X or Wayland).
I have the nvidia-driver-570.169.1403000 driver, the nvidia 570.169. nvidia-drm-kmod and linux-nvidia-libs-570.169 Be
sure you have the latest Nvidia-packages.

 

[SirDice]

chown your_user_name /var/run/user/1001
chmod 700 /var/run/user/1001
XDG_RUNTIME_DIR=/var/run/user/1001

I don't think you have to do anything with the /var/run/user anymore. It just works automagically.

pam_xdg(8) is available from 14.1 onward. This sets it up for you.

 

[GlenH]

Try and disable sddm, and start it from the console with this:
dbus-launch --exit-with-session ck-launch-session startplasma-wayland

When I do that, I get a bunch of errors, but these seem to be the most important ones:

kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found

Then it logs me out.

 

[GlenH]

"Other stupid question--you said you followed the handbook but is seatd definitely running?"

If I do:

sudo service seatd start

the console tells me

seatd already running? (pid=1613)

 

[GlenH]

"I have the nvidia-driver-570.169.1403000 driver, the nvidia 570.169. nvidia-drm-kmod and linux-nvidia-libs-570.169"

I appear to have nvidia-driver-570.169.1402000 and nvidia-drm-kmod-570.169. I did not have the linux-nvidia-libs package installed, and I was really hopeful that that was the problem, but I installed them and rebooted and the errors I get when starting Wayland are exactly the same.

 

[GlenH]

Of note: I cannot start a plasma X11 session using "exec dbus" either. I get

$DISPLAY is not set or cannot connect to the server

 

[GlenH]

OK, so, I'm not sure what exactly did it, but it's now (mostly) working. I cannot start it using the exec dbus command, but if I issue a 'startx' from the console, it starts plasma and a check of the system info tells me it's a Wayland session.

Only problem now it that the system does not correctly detect the resolution of my monitor.

 

[USerID]

$DISPLAY.
Used by X11 clients to select the X display. Values: 0,1...
Display sockets:

# cd /tmp/.X11-unix/
# ls


 

[USerID]

Backends are defined via variables.
GDK_BACKEND=wayland is a GTK subsystem that handles windows (how GTK applications work).

 

[piizog]

When I do that, I get a bunch of errors, but these seem to be the most important ones:

kwin_wayland_drm: failed to open drm device at "/dev/dri/card0"
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found

Then it logs me out.

I had the same exact same problem, but turned out that the Handbook is written in a way that when I went through the steps, I didn't have both seatd and dbus enabled in rc.conf. After that it's all worked smooth, though I haven't tried SDDM since I mainly use gui apps through cage on my system.

I think it might be a good time to update the Handbook so that if you want a desktop on Wayland, you don't have to jump around from the desktop chapter that covers X11 and the chapter covering Wayland separately but rather have one desktop chapter that covers both now that the Wayland support seems pretty mature.