@jessica my two favorite colors

@kayden quick, catch it before it turns blue and disappears

@cancel@merveilles.town it's too late, dbus already crashed and took my entire session with it

@kayden the year of the linux desktop was over a decade ago, we just need to return.
(half joking, but I can't deny that I want a desktop that feels like what I imagine these images to be like from time to time)

@kayden soul

@Yoshi @kayden I've been using Linux for 23 years. I would say Linux as a desktop peaked around 2008.

@Yoshi @kayden In terms of reliability, I would say right now it's about as bad as it was in 2001 or 2002. If it gets worse, it will actually have regressed to worse than when I started using it in 1999.

@cancel @kayden yea I've heard from many people on the internet that the late 2000s was the peak of the desktop. not nearly old enough nor knowledgeable enough to know how it was back then, though. how exactly was the readability? what faults did it have? what did 2008 have right?

@Yoshi @kayden Some people poured a bunch of money and effort into Ubuntu, which was reliable and easy to use in its first few releases.

IBM had only recently sold its ThinkPad division to Lenovo. It would take a few more years for the effects of that to set in. Until then, there were lots of reliable and high-quality laptops still on the market.

Apple had only recently started to make computers that were price-competitive, and the effects weren't visible yet.

@Yoshi @kayden

Software that only ran in web browsers was niche.

Android and iOS barely existed. (iOS was still called iPhone Firmware.)

@Yoshi@wetdry.world @kayden@fedi.nullob.si the good ol' days

@kayden @cancel the year of the Linux NULL is SYMBOL_NOT_FOUND

@poorpocketsmcnewhold It's the same icon set. It's caused by an *intentional* breakage from the GNOME project, and also from Arch Linux's packaging system and maintainers not caring.

@cancel Expected from GNOME, breaking customizations. Shame for your lxde setup. :/

@poorpocketsmcnewhold Installing oxygen icon pack, setting it, then relogging gives me working icons again. But there went 35 minutes of my life.

@cancel What intentional breakage?

@fabiscafe https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/177

@cancel So this?
https://gitlab.gnome.org/GNOME/gtk/-/issues/4754

Is there still something missing? If yes do you have reported it?

@fabiscafe It's already reported. I just linked you to someone else reporting it. They closed it and said it was intentional and not a problem.

@cancel It's also already fixed. Still, if you're missing something make sure that you report it and test.

@fabiscafe It's not fixed. Read it. I don't need to report it. Stop telling me to report it.

@cancel
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4558
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4562
Both are merged, both provide the fix for yours, as well as the moved dup
https://gitlab.gnome.org/GNOME/gtk/-/issues/4754

Everything else is either a misusage of GNOME icons or a not yet fixed (set of) icon(s), someone should report, if not already done.

@fabiscafe Are you a GNOME contributor? I'm guessing your goal is to lead from "Everything else is either a misusage of GNOME ..." and into "well this was some other software's fault for using the icons"

@cancel
I'm in fact a contributor to GNOME in 42. I wrote a meson fix for gnome-music :) I'm also the builder behind the gnome-unstable repo for Arch (FCGU). I'm pretty active in the opensource space in general over the last 15years.
My goal is the clear this up a bit, so back to topic:

Sort of both. A lot of icons where removed who were GTK-relevant icons and they came back with the linked MR.
For GNOME icons, they are not supposed to be used by "3rd party apps" and since they are now shipped with the apps, not anymore as an icon theme, apps who where usingh them don't have them available anymore for this reason.

@fabiscafe This is LXQt that is broken on Arch. The icons were supplied by adwaita-icon-theme, which was chosen as the default icon theme by LXQt after installing the lxqt group in Arch and starting the desktop environment. If the icons aren't meant to be used, they shouldn't show up as an option or be chosen by default by software.

@cancel I can't find anything about LXQt to pull in an own icon theme somewhere, except for 'hicolor-icon-theme'. So it might be a GTK app that pulls in adwaita-icon-theme. So yes, I'm with you. LXQt should pull in another icon theme that provides the icons it uses [Arch side] or shipp them by themself [LXQt side].
I think for Arch this will end up as upstream bug, as they do not define defaults themself, so it might be the best idea to start talking to LXQt.

@fabiscafe You're right that LXQt should specify some icon theme to rely on.

But why is the adwaita icon theme even showing up as a choice, if it's not supposed to be used? Even if LXQt installed oxygen or breeze icons, the adwaita icons would still show up as a choice.

@cancel I think thats because Adwaita still is used as symbolics provider for GTK apps as well as for apps who are not ported, like evolution. GTK apps do not start if some icons are not there, so a simple rename might also not be possible, but I'm not sure about that (so please correct me here)