OSuppose one has an iGPU and dGPU, both AMD, and wants to make a particular flatpak use the dGPU. How would they go about that?
ACool, thanks :3
Hswitcherooctl launch --gpu=1 /path/to/executableyou can get the gpu indexes from
switcherooctl listso you can just replace the executable to the flatpak command
KNo need to specify the GPU
KSwitcheroo will always default to the marked dedicated
KYou can also right click on the desktop shortcut and launch on dedicated
Oso does that mean always launching it with switcheroo or does that get saved somehow?
WIf you on KDE you can do it in the UI and tell it to use the dedicated GPU. Right click on the app in the menu "Edit Application" >> Application Tab >> Advanced Options >> Run using dedicated graphics card
Hoh didnt know about this
Othat's probably the solution I'm looking for, thanks!
KIt's all switcheroo all the way down
CDid this change at some point?
Used to be base (do not use) -> main (use like upstream) -> featured/custom bazzite/bluefin/aurora/etc
Used to be base (do not use) -> main (use like upstream) -> featured/custom bazzite/bluefin/aurora/etc
KNo distinction between base and main
KWe don't recommend them to anyone except those making custom images from them
Co.0 huh
Cthat definitely is new
Hpeople can use them, but we do not recommend it because they are not our focus past being as close to normal silverblue/kinoite/atomic as possible
CHmmm
Hits been like that for some months now from my understanding
KRight, you're not going to get pre-installed flatpaks, you still have RPM Firefox, and at the end of the day our product is not Fedora but slightly better
KThat decision is I think over 6 months old now
KIt's also why the new website doesn't strongly emphasize their existence, and why we don't offer isos for them
KJust something we don't want normal users to be using as a desktop under any circumstance
CAh. I have been somewhat out of the loop
Hnp it happens when youre busy
CNot really even busy tbh
Hthe base images are more of a byproduct from what we actually make
CJust.. unable to contribute to ISO development, which was 95% of the effort around here for a long time, and unable to do much else since my other contributions have either been implemented or rejected
Jthat raid boss was slain
Jmostly just waiting for the efficient downloads, everything else is basically done
CYeah. The 'batteries included' bit which made a big difference initially compared to upstream Silverblue/Kinoite/etc was done a very long time ago
Tbasically its a support thing. nobody is going to add major changes to the base images because thats what bluefin, aurora, and bazzite are for now
CI see
Dwho was working on sound with the steamdeck oled on the newer kernel?
Lmy taskbar keeps resetting itself 
Levery time i reboot my task manager is back to how bazzite has it out of the box
Lthats really annoying
Levery other thing about the taskbar stays the way i configured it
Lexcept for the task manager
CI suppose, between that and the snippets I've seen while checking in here occasionally to skim, it makes sense to de-emphasize the base images, for branding and marketing purposes. If the same things 'just work' on every version, then in my experience the people who want an upstream-like experience will probably loudly say so, and the featured/custom images would be what actually draw people to the project.
Jyeah people who want an upstream experience usually know how to linux already
VBecause this was here
WWhat setting are you changing that keeps getting changed back on reboot?
C
Screenshots for comparison? Not sure what you mean by 'the task manager' in the taskbarWYes screenshots would be good too 
KValve and AMD
KIt affects SteamOS main branch too
Dok, dropping bazzite...
Dtoo buggy and slow on the desktop environment
