A@HikariKnight do not ack
Alet it run
H
Tabsolutely proprietary
Asounds like a skill issue tbh
A(im very aware and very salty about it)
Ai added a cleanup commit that fixes some stuff but id rather let the current one finish first
Aif this finishes we rerun and its ready for merge
Aguess it would be good if someone rebases to it on the deck image as well
Abefore merging
NMinor question, if this is the wrong channel just let me know. Noticed lately my steam will launch from the icon in KDE but makes its own seperate icon like this. Didnt do it before my last update, there a fix?
N
TThis happens to me with Thunderbird flatpak whenever I used KDE
Hbecause the shortcut doesnt actually start steam, it is a bash script that starts steam correctly based on which image you are on as a separate process
Hbecause if you are on a handheld/htpc image, steam must be started with
-steamdeck while on desktop you do not want thatHthere is also a bunch of other things it does too
NI'm on desktop image
Tyea this is a plasma issue but im not sure how to reproduce it
N
NJust forcing scaling but nothing else in the launch opts
Hyeah but
see
bazzite-steam is not actually steam, it is a script that applies some image specific fixes to steamsee
cat /usr/bin/bazzite-steamAgodamn it downloading ge's tarball died
Hessentially the one pinned in the taskbar is not steam it just launches steam with some minor changes
NSo what exactly would I need to edit in that script to get it back under the proper icon?
Hif it worked before, need to wait for a steam update (steam package update, not steam client update) to fix it
NRoger, thanks
Hcould 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 status, grab the URL of your imageKand then:
Krpm-ostree rebase url_hereKminus the
-nvidia partKtoss 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:stable and you're goodHyep
