@Kyle Gospo I was told I can get help from you.
@Kyle Gospo I was told I can get help from you.
Kerror you described is a crash
Kit makes a log in your home directory
Plemme check
KHHD has a toggle for that
Pnope, no errors
Kpost the log
Paight it's a bit hard tho
Pit's my HTPC and I'm chatting from my actual PC
AAutomatically disabled unless you're over 20w
AIt's in energy management
Pmessage.txt10.12KB
K[gamescope] [[0;34mInfo[0m] [0;37mwlserver:[0m Using explicit sync when availableThis will cause you problems when it is working
Pso?
KI'm not sure why it's in nested mode...
K--backend sdl odd
Kwhat version of gamescope is this?
PWell supposedly 3.14.2-1
Pit doesn't seem right
Kif --backend is a param
Kit's way, way too new
Kyou still have the GPU issue
Pbruh
Pin the terminal, it doesn't even have the
--versionyeah that's brand new
Krpm -qa | grep gamescopegamescope, gamescope-debug-soruce and gamescope-debug info v3.14.2-1.fc40
Kdoes --help have a single reference to --backend?
Pnope
Kgamescope-session disagrees
Kso either your logs are old
Kor there's a bug that affects only that one single parm
Pprobable the former
Jthe good: I installed bazzite in my laptop, the bad: It's an optimus based one
Jat least secure boot work
KWhat is an Optimus
KRebase to verified
K
Jsomething I hate
Jfuck*
Ksudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:latestI don't care what you hate fuck just keep it in the privacy of your own game mode
JI just rebased it from fedora silverblue
KYes, you did correctly, you need 2 rebases
KThe second is just so you would be on the signed image tho
Jgreato
RI think Bazzite has a run with dedicated gpu button or something
Pwhat seems to be the problem?
