Sway, Wayland, and Xwayland

[Greg V]

On June 13, 2019 10:36:26 PM GMT+03:00, Dale Brazelton <dalebrazelton at outlook.com> wrote:
>Even after implementing all the suggestions from Jan I was unable to
>get firefox to work in sway, neither natively in wayland or with
>xwayland. After spending a good part of yesterday testing it, I'm
>convinced my problems are due to the implementation of amdgpu in
>FreeBSD 12 stable. For example, I could only run sway once per boot. If
>I ever exited sway and tried to restart it my computer would hang and
>I'd have to power it off.

Yeah, recovery from a compositor exit has always been.. fun. With my consolekit2 setup, quitting and restarting a compositor sometimes works.

> (I realize I'm probably the only person in
>the world trying to run a FreeBSD desktop on an amd Vega 64 graphics
>card!)

Oh no, I'm using a Vega daily, been doing that since last winter (and used an RX 480 before that). And several people with Vega have reported bugs on our GitHub issue tracker (FreeBSDDesktop/kms-drm).

> I'll postpone further testing until we have a more up to date
>amdgpu, mesa, xorg-server, and xwayland in 12 stable.

Why wait when you can use -CURRENT and kms-drm from git? :D