GNOME 41 is ~~starting to reach~~ in Arch

[FredBezies]

It was just a small thing I wanted to add. I do not want to go off topic. Gnome since 3.0 is either loved or hated. Sometimes both.

After, Gnome is giving advices. Every person is free to follow them or not. If not, just don’t cry if everything is broken during a Gnome upgrade.

That’s all for me here.

[otherbarry]

@FredBezies

This is official way to manage every single package if you don’t want to destroy your installation in the long run.

Not really.

https://wiki.archlinux.org/title/Arch_User_Repository

Note: The AUR is unsupported, so any packages you install are your responsibility to update, not pacman’s. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.

Back to Gnome 41 stuff …

[freebird54]

Call me when Gnome does something sensible with OK/Cancel and such…

[dalto]

@FredBezies

This is not the ALTERNATIVE way. This is official way to manage every single package if you don’t want to destroy your installation in the long run.

This is simply not true on a variety of levels.

• Installing software from the AUR isn’t considered “The official way” by most people. It certainly isn’t considered “Official” by Arch itself.
• Installing extensions or most other things into a non-system directory such as your home directory should not “destroy your installation”
• It is true that when you install software to system locations such as /usr you should always use a package to do that but that isn’t applicable here.

[pebcak]

@FredBezies

@pebcak

I don’t do my extensions through AUR. I mange them manually myself.

But thanks for pointing out an alternative way.

This is not the ALTERNATIVE way. This is official way to manage every single package if you don’t want to destroy your installation in the long run.

@FredBezies

I prefer to use AUR to manage my extensions. Cleaner and simpler.

[FredBezies]

@dalto

@FredBezies

This is not the ALTERNATIVE way. This is official way to manage every single package if you don’t want to destroy your installation in the long run.

This is simply not true on a variety of levels.

• Installing software from the AUR isn’t considered “The official way” by most people. It certainly isn’t considered “Official” by Arch itself.

It uses the technology developed by Archlinux developers. Moreover, Trusted users are managing AUR contents.

@dalto

• Installing extensions or most other things into a non-system directory such as your home directory should not “destroy your installation”

Only your profiles

@dalto

• It is true that when you install software to system locations such as /usr you should always use a package to do that but that isn’t applicable here.

The exception that proves the rule.

[FredBezies]

@otherbarry

@FredBezies

This is official way to manage every single package if you don’t want to destroy your installation in the long run.

Not really.

https://wiki.archlinux.org/title/Arch_User_Repository

Note: The AUR is unsupported, so any packages you install are your responsibility to update, not pacman’s. If packages in the official repositories are updated, you will need to rebuild any AUR packages that depend on those libraries.

Back to Gnome 41 stuff …

Not official but using native technologies of Archlinux. Which is better than sudo make install installation method.

Besides this Gnome 41 is more an evolution than a revolution.

[dalto]

@FredBezies

Which is better than sudo make install installation method.

Nobody is talking about using sudo make install. We are talking about installing extensions into the proper locations in your home directory which is both supported and recommended.

If you prefer to use AUR packages to maintain your extensions that is certainly a good and valid choice. However, it doesn’t mean that someone who chooses a different path is wrong or doing something unsupported.

[otherbarry]

@FredBezies

Which is better than sudo make install installation method.

Nobody suggested that.

We are talking about a method inbuilt into the DE and suggested for use by the developers of that DE.

Oranges and Apples.

[ricklinux]

Just do KDE problem solved!

[Christopher67]

What are the top 3 Gnome Extensions, asking for a friend.

[gideon]

Extensions are placed in ~home/.local/ share/Gnome-shell/extensions in a folder the name of the extension. they are not installed just read that is the correct way that can not harm your setup in any way.

@Christopher67 the top 3 are kill KDE, kill KDE, kill KDE,

[ricklinux]

Kill KDE? I just got all kinds of updates again. Rolling perfection!

[Scotty_Trees]

Looks like Gnome 41 is officially here now in the stable repos. Thanks to anyone that tried it out in Testing to get it to this point. *note gnome-backgrounds is still out-of-date, but more than likely that’ll probably change, I may have just checked for updates too quickly

[scott@endeavourOS ~]$ checkupdates; yay -Qua
adwaita-icon-theme 40.1.1-1 -> 41.0-1
at-spi2-core 2.40.3-1 -> 2.42.0-1
cheese 3.38.0-1 -> 41.0-1
epiphany 40.3-1 -> 41.0-1
evince 40.4-1 -> 41.2-1
evolution 3.40.4-1 -> 3.42.1-1
evolution-data-server 3.40.4-1 -> 3.42.1-1
folks 0.14-5 -> 0.15.3+6+gdb1de866-1
gcr 3.40.0-1 -> 3.41.0-1
gjs 2:1.68.3-2 -> 2:1.70.0-1
gnome-boxes 40.3-1 -> 41.1-1
gnome-calculator 40.1-1 -> 41.0-1
gnome-calendar 40.2-1 -> 41.1-1
gnome-contacts 40.0-1 -> 41.0-2
gnome-control-center 40.0-1 -> 41.1-1
gnome-desktop 1:40.4-1 -> 1:41.1-1
gnome-maps 40.4-1 -> 41.1-2
gnome-music 1:40.1.1-1 -> 1:41.0-1
gnome-remote-desktop 40.1-1 -> 41.1-1
gnome-settings-daemon 40.0.1-2 -> 41.0-1
gnome-shell 1:40.5-1 -> 1:41.1-1
gnome-shell-extensions 40.4-1 -> 41.0-1
gnome-system-monitor 40.1-1 -> 41.0-1
gnome-user-docs 40.4-1 -> 41.0-1
gnupg 2.2.29-1 -> 2.2.32-1
jre-openjdk 17.u35-1 -> 17.0.1.u12-1
jre-openjdk-headless 17.u35-1 -> 17.0.1.u12-1
libdrm 2.4.107-1 -> 2.4.108-1
libevdev 1.11.0-1 -> 1.12.0-1
libnautilus-extension 40.2+7+g67c7bdbf8-1 -> 41.1-1
libytnef 1:1.9.3-1 -> 1:2.0-2
mutter 40.5-1 -> 41.1-1
nautilus 40.2+7+g67c7bdbf8-1 -> 41.1-1
opencv 4.5.4-5 -> 4.5.4-6
orca 40.0-1 -> 41.0-1
pinentry 1.1.1-1 -> 1.2.0-1
sushi 3.38.1-1 -> 41.0-1
vivaldi 4.3.2439.63-1 -> 4.3.2439.65-1
welcome 3.16.10-1 -> 3.16.11-1
xdg-desktop-portal-gtk 1.10.0-1 -> 1.10.0-2
xf86-input-libinput 1.2.0-1 -> 1.2.0-2
xf86-video-fbdev 0.5.0-2 -> 0.5.0-3
xf86-video-intel 1:2.99.917+916+g31486f40-1 -> 1:2.99.917+916+g31486f40-2
xf86-video-vesa 2.5.0-1 -> 2.5.0-2
xorg-server 1.20.13-3 -> 21.1.1-2
xorg-server-common 1.20.13-3 -> 21.1.1-2
yelp 40.3-1 -> 41.1-1

In case you have a very keen eye, you’ll notice Gnome gdm is absent from my checkupdates. This is because per the EndeavourOS wiki to get optimus manager working (click here), I had to install a package called gdm-prime from the AUR that is patched to make the optimus manager work. No clue if I can update safely or not until that package is updated, so I’m gonna wait a couple more days and see.

Edit: gnome-backgrounds has just been updated, so all of the Gnome 41 packages are fully up to date on Arch now! And working quite well might I add. This has been the smoothest Gnome upgrade I’ve ever done.

[jonathon]

Interestingly, I found that GNOME automatically offloaded 3D applications to my dGPU - no need for prime-run or anything else.

[Rockwallaby]

So far so good for me… I don’t run a lot of extensions though

[ricklinux]

Gnome 41 landed on my desktop?

[Scotty_Trees]

Should’ve used KDE

[Zircon34]

@ricklinux

Gnome 41 landed on my desktop?

but you hate gnome?! Love it now?

In the meantime I installed kde

[keithy]

Disabling the extension version validation check brings much relief with non working extensions

dconf write /org/gnome/shell/disable-extension-version-validation true

Until the extension really becomes incompatible of course

HTH