Skip to content
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

Unable to enable NVIDIA driver after upgrade to F41 #666

Open
rocketship-pancake opened this issue Oct 30, 2024 · 2 comments
Open

Unable to enable NVIDIA driver after upgrade to F41 #666

rocketship-pancake opened this issue Oct 30, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@rocketship-pancake
Copy link

Describe the bug

After bluefin-dx-nvidia:latest upgraded to Fedora 41 I get a notification from Software to enable NVIDIA Graphics Driver. When I go through with the process (it is simple and takes just few mouse clicks) I get an error and fail to enable NVIDIA Driver.

Failed to prepare reboot

Detailed errors from the package manager follow:
Error accessing /usr/libexec/gnome-software-dkms-helper: No such file or directory

What did you expect to happen?

Expected to enable NVIDIA Drivers.

Output of rpm-ostree status

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 5min ago
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Digest: sha256:a56a28f9afbcd933a9e342cc3860de6ce92c29e4f7ff2a6db5356aebe3f319c9
Version: 41.20241030.0 (2024-10-30T04:44:46Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Digest: sha256:9605c4dfe032733e47d5ac47bc278f98af6593a6c72bb51b7df82a9de2d2e87b
Version: 41.20241029.0 (2024-10-29T23:11:04Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:latest
Digest: sha256:66e43a5bd69b0e95c5fbed757c60b72bcd50e01dcb843cdab081ddeb869f62f3
Version: 40.20241027.0 (2024-10-29T01:22:40Z)
Pinned: yes

Output of groups

rocketship wheel docker

Extra information or context

Screenshots:
https://imgur.com/a/9qJuxAh

@dosubot dosubot bot added the bug Something isn't working label Oct 30, 2024
@castrojo
Copy link
Member

We do this automatically and turned off the notification (or thought we did). You're on the right image there's no need to do this, but we should ensure you never see the notification.

@m2Giles
Copy link
Member

m2Giles commented Oct 31, 2024

Can we move this to main? We need to figure out why the notification prompted even though the binary was removed.

@castrojo castrojo transferred this issue from ublue-os/bluefin Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants