if you want a login screen and select which mode to go into then you need to make a custom image htt
if you want a login screen and select which mode to go into then you need to make a custom image
🎮bazzite
🎮bazzite
D
Sokay nice! I will read that thanks again
Hif you dont feel like messing with container files there is also https://blue-build.org that is more declarative if you are familiar with yaml files
BlueBuild
The BlueBuild project creates accessible tools for you to create, configure & build custom images of atomic Fedora distributions.
ACan you push builds to stable?
Hyes
ATested my ass, the ready appears to be broken
AGive me one sec
Has long as kyle hasnt locked hhd versions somewhere then i can rebuild as much as you want from work
Sperfect thanks! I'm pretty comfortable with containers, that should do it! 
Hyeah then you will probably prefer the first method since it is just a containerfile you edit
Hwe do not provide an image with the login screen enabled and gamemode session installed because it would mean another image for a 1kb change 
plus it breaks the steamos session management so instead why not use it to carrot people into learning how to do custom images 
plus it breaks the steamos session management so instead why not use it to carrot people into learning how to do custom images 
Arun this
ujust _hhd-dev and see if it fixes itAif it does we will push a new ver ASAP
Syes I admit it's a good source of motivation 
what problem with stemos session will I encounter?
what problem with stemos session will I encounter?Hessentially the shortcut to "return to gamemode" is a lie and steams "switch to desktop" is a lie
they will both just log you out instead
they will both just log you out instead
Hit also means that
steamos-session-select will just log you out instead of switching sessionsHminor non-issues really that wont affect you
Hyou will just have to live with the fact that your system will be gaslighting you daily with lies about what those 2 things do 
AGitHub
Handheld Daemon, a tool for configuring handheld devices. - v3.3.6: Ally ready disable · hhd-dev/hhd@014e2ec
Aand then maybe push a build
Hsure thing
Shahaha the nasty liars!! 
DIt didn’t fix it sadly 
DI even tried checking the localhost url in Firefox and no luck
H@antheas since it didnt work for DK i assume wait with build
AI don't think hhd is broken
AI think the logs showed your ally did not initialize properly and that's what I tried to fix
ADid you get the proper token?
DI got the same token when I did the command
AClose and open the desktop app
AIt will grab the token and autologin
DIll try that again
Hjust tell me when to press build, i will be on standby with my phone to press build 
have to leave pc for a bit
have to leave pc for a bitD
Arun the ujust
KWeak. What kind of crapshow are you running? Get a surface table.
AActually fuck it
A@HikariKnight press build
Hdone
ARollback to yesterday's version and wait for bazzite to build
Asudo rpm-ostree rollback and then rebootAThe controller plugin is locking hhd and preventing it from clos8ng
DThank you, I’ll do that now
DDone that, rebooted and still not working. Sorry
ADelete
~/.config/hhdAThen reboot
Asudo systemctl stop hhd@$(whoami) first so it doesn't get upset over the config disappearingDI’m gonna try again later, thank you. I did try that before and fired up he again and same screen plus the rgb is enabled (I turned off)
Hfails because of a syntax error in a just script and eveyone is asleep 
i wrote a patch though so will build anyway once its merged
i wrote a patch though so will build anyway once its merged
DSince a couple of versions, gnome nvidia version will blank by displays but the displays never go into standby. Is there anything I can check that might sort it?
Also has Bazzite migrated away from Ptyxs terminal?
Also has Bazzite migrated away from Ptyxs terminal?
