Maybe it's more so that OS development is hard as j0rge said, and Valve employees generally only wor
Maybe it's more so that OS development is hard as j0rge said, and Valve employees generally only work on what they want to
CThe whole process is vulnerable to bikeshedding
Aor y'know, when your entire company is something like 300 employees total
Aof course you don't have bandwidth to work on both the deck OLED and a general-purpose SteamOS release
Awhich is why Valve said no to Lenovo when Lenovo reached out
MMost kernel stuff is igalia anyway
CBut even then, if you have a handful of hyperproductive lads like S76 does
Jthis is why the cloud native way wins, maintaining distros is hard. So don't maintain a distro, derive from a base image and improve. Boom.
P"don't maintain a distro. just maintain a distro"
CKick the can down the road :moyaiguy:
Ai do think the CI/CD update cadence is a bit crazy though
V
Jyeah but the cadence is totally adjustable
Jbazzite chooses to be this way I guess lol, but it seems to be working
VHelp it's stolen focus, I can't move it
VThis is the future microsoft wants
V
Pyou probably don't want to bother with this on wayland lmao
Aeh, i've been disincentivized from updating bazzite too often. not sure about others, but i get regressions more often than features
CMaybe Kyle likes to watch the builder do its thing
Aso now i just wait a while before updating
Tsomeone took a bite out of that window
JI get it, I'm in bluefin land and everything about my computing life is perfect hahah.
CI'm actually waiting on the next successful build to see rechunk working
Jthough I think if more people stepped up we could maybe add a new tag or something
Twe need to convince the bazzite users to install bluefin/aurora on something
CHaven't had many regressions lately, besides Blur my Shell fucking with workspace transitions on unlocking from sleep
JThat's the nice thing about this Verge mention, the more attention we get, the more people like us will show up, which means we can fix more stuff. The virtuous circle.
DPerhaps this issue (not that there's anything useful there): https://github.com/winapps-org/winapps/issues/210
CFixed by overriding it with a local install, broke the screenshot blurring on my secondary monitor :build_failed:
CYou win some, you lose some
VI've got a few issues which I'll look into, for example launching an app isn't starting the container for me so I have to do it manually
VAnd sign out*
Ai'm stuck on image 07/22 on some of my devices because of the screen artifacts bug 🛟bazzite-helpscreen artifacts in gamescope-session on the V3
CA lot of the ones I've seen are gamescope related, I'm spared of those on the desktop image thankfully
Aoh yeah, desktop has less issues
DOn mine I have to attempt opening the app twice. So: Boot > explorer > wait a bit > explorer again. Do let me know what you can and can't fix I'll update the guide
VYeah just nothing, never starts. I get this error.
HHey I’m only getting 115W of my GPUs 140W max TDP, is there a trick to getting it to run fully? I can’t seem to remember
VVNC isn't on either so I'm guessing the container is just down
DYeah probably, especially if it's fixed with booting it up manually. It should use your ~/.config/winapps/compose.yaml file to spin up
KWould also be nice if these issues were consistent
KLike I know that artifacting is a bug, but I don't have it on any hardware
KAnd there are other people with the exact same hardware who do exhibit it
KAnd of course gamescope just being stable for once
KI think we're close
Pcatch me doing NOPTHING
Phahaaa thanks vberge
LI’ll hopefully be in a better place to test stuff on my OLED in around a week
V@dannymate Ok for some reason I don't think it ever "makes" the container? Because if I then try to use "start" it just says no winapps container exists
Ayep, i get that it's mostly outside of your control. and thankfully rpm-ostree makes it trivially easy to rollback
i'm just not as gung-ho about updating as I was before
i'm just not as gung-ho about updating as I was before
