Arch Linux 2024

The place to discuss Linux and Unix Operating Systems
Forum rules
Behave
Post Reply
User avatar
Zema Bus
Your Co-Host
Posts: 1955
Joined: Sun Feb 04, 2024 1:25 am
Location: Arizona

Re: Arch Linux 2024

Post by Zema Bus »

At this point which would you say is the more difficult one to deal with, Arch or Manjaro updates? :)
User avatar
Grogan
Your Host
Posts: 3211
Joined: Sat Aug 21, 2021 10:04 am
Location: Ontario, Canada

Re: Arch Linux 2024

Post by Grogan »

Well, Manjaro updates are Arch updates, but delayed. Most of Manjaro is just their own PKGBUILDs that follow Arch. So in Manjaro, if I was following their updates, I'd simply have a lot more rubbish to deal with at once, rather than something stupid to piss me off every day.

I just need to have things normal, I don't want my image libraries loading in bubblewrap containers set up by systemd. Gnome and systemd can fuck all the way off. I just want to use the GTK+3 environment.

It's the distro trying to keep the system Gnome compatible that's the problem here.
User avatar
Grogan
Your Host
Posts: 3211
Joined: Sat Aug 21, 2021 10:04 am
Location: Ontario, Canada

Re: Arch Linux 2024

Post by Grogan »

It looks like Arch fixed this:

https://gitlab.archlinux.org/archlinux/ ... 49e51f103f
GdkPixbuf-WARNING **: 11:51:10.109: Error loading XPM image loader: Image type “legacy-xpm” is not supported

Apparently was removed from gdk-pixbuf, moved to glycin, but glycin implementation is incapable of handling "gdk_pixbuf_new_from_xpm_data" thus returned to pixbuf and disabled by default
These two things, a cherry pick "patch" and enabling legacy_xpm. This was also broken with glycin too, not only for me.
# Unbreak gdk_pixbuf_new_from_xpm_data
# https://gitlab.archlinux.org/archlinux/ ... k_items/13
git cherry-pick -n 62b8f9fd0bb3b862823cd34afce4b389fbd27569

-D legacy_xpm=enabled
That's it for me though, I'll be maintaining gdk-pixbuf2 myself from now on. I'm not having that bollocks.
User avatar
Zema Bus
Your Co-Host
Posts: 1955
Joined: Sun Feb 04, 2024 1:25 am
Location: Arizona

Re: Arch Linux 2024

Post by Zema Bus »

This sounds like what happened in the CachyOS forums.

User avatar
Grogan
Your Host
Posts: 3211
Joined: Sat Aug 21, 2021 10:04 am
Location: Ontario, Canada

Re: Arch Linux 2024

Post by Grogan »

What a bunch of fuckweasels. XLibre is an alternative that plenty of people will like to use, once Xorg X11 stops being viable. I have no reason to now, but hope that fork sees some contributions between now and then. I don't think one guy would be able to maintain it for very long, once things get out of whack. I see XLibre shunned by some people (e.g. chimps at Phoronix) because they want everything to be Wayland. There could be some of that going on here, it really doesn't make sense.

Telling subreddit moderators to censor people talking about age verification too. Fuck them... I'm not having that, as a matter of principle.
User avatar
Grogan
Your Host
Posts: 3211
Joined: Sat Aug 21, 2021 10:04 am
Location: Ontario, Canada

Re: Arch Linux 2024

Post by Grogan »

So, earlier in the week Arch upgraded wayland, but not lib32-wayland. It is not possible to compile lib32-mesa in that situation, because it's the wrong version of wayland-scanner (64 bit, common between). I had to fix it (compile lib32-wayland 1.25... I was just using the distro package for the lib32) but they STILL have not fixed that. See, they wouldn't care because they don't need to compile mesa, yet (they are still on mesa-26.0.5 and they probably won't be doing another until 26.1.1). They don't care about anything but the distro packages they distribute. There's no way I'd leave that broken for 4 days if it were my distro. It especially irks me, because I don't even use Wayland, but it's a system dependency.

I'm on the 26.1 branch, currently mesa 26.1.0-rc2.221275.9445e5d0a6c as of a few minutes ago. It's shaping up to be pretty good.
Post Reply