Solved How to switch from X.org to Xlibre?

scottro said:
So, it might affect the quality of his software. It defintely make me feel suspicious when he says how he was silenced.
Click to expand...
xlibre has a number of developers working on it (more than most Wayland projects). One of them is stefan11111 who has in the past done some great work at cleaning up fundamental libraries (i.e gtk+2).

Speaking of which, there is even more interest for X11 and Gtk+2 in recent weeks.
 
freezr said:
I see this:

Code: 
xlibre-nvidia-driver-595.58.03_2 NVIDIA graphics driver userland
xlibre-nvidia-driver-304-304.137_11 NVIDIA graphics driver userland
xlibre-nvidia-driver-340-340.108_5 NVIDIA graphics driver userland
xlibre-nvidia-driver-390-390.157_1 NVIDIA graphics driver userland
xlibre-nvidia-driver-470-470.256.02_2 NVIDIA graphics driver userland
xlibre-nvidia-driver-580-580.142 NVIDIA graphics driver userland
xlibre-nvidia-driver-devel-595.58.03 NVIDIA graphics driver userland

What are they? Regular Xorg packages renamed as Xlibre? 🤷‍♂️
Click to expand...
No. These are ADDED.

I myself didn't accepted, but x11/nvidia-driver is fravorized, as xorg and xlibre keeping xorg to be default. Others (x11/nvidia-driver-{304|340|390|470|580|devel}) are child (slave) ports that simply overriding versions, PORTREVISION and suffixes. So also affected and additional pkgs are built.

xorg flavor (the default) didn't change pkg names and stay as-is.
 
MG said:
I have the idea it's an old X11R6 rip-off.
Click to expand...
Yes. At the era, Mk/bsd-default-versions.mk and USES framework were NOT implemented yet, thus, WITH_NEW_XORG Makefile variable was used to force xorg to be built instead of XFree86 (old X11R6 implementations) through the introduction of xorg and removal of duplicate ports are done at once.

This approach was very nice as it didn't confuse anyone who weren't understanding precisely what they were doing, and can be done much simpler with current ports framework. And was the way what I've proposed.
 
eternal_noob said:
XLibre is a scam, just use Wayland. 👻
Click to expand...
My experiences on Wayland were far, far more worse than Xorg.

So sticking with Xorg is the way to go until better alternatives appear, for example, UEFI evolves as hypervisor and provide all device supports as strictly standardized runtime / boottime services and basic windowing are done there (decorations and so on are kept per-OS / requesters).
 
T-Aoki said:
Yes. At the era, Mk/bsd-default-versions.mk and USES framework were NOT implemented yet, thus, WITH_NEW_XORG Makefile variable was used to force xorg to be built instead of XFree86 (old X11R6 implementations) through the introduction of xorg and removal of duplicate ports are done at once.

This approach was very nice as it didn't confuse anyone who weren't understanding precisely what they were doing, and can be done much simpler with current ports framework. And was the way what I've proposed.
Click to expand...
I installed it and ran it with the default twm.
But where's the project code? X11R6 and X.org already existed... The source code of the project itself without the dependencies. I think there's nothing and they only changed the former X11R6 file- and package names.
 
I did not insult anyone. I just raised valid questions. What I got in return was at least scottro insulting me. The rest of the comments I didn't read, but I can imagine that they include more insults. That speaks volumes of you lot, and says nothing about me.
 
AlfredoLlaquet, you made a rather sweeping generalization, which, from what else I've seen of what you've written, made it sound as if you were looking for a disagreement.. I should have said "deliberately obtuse" rather than obtuse. It was meant in a friendly way, I'm sorry if you took it as an insult.
 
Yesterday I tried to install Xlibre but it didn't ask me to remove X.org so I decided to not go over cause I didn't have time to dealing with a broken system. Perhaps I'll try again later today, in the afternoon… 🤔
 
kpedersen said:
We should be envious of AIX; it has had Gnome 2.4 for basically a decade. We were the mugs that updated to v3!
Click to expand...
It has a forever false position. The appearance and operation of applications doesn't need to be standardized for anything except commercial software that relies on image/brand.
IBM seems to get it... What's the point of GTK3? Different button click behaviour?
 
kpedersen said:
xlibre has a number of developers working on it (more than most Wayland projects). One of them is stefan11111 who has in the past done some great work at cleaning up fundamental libraries (i.e gtk+2).

Speaking of which, there is even more interest for X11 and Gtk+2 in recent weeks.
Click to expand...
Thanks a lot for that link, really. This way I stumbled upon Pale Moon browser, which is a "saw-off" Mozilla fork, if I may use the expression. And I like it.
 
I think I installed Xlibre but how can I verify I am actually running it? 🤷‍♂️

EDIT:

It looks like I got it! 🦾

1778912661247.png
 
freezr said:
I think I installed Xlibre but how can I verify I am actually running it? 🤷‍♂️
Click to expand...
Just an additional note:
x11-servers/xlibre-server conflicts with x11-servers/xorg-server, thus, cannot install if x11-servers/xorg-server is already installed.

But found an unfortunate fact while comfirming this.
On x11-servers/xorg-server side, conflicts against x11-servers/xlibre-server is NOT made in its ports Makefile, thus, possibly installable even after x11-servers/xlibre-server is installed, causing mangled situation on upgrades.
 
T-Aoki said:
Just an additional note:
x11-servers/xlibre-server conflicts with x11-servers/xorg-server, thus, cannot install if x11-servers/xorg-server is already installed.

But found an unfortunate fact while comfirming this.
On x11-servers/xorg-server side, conflicts against x11-servers/xlibre-server is NOT made in its ports Makefile, thus, possibly installable even after x11-servers/xlibre-server is installed, causing mangled situation on upgrades.
Click to expand...

It looks like my Nvidia doesn't play nicely with Xlibre:

Code: 
cat /var/log/Xorg.0.log | grep WW
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[2026-05-16 08:54:50] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[2026-05-16 08:54:50] (WW) Disabling Keyboard0
[2026-05-16 08:54:50] (WW) Disabling Mouse0
[2026-05-16 08:54:50] (WW) seat-libseat: libseat integration requires -keeptty which was not provided, disabling
[2026-05-16 08:54:51] (WW) LoadModule: If you are using one of the legacy branches of the nvidia proprierary DDX driver (e.g. 470, 390, 340, etc.)
[2026-05-16 08:54:51] (WW) LoadModule: you need to build Xlibre with -Dlegacy_nvidia_padding=true
[2026-05-16 08:54:51] (WW) LoadModule: Otherwise, you will get a segmentation fault due to the abi mismatch between the new X server abi and the one these old drivers are compiled against.
[2026-05-16 08:54:51] (WW) LoadModule: If you are using one of the maintained branches of the nvidia nvidia kernel drivers,
[2026-05-16 08:54:51] (WW) LoadModule: you can try using the in-tree, open-source modesetting DDX driver instead of the proprietary nvidia DDX driver.
[2026-05-16 08:54:51] (WW) LoadModule: Implicitly ignoring abi mismatch for the nvidia proprierary DDX driver
[2026-05-16 08:54:51] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 26.0, need < 25.0).  The driver will continue to load, but may behave strangely.
[2026-05-16 08:54:51] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[2026-05-16 08:54:52] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[2026-05-16 08:54:59] (WW) ProcXkbGetKbdByName() childbuf size (6580) mismatch mrep size (6588 // 1647 units)
[2026-05-16 08:54:59] (WW) ProcXkbGetKbdByName() childbuf size (6580) mismatch mrep size (6588 // 1647 units)

I might consider to revert this setting, luckily I created a BECTL snapshot.
 
You must log in or register to reply here.
Back
Top