Hwhich is why i jokingly made the suggestion to rename it to 
j0rge also doesnt like the name ujust
justu j0rge also doesnt like the name ujust
Xbluejust aka bust
Jwhat's the issue with just?
Jone the files busted last night but we fixed it
Xi don't have any issues with just
Bthanks
Dwe have 2 critical issues currently for bazzite https://github.com/ublue-os/bazzite/issues
TJust installed the bazzite deck but unfortunately I get a black screen every time I try to click on the ‘return to game mode’. I’ve tried the Ctrl Alt F2 to open the terminal and login so I could use the ‘steamos-session-select plasma’ to boot into the desktop mode. However, clicking on ‘return to game mode’ just takes me to square 1 again
T
HDid you run bazzite portal once so that steam actually can start once and download the required files for gamescope session to work?
TYes I’ve gone through the portal process already. As you can see from the vid the exclamation mark on the portal is missing since I’ve gone through the process already
TI’ll go through it again and reboot
TNo progress unfortunately
Atry
there's some discussion about some new problems on the Steam Deck with bazzite, which could be related 🛟bazzite-helpNo audio on Steam Deck after bazzite-deck:latest update
rpm-ostree rollbackthere's some discussion about some new problems on the Steam Deck with bazzite, which could be related 🛟bazzite-helpNo audio on Steam Deck after bazzite-deck:latest update
TThanks, I’ll try that and see if it helps
Aapparently today was a bad day to do a clean install 
No audio on Steam Deck after bazzite-deck:latest update
No audio on Steam Deck after bazzite-deck:latest updateTYh I also had the same problem with audio but not being able to launch game mode was the bigger of the 2 issues
TI opened Firefox to continue with your installation vid and there was no audio
Jplease move the discussion over to #
bazzite - this channel is for main ublue dev
bazzite - this channel is for main ublue dev
Bmain builds all red 
Jyeah new kernel, this always happens
Bnoo
Joooh, looking
Berror creating build container: initializing source docker://quay.io/fedora-ostree-desktops/silverblue:39: can't talk to a V1 container registryJhuh
Ball of them
Jrerunning
J502 on some of them, maybe a maintenance window
JJbut I bet it's the kernel if it fails. 
Bi was hoping to hop on the new kernel today
Bseems its going!
Joh akmods built fine except one of them so maybe we'll get lucky
Bsince you removed podman-compose from main, do we need to add it back in bluefin?
Jno upstream isn't keen on it
Jthey kind of gave up on "let's make compose but with podman", they just recommend either using the normal k8s yaml or using actual docker-compose to talk to podman via the socket
Balright they go green now, awesome.
Joh nice
Band the red one is kernel indeed
J37 should be going eol soon so we can remove a bunch of these
JJis when F37 closes
Bi'm firing off bluefin builds
D
W@j0rge what's wrong with my just syntax? https://github.com/ublue-os/bluefin/actions/runs/7047134372/job/19180540988?pr=694
Jnot sure yet, been looking at it
Jdoes it work locally?
WI'm setting up a
just test environment, give me a few minutesW@j0rge made a few changes and tested locally. Can you confirm it works on your end?
