no need to reinstall if the system is installed just `rpm-ostree update`
no need to reinstall if the system is installed just
rpm-ostree update
RNo upgrade available
Rbazzite-deck-gnome:latest
RNvm, it probably is OK now.
RMy mistake, sorry.
Hi started looking around in the container files to see the actual flow to see if i missed something XD
is it updating now?
is it updating now?
RIt seems to have updated itself when Gamescope was booting for the first time.
Rdistrobox.ini is present now on fs
Hnice
Hyeah i moved it to be part of the ujust rpm instead
RSrcpy installation (that's what fedora distrobox is needed for from what I'm seeing) now passed successfully
Hgood good 
RFedora distrobox has been created
RThank you for the quick response 
Hnp, im sorry that it happened to begin with
Aso, how can i get my cpu to show up vga controller inxi -G only dgpu showing up
YSO I REINSTALLED BAZZITE RIGHT?!
YThe new splash screen is DOPE! Also noticed the desktop scales correctly I a fresh install or at least looked like it
YI keep trying things just to end up back on bazzite
JThis is a weird bug.. During XIV launcher setup one of the steps is giving it the launch options of
XL_SECRET_PROVIDER=FILE %command% run --parent-expose-pids --parent-share-pids --parent-pid=1 --branch=stable --arch=x86_64 --command=xivlauncher dev.goats.xivlauncher And that works super well on base steamOS but on bazzite it fails to open unless you remove --parent-expose-pids --parent-share-pids --parent-pid=1
Tthose arguments are from flatpak itself and not XIVlauncher
See also https://docs.flatpak.org/en/latest/flatpak-command-reference.html
The question is whether XIVLauncher on Bazzite communicates with Steam to report that the game has closed without them
Q: Final Fantasy XIV doesn’t close properly / Steam constantly thinks Final Fantasy XIV is playing
Make sure you set the Launch Options in the “Add a Non-Steam Game” step. Specifically the --parent-expose-pids --parent-share-pids --parent-pid=1 arguments allow XIVLauncher to communicate with Steam to report the game closing.
via https://goatcorp.github.io/faq/steamdeck.html
See also https://docs.flatpak.org/en/latest/flatpak-command-reference.html
The question is whether XIVLauncher on Bazzite communicates with Steam to report that the game has closed without them
Jit doesnt
Jsadly
JYou get stuck with the trial running and unable to tell it that its really closed
TMaybe the PID just needs to be changed to something appropriate. Can’t tell you what that is though.
Aso its not possible but my cpu is coffee lake
KIt's the same for me on my AMD Ryzen 5600G
Konly my dgpu is visible. I assume something is disabling the igpu (to save pci-e lanes maybe?)
Kmost desktops do this
Ksince there's no reason to keep the igpu in that form factor
Aodd, cuz i need plug my second monitor but i dont want to plug to dgpu its bad for me
KI mean, what if I wanted to dGPU for Linux desktop, and use my 6700XT for Windows VM games? (I don't, but it's a use I could see)
Ayep you right its my motherboard disables my integrated gpu due to this Integrated video is not available if a graphics card is installed. why this is a thing.
Ai saw it on their website of my motherboard im usin
Ahow fun
BIs there a command to change gamescope (deck's gamemode) resolution, say I wanted 16:9 aspect for compatibility with moonlight on my TV?
Kit uses the native res of your display, you can change the res per-game though
BI do for many games already, but sunshine seems to capture my whole wayland session (800p deck screen) instead of whatever res i set for a game (which gamescope does use). So for 16:9 apps like Kodi, i have a high res downscaled box with bars on all 4 sides
SHow does dual booting work btw do I have to go into bios to change OS?
C-Folks, she wants me to format her laptop and install a distro, is she the one?
+Bazzite please!
+Bazzite please!
CMy evangelizing is working
SDepends. Bazzite’s Grub picked up my other Distro most of the time and I could just select it on the boot screen. Other times I’d have to pick it as a boot device on start up.
TUpon further consideration, I’m questioning those arguments in general because they’re related to flatpak patent processes
Jhmmm
TI ran the full flatpak command in the terminal and got a bwrap error that then sent me in a rabbit trail of people asking why that’s set on GitHub
TI have to pause this for now though
J
thanks for looking into itCInspector Term on duty, well, now on break but you get the idea
TGitHub
From Alicia on Discord: On arch, I'm suddenly getting a really weird issue where the launcher fails to start when using the recommended launch options for steam. Launch options: LD_PRELOAD=&quo...
J
I should have checked there first. Thanks!!