Wayland

[hiro]

...
individual parts separately instead. It's also no longer a Freedesktop.org / Red Hat project which means fewer paid programmers are working on it. I always seem to get fed up with Freedesktop.org projects, I've even given up on Modem Manager now and had more success directly configuring pppd, so I'm tempted to consider this a good thing.

hahaha yes. been using pppd for a long time. since before modemmanager existed.
also AT commands and qmi and uqmi tools for 3G/4G modems, all manually, bec. each modem needs different quirks. for QMI i *tried* to use modemmanager, but it didn't work!
for wifi at first i also tried networkmanager, but it didn't work. bugs, performance issues, packet drops, impossible to debug.
so instead: for both ethernet and wifi: udhcpc (learned here from TC) with my own action script
and `wpa_cli -a actions.sh` with the same actions script for L1 events, in addition to link state events (from iproute2's `ip monitor`).
and wpa_supplicant, configured via the comfortable wpa_gui that ships with it.

even networkmanager hates networkmanager, so they use netplan now as a backend on the newest ubuntu (off-topic here i know, but probably worth the schadenfreude). at least that's editable in plaintext finally, it's much better than nm-cli now, which has a lot of unacceptable bugs that i keep running into on systems administered by others.

[hiro]

As mentioned above, using fltk-1.4, it’s possible to make a wayland only version of TinyCorePure64.

that's a relief, but my most important programs are aterm, urxvt, xterm

[Juanito]

Foot and havoc are described as minimal wayland terminal emulators, but I haven’t tried them.

[Juanito]

havoc added to x86_64 repo

[GNUser]

I gave weston a try on TCL14 x86_64. From the console, with a working network connection:

Code: [Select]

$ tce-load -wi weston xwayland aterm
$ XDG_RUNTIME_DIR=/run/user/$(id -u) weston-launchAfter that, weston starts successfully. It has a bar going across the top with an icon that, when clicked, causes the default terminal emulator (weston terminal) to launch successfully.

From weston terminal I'm unable to launch  aterm  or any other application that requires X. Error each time is some variation of "display :0 not found".

Please, in addition to loading xwayland, what else needs to be done in order for X applications to work in wayland (e.g., in weston)? Or will most applications that expect X not work with wayland?

(Pardon my ignorance--this is my first time ever not in an X session. I'm just kicking weston's tires at this point, to see if it would be a viable alternative to fluxbox if someday I were forced to "upgrade" to wayland.)

[gadget42]

poked around and stumbled into this FAQ which mentions weston/libweston a few times.

https://wayland.freedesktop.org/faq.html

[Juanito]

To use xwayland you need the following in ~/.config/weston.ini:

Code: [Select]

[core]
xwayland=true

[xwayland]
path=/usr/local/bin/Xwayland
Of course the idea is not to use xwayland, which is a little painfull as it means the tinycore helper gui applets don't work.

Note that all gtk3 apps will work without xwayland as it has a wayland backend - qt-5.x apps will probably work too.

Here's an example weston.ini without xwayland (the location of the adwaita icons may have changed):

Code: [Select]

[launcher]
icon=/usr/local/share/weston/icon_terminal.png
path=/usr/local/bin/weston-terminal

[launcher]
icon=/usr/local/share/icons/Adwaita/22x22/legacy/accessories-text-editor.png
path=/usr/local/bin/gedit

[launcher]
icon=/usr/local/share/icons/Adwaita/22x22/legacy/system-file-manager.png
path=/usr/local/bin/nautilus

[launcher]
icon=/usr/local/share/icons/Adwaita/22x22/legacy/web-browser.png
path=/usr/local/bin/firefox

[shell]
num-workspaces=4

[keyboard]
keymap_layout=gb

[output]
name=HDMI-A-1
mode=1920x1080

[Juanito]

Also useful: https://man.archlinux.org/man/weston-bindings.7.en

[GNUser]

Note that all gtk3 apps will work without xwayland as it has a wayland backend - qt-5.x apps will probably work too.

Hi Juanito. Thank you for sharing this very useful information. It will provide some pain relief.

brave-browser is a gtk3 app, so I guess it should work in wayland. This is what I see in weston, without xwayland, using the default terminal emulator:

Code: [Select]

$ sudo /usr/local/etc/init.d/dbus start
$ brave-browser
[9170:9170:1020/092545.448733:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
[9170:9170:1020/092545.448763:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
Any idea how to fix?

[GNUser]

Also useful: https://man.archlinux.org/man/weston-bindings.7.en

Thank you for that. I found this for custom keybindings: https://github.com/tarvi-verro/weston-binder
Do you think it would be useful to include this module in the weston extension?

[GNUser]

Code: [Select]

$ brave-browser
[9170:9170:1020/092545.448733:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
Any idea how to fix?

Hi Juanito. The fix in this case turned out to be easy:

Code: [Select]

$ brave-browser --ozone-platform=wayland

[GNUser]

I'm going to set a TCL instance aside for wayland testing, using its reference compositor. But weston depends on Xorg-7.7-3d and X starts automatically, which is inconvenient in this setting.

What's the most proper (i.e., TCL-idiomatic) way to prevent X from starting automatically?

[Juanito]

You can use the boot code “text”.

[GNUser]

You can use the boot code “text”.

Hi Juanito. That's exactly what I was looking for. Thank you very much.

[Juanito]

weston has been updpated in the x86_64 and aarch64 repos.

weston-launch has been depreciated, so the new way to start weston is:

Code: [Select]

sudo -- seatd -g staff -n /run/seatd.sock & XDG_RUNTIME_DIR=/run/user/1001 weston