new build available with the fix for `distrobox-assemble`, sorry for the inconvenience with it
new build available with the fix for
distrobox-assemble, sorry for the inconvenience with it
AThats funny
Adont you hate when your cpu wont show igpu in inxi -G Just only dgpu shows quite annoying what if i want use another monitor lol
Tthen plug in another monitor to the dGPU
Athats bad idea if i did it would use resources of dm again so, i prefer igpu for that solution
Tresources of dm?
Adesktop manager its already using 2gb of vram of my dgpu so its not good idea is it.
Tdo you only have 3GB of VRAM?
A8gb max
Tyou're fine
Ayou arent fine if u palying games
Asome games uses almost all of my vram so i need help with igpu situtation
TI briefly ran a 3070ti with a 1440p ultrawide and a 1440p standard wide. you're fine
Ahow much vram
T8GB
Hwell to my understanding of how the different image layers work it should be fixed 
RI'll reinstall from scratch and report if I encounter any other issues.
Hno need to reinstall if the system is installed just
rpm-ostree updateNo 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=1those 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)
