could also been a plasma update or something inbetween that changed too
could also been a plasma update or something inbetween that changed too
Hdone
NYeah tested reverting from Steam Families beta to normal and that fixes it. Gotta have families but assume it'll get fixed later
RSeems that I can't send this up to dri-devel, not sure why.
RIn the meanwhile, @Kyle Gospo
Re0EQVvP.eml2.09KB
EI installed bazzite-nvidia, but then upgraded to an AMD card. Everything is working well, but I still get package updates for nvidia stuff which makes me wonder if I missed an important step. How can I get rid of the nvidia pieces?
Krpm-ostree statusand then:
Krpm-ostree rebase url_hereminus the
-nvidiatoss your status here for a working example
RLiterally sent up 4 times, no bounce back but nothing on the mailing list itself.
RNo clue.
KMario's on vacation but whe he's back maybe we can ask for help again
KYou in the Linux dev discord?
RNope, there is one? XD
Kyep, I'll get you an invite
EState: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
Digest: sha256:73dabc6ac45bc2c2c8e3b5c04ea33a48d7b15bfae7972f757125a4d461f46b12
Version: 40.20240621.0 (2024-06-21T05:11:41Z)
LayeredPackages: podman-compose sunshine
ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
Digest: sha256:73dabc6ac45bc2c2c8e3b5c04ea33a48d7b15bfae7972f757125a4d461f46b12
Version: 40.20240621.0 (2024-06-21T05:11:41Z)
LayeredPackages: sunshine
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:2bd8d399e60fd24b3d8b3e3ac5dce742f2cc56d8f60d808428ed57454bf6a3c9
Version: 40.20240607.0 (2024-06-07T17:01:41Z)
LayeredPackages: sunshine
Pinned: yes
I don't know why two are unverified and one is a signed docker image. That seems strange.
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
Digest: sha256:73dabc6ac45bc2c2c8e3b5c04ea33a48d7b15bfae7972f757125a4d461f46b12
Version: 40.20240621.0 (2024-06-21T05:11:41Z)
LayeredPackages: podman-compose sunshine
ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
Digest: sha256:73dabc6ac45bc2c2c8e3b5c04ea33a48d7b15bfae7972f757125a4d461f46b12
Version: 40.20240621.0 (2024-06-21T05:11:41Z)
LayeredPackages: sunshine
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
Digest: sha256:2bd8d399e60fd24b3d8b3e3ac5dce742f2cc56d8f60d808428ed57454bf6a3c9
Version: 40.20240607.0 (2024-06-07T17:01:41Z)
LayeredPackages: sunshine
Pinned: yes
I don't know why two are unverified and one is a signed docker image. That seems strange.
Hthey are unverified because you probably did a rebase and snagged the command from https://bazzite.gg which is meant for when you rebase from fedora kinoite/silverblue
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
Eyeah, that tracks. I'm pretty sure that's exactly what I did. So what rebase should I do now to straighten it out?
Rrpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stableyep
ENot quite good:
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature
Ryou can unpin your nvidia one with
sudo ostree admin pin --unpin (deploy number)oh your image is quite old then, see https://discord.com/channels/1072614816579063828/1074438180847239279/1257854077048721520
KAlready off nvidia
KYou might be seeing the flatpaks at most
RI rembered now that in order to unpin it's needed to pin --unpin 
Hpin --unpin --repin --respinnow that would be a cursed command
Amaybe leftover yum repo?
Edoes Discover pull down updates for all the pinned images? I often see duplicate app updates there.
KNo, but you may just have duplicate apps
KOr otherwise apps depending on similar SDKs
EI have two instances of Discord in the list for instance. As far as I can tell its the same exact app.
Kflatpak list | grep discordWhat do you see?
EDiscord com.discordapp.Discord 0.0.61 stable flathub system
Discord com.discordapp.Discord 0.0.61 stable flathub user
Discord com.discordapp.Discord 0.0.61 stable flathub user
Eit seems I installed it both as a user app and a system app
Eno idea how
KYeah you just have duplicate apps, delete user apps
Kiirc Kyle wanted to remove the user repo
KFor that reason I presume
Aafaik is the reason some flatpak only works correctly as system flatpak
Eit looks like I have a lot of things that are installed as both user and system and I have no idea why. Like Freedesktop Platform.
Kduplicate dependencies are normal
KThat one makes sense because its a dependency
Eso I shouldn't uninstall those?
EI'm coming from Ubuntu so a lot of these concepts are a little unfamiliar, but welcome.
KIf your plan is to uninstall every user flatpak, than you should uninstall those
