-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AGS (Aylurs GTK Shell) v2 breaks AGS overview #488
Comments
There are no some workarounds for this issue, until the code can be updated For NixOS users:
Then rebuild Remove your current AGS installation. You can install an older version on the side and keep the new one, but that comes witht he hassle of redirecting your keybinds to the old one. yay or paru -R aylurs-gtk-shell (aylurs-gtk-shell is AGS in case anyone didnt know, AGS in AUR is a game engine apparently) go to the git page and download version 1.8.2 zip or tarball https://github.com/Aylur/ags/releases unpack it and place it wherever you want to build from. open a terminal window and CD into the build folder and then into the unzipped AGS folder. Then copy and paste the build instructions below and voila your AGS is back to normal npm install if anyone wants to see the build instructions on the AGS wiki the link to the page is below, build instructions at the bottom. https://aylur.github.io/ags-docs/config/installation/#from-source (edited) As of this announcement AGS is still at v1.8.2 https://docs.fedoraproject.org/en-US/quick-docs/dnf/#exclude-package The covers how to add an exclusion to DNF to prevent AGS from being updated The package name is: aylurs-gtk-shell
Add |
Distro-Hyprland install scripts have been updated to install from Source (Aylurs GtK shell v1.8.2) so that AGS overview will still work |
Arch User Solutions Go Back v1.8.2 |
This is just to inform you that with the new ags (aylurs-gtk-shell) breaks the AGS overview
JaKooLit/Arch-Hyprland#173
I dont have immediate plan atm as I am outside country
target for fixing would be by end of December or even Jan 2025 once im at home
The text was updated successfully, but these errors were encountered: