I've found that my legion go doesn't always sleep correctly or come out of sleep correctly. Not sure
I've found that my legion go doesn't always sleep correctly or come out of sleep correctly. Not sure if this is a known issue.
HIt's been mentioned in the buzz long before and in a recent one before it was marked as done, and it's done in bazzite so recipe names should not change going forward.
Even if we did add a warning in just, it would only show up in the list output at best, not when they run the command
Even if we did add a warning in just, it would only show up in the list output at best, not when they run the command
TGitHub
Describe the bug Seems like the new kernel is faulty or needs some Modifikation. If i select the old kernel, standby funcion does fully work on my Legion Go. Someone else have the same issue on Red...
TIs this it?
Tyeah to add to this. bazzite has rapidly changed in the 8 or so months it's had a public release. By the time it's a year old, things should relatively stay the same without major changes or cleanups
Twe're still in our infancy imo
NHave you heard of mythic for Mac or Heroic game launcher
TI am very familiar with Heroic but not Mythic. You can install Heroic via flatpak
AThey don't even read the readme you think they will read the buzz 
Tthey should /s
HThen why would they read a deprecation warning you would only see if typing
ujustBelieve me if I had a better way to deprecate the commands I would have
AYes, keep the old ujust commands until summer and add a warning when you execute them
AWelcome to technical debt 
HCan't when an alias does not allow you to do that
Twe're a cloud native project. why wait for shit
HI can give it a different description at best
Tci/cd makes progress
AYou can call ujust from ujust
AAnd add a warning before
AAnd just forget it there for a couple of months
Tstart saying this stuff if we change ujust commands after august this year imo. maybe we should be more upfront about it but ublue in general is considered experimental until Fedora officially supports this: https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable
NYeah I’m trying to figure out how to update the thing
Tpull service for github
Twe have docs on forking on our discourse
TTo continue, right now and even later on stuff might rapidly change. Development is moving fast to find the best approach for all of this, but it will eventually slow down once we consider everything to be feature complete
Ait is feature complete now
TWe wont say that until anaconda webui
TAlthough #ISO thread is cooking rn
Tso maybe sooner
Twell they're cooking with the kitchen on fire rn but eventually that'll be worked out
KYes, fix is in the issue you were linked
KUpstream kernel bug
KThanks guys. Fix applied and everything is good.
KQuick question. If I do just update, will it update the kernel to the buggy one?
KOr do you have to do an explicit rebase to change kernels?
KYeah, but you're missing almost nothing on that version at that time
KThere will be an announcement when you're clear to update
CI'm somewhat upset retrodeck decided to remove citra and yuzu completely, instead of just building from source.
Cgotta figure it out myself
CHas emudeck done that also?
Kyep
Alol
CDamn… is that them worrying about the legality of it?
Kyeah, I imagine a fork will pop up that doesn't decompile titles
Awho knows but they removing it cuz its noi longer getting updated
CThis is sad
CWasn’t citra the only real 3ds emulator too?
Kyea
Ayea
Kanother case of a fork definitely popping up
