XLibre - a fork of Xorg

[Vaguiner]

Foot says: err: main.c:436: setlocale() failed

Loaded mylocale, etc. But still:

Code: [Select]

locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX

[Juanito]

I couldn't run any terminal.

Did you try havoc?

[GNUser]

Loaded mylocale, etc. But still:

Code: [Select]

locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX

Hi Vaguiner. A UTF-8 locale is required for  foot  to work, as stated in its  .info  file. It seems your locale is not correctly configured. You need to see something along these lines:

Code: [Select]

$ locale -a
C
en_US.utf8
POSIX

$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=Once your locale is set correctly,  foot  should work. I use foot 1.21.0 in TCL16 x86_64 as my daily driver without issues.

[Vaguiner]

Did you try havoc?

Got it


The whole thing feels more elegant, smooth, and responsive. Definitely a good thing.

[Vaguiner]

Everything works as it should, so it's probably close to perfect. Heh, who would have thought that TinyCore, such a conservative and tinysystem, would now be one of the first to be able to run Wayland only?

Thanks, I'll keep that in mind. However, although very tempting, it's not feasible for me to stay on 15w.x with so many extensions that have already been updated on 16.x.

btw my onboot is like this:

Code: [Select]

mylocale.tcz
firmware-i915.tcz
havoc
labwc
firmware-atheros
firmware-iwlwifi
wireless_tools
wifi
nano
file
Xorg-fonts
Took me some time to realize that labwc was refusing to spawn because of missing extension Xorg-fonts

I also have no idea how to change the keyboard layout. In dwl, it's easier to do it through the source code.
"file" is missing by nano

[GNUser]

I also have no idea how to change the keyboard layout.

In labwc it's done through environment variables, which you define in ~/.config/labwc/environment

I like US standard layout as default, with ability to switch to US international layout by pressing Shift+CapsLock. So, as an example, this is what my ~/.config/labwc/environment looks like:

Code: [Select]

$ cat ~/.config/labwc/environment
XKB_DEFAULT_LAYOUT=us,us(intl)
XKB_DEFAULT_OPTIONS=grp:shift_caps_toggle
XCURSOR_THEME=Bibata-Original-Ice
XCURSOR_SIZE=24
More details here:
https://github.com/labwc/labwc/blob/master/docs/environment
https://labwc.github.io/labwc-config.5.html#environment_variables

[nick65go]

It will be nice if this will evolve in a TC wiki specifically dedicated to Wayland and its application.
Maybe short tips of what config to load, what options are for menu, terminal, keyboard, panel, taskbar etc.

They can be in each .info files, but centralized in a wiki page could be better (even if just concatenate of copy/paste *.info).
And maybe some links to developer source/docs for people who want to spend time to read the fine tune ups. (as GNUser already started listing few).

[Rich]

Hi nick65go

It will be nice if this will evolve in a TC wiki specifically dedicated to Wayland and its application. ...

Thank you for volunteering, and congratulations, you've been promoted to Wiki Author.

[GNUser]

what options are for menu, terminal, keyboard, panel, taskbar etc.

Hi nick65go. If you are using a wlroots-based compositor such as sway or labwc, here is a helpful list of options:

https://github.com/solarkraft/awesome-wlroots

[nick65go]

Hi nick65go
Thank you for volunteering, and congratulations, you've been promoted to Wiki Author.

@Rich: Thank you for your trust and your over-estimating of my skills   
I am still on CachyOS with KDE (Kwin windows manager). But I will prepare something offline and message you when is suitable (after testing my findings) and when time will allow me to focus more on TC. Tiny-core still remains for me a nice project to promote and survive.
FYI: Until now, I never wrote any wiki articles and my English is not native. It could become embarrassing to me.

[GNUser]

Hi Juanito, Rich, curaga, Paul_123. I'm pleasantly surprised to see that XLibre is taking off: Currently there are 535 contributors to its xserver, with a very active merge history. The XLibre developers seem seriously committed to maintaining and improving X.

Some OSes have no plans of abandoning X. Among those, some are moving from Xorg to XLibre (GhostBSD, for example: https://ericbsd.com/addressing-xlibre-change-and-ghostbsd-future.html).

What are your thoughts on TCL moving from Xorg to XLibre? Do you think such a move would add stability to TCL? I'd be interested in your thoughts on this. I'm willing to help with packaging and testing, of course.

EDIT: I'd also be happy with the status quo (Xorg) and a wait-and-see approach. Kindly let me know your thoughts--I've always been happy just going along with whatever TCL is doing

[GNUser]

The silence is eloquent. I hear "status quo is preferable" loud and clear. Works for me

[Rich]

Hi GNUser
Maybe these warnings served as a deterrent:

Upgrade notice

    Module ABIs have changed - drivers MUST be recompiled against this Xserver version, otherwise the Xserver can crash
    or fail to start up correctly.

    If your console is locked up (no input possible, not even VT switch), then most likely the input driver couldn't be loaded due
    to a version mismatch. When unsure, it's best to be prepared to ssh into your machine from another one or set a timer
    that's calling chvt 1 after certain time, so you don't need a cold reboot. Or, make sure that you have magic SysRq key
    enabled (Alt+PrtSc) via sysctl (kernel.sysrq=1), then press following combination depending on keyboard layout to
    make kernel regain control over keyboard to make VT switching work:
        QWERTY/AZERTY keyboard layout: SysRq + R
        Dvorak/Colemak keyboard layout: SysRq + P

    Proprietary Nvidia drivers might break: they still haven't managed to do even simple cleanups to catch up with Xorg master
    for about a year. All attempts to get into direct mail contact have failed. We're trying to work around this, but cannot give
    any guarantees. But you can make it work by adding Option "IgnoreABI" "1" line to ServerFlags section in Xorg
    config.

    Most Xorg drivers should run as-is (once recompiled!), with some exceptions. See .gitlab-ci.yml for the versions/
    branches built along with Xlibre.

Found here:
https://github.com/X11Libre/xserver/tree/xlibre-xserver-25.0.0.0

Outright replacement of Xorg with Xlibre runs the risk of unforeseen breakage.
I doubt there is any appetite for that.

I also don't see any clean and simple way for Xlibre to co-exist with Xorg to
allow someone to switch back and forth between the two.

[GNUser]

Outright replacement of Xorg with Xlibre runs the risk of unforeseen breakage.
I doubt there is any appetite for that.

Breakage is not my favorite dish, either

I naively thought XLibre was a drop-in replacement for Xorg, maintained by folks committed to its longevity. Real life is always more messy than theory.

I'm happy to kick this can down the road.

[Juanito]

The silence is eloquent. I hear "status quo is preferable" loud and clear. Works for me

Perhaps it's worth detailing where we are now with x11 and wayland:

x86 (TinyCore)
Xvesa, Xfbdev and xorg-server are all available
mesa is not compiled for wayland in the interests of keeping things small
fltk-1.3 does not support wayland

x86_64 (TinyCorePure64)
Xfbdev and xorg-server are available
mesa is compiled for x11 and wayland
fltk-1.4 supports wayland so the tinycore applets are available in a wayland compositor

armhf (piCore)
xorg-server is available
mesa is compiled for x11 and wayland
fltk-1.4 supports wayland so the tinycore applets are available in a wayland compositor

aarch64 (piCore64)
xorg-server is available
mesa is compiled for x11 and wayland
fltk-1.4 supports wayland so the tinycore applets are available in a wayland compositor

x11 is becoming increasingly unsupported, particularly for x86 (xorg-server will not start with my intel hd4400 graphics using the modesetting driver, but will start with the obsolete xf86-video-intel driver)

wayland is becoming increasingly supported, wayland-only test versions of x86_64 and aarch64 work well (firefox works noticeably better on an RPi3 with wayland as compared to x11). All gtk3 and gtk4 apps work with wayland.

XLibre might make sense for x86, particularly if it updates Xvesa and Xfbdev (I don't know if this is planned), but I'm not sure if it makes sense for x86_64, armhf or aarch64.

The decision to be taken is perhaps not deciding between x11 and XLibre, but rather deciding between x11/XLibre and wayland.