-
Notifications
You must be signed in to change notification settings - Fork 70
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
Application does not work with GNOME 41 #294
Comments
We have several issues open about Arch and Arch-based distros (and their kernel versions) already: If the issue being reported here is regarding the GNOME Shell extension, its repository is https://github.com/pop-os/gnome-shell-extension-system76-power. |
I saw those other issues but the errors were different. I filed this against system76-power as the issue is with the main application not really the extension. There is a branch that I made for adding GNOME 41 to the metadata.json file. |
Sounds like the Arch packaging is just outdated, and lacks the service file containing |
It looks like it has that in the
At least in this version in the AUR |
You could try installing system76-power from the |
So running these commands are still needed as of testing today with GNOME 41.5:
I haven't been able to build the AUR package using the |
@ahoneybun I had this issue in 22.04 (beta)
and was solved applying the same commands. |
Distribution (run
cat /etc/os-release
):Related Application and/or Package Version (run
apt policy $PACKAGE NAME
):pacman -Qs system76-power local/gnome-shell-extension-system76-power-git 2.0.2.r0.ga901dc0-1 Gnome shell extension for System76 power management local/system76-power 1.1.19-1 System76 Power Management
Issue/Bug Description:
Not able to use the
system76-power
package in Arch with GNOME 41 and it seems to happen in Fedora 35 as well.Steps to reproduce (if you know):
system-power
andgnome-shell-extension-system76-power
Expected behavior:
Able to switch modes and profiles
Other Notes:
If you start the systemd service you are able to use the CLI but not the extension. This is the message you see when you try to use the CLI or enable the extension when you boot before starting the service:
The text was updated successfully, but these errors were encountered: