fungal_net wroteI tried this and got it started, used main arch repository sway and wlroots from obcommunity ...
Ooh. I am a bit surprised. I thought wlroots from obcommunity is still 0.12, and the gtkgreet greeter requires wlroots 0.13. Did you bypass the greeter and launch sway directly using `wayland-session sway`?
I disabled xwayland on /etc/sway/config but still I don't know whether it is running on wlroots or not.
Two tricks to tell whether or not a window is using xwayland:
1. Add the following to your sway config: (taken from
this reddit thread)
for_window [shell=".*"] title_format "%title :: %shell"
Native wayland windows will display `:: xdg-shell` in the window title.
2. More fun, but becomes tedious: run `xeyes`. It will only respond if the mouse is over an xwayland window.
My screen was abou 1/3 size and I couldn't adjust, then I noticed some of the sway executables were throwing linsystemd errors.
These are propably unrelated. For the systemd errors, has the sway package installed `/etc/sway/config.d/50-systemd-user.conf?` I simply deleted that file (actually, symlinked it to /dev/null to maintain package integrity while disabling the file).
The screen size is entirely determined by `sway-output` commands in your sway config (`~/.config/sway/config`).
So I tried to build aur's next version of wlroots-git and built it , but sway-git I couldnd't and it is needed in conjunction to wlroots-git 0.13
Recent versions of sway-git require sd-bus support. The minimal non-systemd version of sd-bus is
basu. So perhaps you can build sway-git if you have basu installed? (Although you may still need to patch the PKGBUILD.) Looking into this on my own machine, I was able to build sway-git because I still have libelogind kicking around, so sway-git build against that. But I don't run elogind; I run seatd instead.
I also noticed that swaybg is not a branched subprocess, it starts its own main branch
You are right. Any programs started via `exec` in your sway config run on their own branch. e.g. swaybg, swaybar. However, they are killed when sway exits.
I am a little lost, if you can throw some light to a sway/wayland nube.
Hope this helps. It still takes a bit of effort to get a more fully-functioning desktop on sway. I have built, installed and configured: swaybg, swayidle, swaylock, swaynagmode, and
mako for desktop notifications. I use i3status on my swaybar, but there are now plenty of alternatives available. Endless hours of tinkering await... :)
