Ai pinned my stable image that i was on and rebased to testing to see how good the new driver is (it's good). I'm new to the atomic thing. do i rebase back to stable, or just boot into my pinned image and that's all i need to do?
Tfedora, with a stock ublue kinoite-nvidia
Kyou'd need to add launch options for nvidia
Kauto-dGPU is a bazzite feature
Toh right, that makes sense. I'll just rebase to bazzite and see if my problems go away 
Kif you do, make sure to delete bazzite-arch
Kzero reason to use it
Toh yeah of course
Kyou can also try aurora or bluefin
Kboth have the same auto dgpu
Tah interesting
TI don't know, I've been reading the code trying to decide which image to go with... it's hard to choose!
TI'm a software dev, I play games, I also do some gamedev...
TI think bazzite would make sense?
T100%
Twe're also releasing a massive update in
:testing
CWill the current commit be 3.1?
KWhy were some programs removed?
ホAnyone using a Legion Go? Trying to figure out if the CSS profile displays correctly or not
Trebasing to bazzite-nvidia:stable first to see how much it flickers
T3.5
TMake image smaller
A@tducasse it’s not a LOT but it definitely does it and is annoying
AI ran testing for a little while and it’s sooo much better.
ASwitching back to stable right now cause I need maximum stability for my system. I can wait for the official release of 555 cause I’m guessing it won’t take long.
KWhat's the reccomended replacment for qsynth? The flatpak works?
Tit won't take long 
Tnice, that's good to know! will try stable, install balatro because it's not a 100gb DL, and see if I get 12 FPS or not 
Alol
JI'm tempted to try the testing image...
JThere is a way to see what is implemented on testing?
CIt's the same as main right now I believe, just with built images
Tgithub commits in testing branch
Tchanges will be announced when it's in stable
KOkay the flatpak works, great
KKinda surprised tbf
Aok this atomic stuff is way cool.
JTy
RYeah I can't go back to traditional after this
Arebased to testing. played around for a bit. typed in the rollback command and booted right back to stable.
Aso easy even a noob like me can do it.
Aoh and i pinned my stable deployment too just to be safe.
Tokay so it doesn't flicker anymore, but I still have the intel card in steam
O>notice memory is at 92%
>close everything except steam
>still at 80%
>close Steam
>mfw
>close everything except steam
>still at 80%
>close Steam
>mfw
JIf you rollback you overwriting the same image? If you 0 is testing and 1 is stable 2.9 you will keep the 2.9? (No pinned)
Ai believe if i understand it correctly, rollback just switches them. so testing would move to 1 and stable would be 0. so that way it default boots to stable again.
Aand then the next time you update stable, your current stable build goes to 1 and the new update would be at 0. and testing would be gone unless you pin it.
JI see,ty for the explanation
Ayou bet. hopefully i'm right but thats how it seemed to me when i read through the documentation.
