Skip to main content ↑ ↓
Topic: X.Org is being forked, huge drama brewing... (Read 14612 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: X.Org is being forked, huge drama brewing...

Reply #60 –
Quote from: Artist – on
The xlibre-server package has been updated with the fix for the startup problem with Qt programs.
Am I missing where this should be or is it still internal? I would like to be a guinea pig.
 

Re: X.Org is being forked, huge drama brewing...

Reply #61 –
Quote from: Wirlaburla – on
Quote from: Artist – on
The xlibre-server package has been updated with the fix for the startup problem with Qt programs.
Am I missing where this should be or is it still internal? I would like to be a guinea pig.

You can try, at your own risk and unsupported of course, by temporarily adding repository galaxy-goblins to your pacman.conf file and installing package xlibre-server. This will show an instruction when finished.

Normally no goblins (Staging) repository should ever be enabled as this will break your system: https://wiki.artixlinux.org/Main/Repositories#Staging

artist

Re: X.Org is being forked, huge drama brewing...

Reply #64 –
IMPORTANT: xlibre has been updated and now has version 21.1.13. This is lower than the previous version so it needs to be installed explicitly again using pacman.

artist

Re: X.Org is being forked, huge drama brewing...

Reply #65 –
I was just browsing (probably for the first time ever), for fun, the Xorg website. The latest "news" is from 2013. The latest press release is from 2015. But the board of directors is alive and active (last meeting 2 June, before the fork drama). The board secretary works for Red Hat. Looking at their minutes, all they ever talk about is
- funding/sponsors
- the next board election
- organizing the next XDC (where all things wayland shall be discussed)

Re: X.Org is being forked, huge drama brewing...

Reply #66 –
Quote from: dpx – on
Quote from: mrbrklyn – on
From the perspective that you explained, yes that is true.  That is just one possible future route.  What I am saying is that there is a very large X user base that would be willing to just fork GTK5 to allow for it to work on X ***or*** it might well just be not relevant in 2035, long after I am dead and when you can expect to see GTK5 because the hardware and underlining Human Interface Design is changing so fast.  A Mouse, Screen and Keyboard... how quaint of an idea that will be.

If you read what I said before in this thread you may see that I also hope people to fork when needed and expect X to exist long after you are dead. But I also remember how quickly systemd was adopted almost everywhere after corporate started to push, and would rather consider options and possible action rather than counting on hope.

You can't deny it is getting increasingly harder to remove all traces of wayland, like you noticed in another thread. I don't like it one bit but I would rather know my options if and before lock in gets firmer.

Of course I am talking about one possible route and only in my name, how else it can be?


make x great again

Re: X.Org is being forked, huge drama brewing...

Reply #67 –
The xlibre xf86 driver pkgs have been updated. Some might have a lower version, so a manual check and reinstall is needed then.

artist

Re: X.Org is being forked, huge drama brewing...

Reply #68 –
Modesetting driver here finally got TearFree option.
And it's enabled by default.  ;)

Re: X.Org is being forked, huge drama brewing...

Reply #69 –
Quote from: darcy – on
Modesetting driver here finally got TearFree option.
And it's enabled by default.  ;)

Remember how wayland was needed because they couldn't fix tearing on X? If you are testing XLibre please occasionally drop few impressions.

Re: X.Org is being forked, huge drama brewing...

Reply #70 –
Can't say I'm testing it, just installed it to my old laptop out of curiosity.
Usual stuff like alacritty, chromium/firefox, thunar, mpv, some other GTK and Qt apps work as usual.
TearFree seems to work fine as well - no tearing in videos and while moving app windows whatsoever.
Haven't tried DEs and login managers though. I'm using dwm with startx.

And yeah, it's running on Intel Celeron B820 (Sandy Bridge) with Intel HD Graphics.

Re: X.Org is being forked, huge drama brewing...

Reply #71 –
Quote from: darcy – on
I'm using dwm with startx.

Is there something else than dwm and startx? That's all I need too. 😎

Re: X.Org is being forked, huge drama brewing...

Reply #72 –
This now appears to work OK with the Nvidia blob (I know, I'm a terrible person) with this PR.
https://github.com/X11Libre/xserver/pull/89
https://patch-diff.githubusercontent.com/raw/X11Libre/xserver/pull/89.diff

I needed to pass the option -ignoreABI or the nvidia driver complains and exits X.
For example:
Code: [Select]
startx -- -keeptty -ignoreABI >~/.local/share/xorg/xorg.log 2>&1

Early days but I haven't noticed any problems yet.

Re: X.Org is being forked, huge drama brewing...

Reply #73 –
So I see xlibre-server is now in [omniverse], but
Code: [Select]
# pacman -S xlibre-server
resolving dependencies...
warning: cannot resolve "xlibre-xf86-input-libinput", a dependency of "xlibre-server"
Why is it there if all the components it depends on aren't?

Also, should we have a new thread for Xlibre testing experiences?

Re: X.Org is being forked, huge drama brewing...

Reply #74 –
xlibre was not supposed to be in omniverse; pacman -Sy should fix that now.
So far there was only one issue, Qt apps not starting, which was fixed last Sunday.

artist