Mand it does happen on kde plasma
K3 Decks?
KWow
Tactually DE probably doesnt matter
Tmaybe idk
SWhy would there be 4 entries here and not 2?
Kostree Bug
VIt's happening a lot more regularly on GNOME than it ever did plasma. Mainly when opening overview.
T@Crush try rebasing to
:testingsee if the issue persists
VWhich issue
Tall of them
Thopefully
Awe need to fix that in any case
Twe dont
Tthis is upstream
Tfedora silverblue/kinoite do this too
Tits a grub bug
Aits not
Aits a backwards compatibility thing
Teither way
Tit happens upstream
Aif you verify grub is current you can remove the options with the setup script
Aso if fedora jumped off a bridge you would too?
Term uhhh maybe 
Tif someone fixes it for universal blue/bazzite then it should be upstreamed afterwards if it can
Tim for that
VIt's going to be hard to test seeing as most of my issues were on the initial install
Ait cant be upstreamed unless kinoite has a setup script
Amaybe bootupd can automatically fix it on f41 after updating the bootloader
Abut thats about it
ZNvm, seems setrobleshoot isnt included in the main image 
Zgonna simply push it to bazzite and bluefin instead of main to avoid any issue
Zok what is it now 
Ajust relabel your system
Aor disable selinux
Alive on the dangerzone
SKind of confused about terminal usage in containers
I set up my terminal, installed various utilities via brew.
Now I open a distro box container, those utilities are not available in the container's shell. Surely I'm not supposed to reinstall my whole shell env in every container?
I set up my terminal, installed various utilities via brew.
Now I open a distro box container, those utilities are not available in the container's shell. Surely I'm not supposed to reinstall my whole shell env in every container?
KBrew is for the host shell, you can make it work in a distorbox by setting env variables to point to brew
Kor you can export stuff you need from the container
II’m on a Legion Go
Hdoes anyone know if there's a fork of waydroid already with proper suppoort for novideo
cards?
cards?
KThat can't ever be one
His there any reason why?
KAndroid's entire graphic stack is built on Mesa
KNVK might work in the future, but it will need to wait for Android to update to a more modern version of Mesa that has a halfway decent NVK implementation
HI mean, can't they do something like implementing vkpipe
KThey're a container, not a VM. I don't think that's something they have any interest in doing
HI really thought it was basically just qemu
