weird. i would guess at it being some weird compatibility fix for something with gnome. (big stab in
weird. i would guess at it being some weird compatibility fix for something with gnome. (big stab in the dark)
JI'll investigate tomorrow when I'm more awake. Still happy to have finally gotten it installed on working on my steam deck, so now it's just figuring out the little things to make using it in Desktop mode better for me.
IIs there somewhere I can easily follow the status of bazzite on steam deck oled? I'd like to install it when it's fully functional
Pthe
:testing branch has many OLED fixes/changesPthere's no curated document or anything if that's what you were after.
Iyeah I was looking for like a list of known oled specific issues
Iguess I can check back in a month or so to see if stable branch is working well
MNobara and Bazzite have 100% OLED functionality. Nobara does for sure and the new fsync kernel today that will get put on :testing should have the last fix needed for Bazzite, related to refresh rate changes.
MWiFi and Bluetooth got figured out a couple weeks ago while audio for Linux 6.6 finally got solved last week
JDigging through the ublue-os repos on GitHub, I found this: https://github.com/ublue-os/akmods/blob/main/build-prep.sh
I think the -deck images are built with
I think the -deck images are built with
KERNEL_FLAVOR=fsync, which triggers running rpm-ostree cliwrap ... which I think installs scripts in /usr/bin/dnf and /usr/bin/rpm.GitHub
A caching layer for pre-built Fedora akmod RPMs. Contribute to ublue-os/akmods development by creating an account on GitHub.
JI'm trying to understand why
rpm-ostree cliwrap needs to be called in that script.
Hthe fsync kernel should only be in :testing atm i believe, since it will not work with secure boot, are you on
other than that i dont know anything else about it
:testing?other than that i dont know anything else about it
Phoneslt i think its just to work around lakc of user knowledge. i would just back it up in case something goes awry and remove it
Kcan't install a kernel w/ ostree without doing that
Pinstantly corrected lol
K
RIt's published by Epic, not sure if it ever get published outside EGS.
R(I mean, if they want to get back the money spent on it probably yes /s)
CNow that i finally have filled up my sd card with games ill never play, time to add productivity crap. What’s the best way to install ides? Jetbrains etc, heard there were a couple options layers, distrobox, etc - flatpak’s a no for jetbrains unfortunately (or it might be, havent tried out flatpak jetbrains in a while)
Hfor any application the ideal order to try find applications would be
- flatpak
- your choice of appimage, distrobox, nix, brew, etc in the order you want/prefer
- rpm-ostree (last resort as it will slow down your updates a lot)
Hif you do have a dev environment you can replicate in a different distro, i would suggest making a development distrobox and contain the toolchain to that 
CNice, thanks mate
Hand if youre proficient with nix then use nix if you prefer that
Hi personally prefer distrobox
RThere is also Devbox which can create "isolated, reproducible development environments that run anywhere". It also uses Nix under the hood.
https://www.jetpack.io/devbox/
https://www.jetpack.io/devbox/
Devbox creates isolated, reproducible development environments that can run anywhere without Docker or virtual machines.
KAny reason dual boot doesn't work out of the box if this uses the Fedora installer ?
JAh, it probably needs
/usr/bin/kernel-install which does several non-trivial actions in the cliwrapper script. I will just install etckeeper into /usr/local
JYes, I'm testing bazzite on a Steam Deck OLED, and that seems to be the only image+tag that allows a USB keyboard attached to the dock to work at boot (needed to enter password used for FDE).
DIs there a way to disable the thing that asks for a password every time I open my browser? It's super annoying
Dif you want dual boot use separated disk
CIt does, the disclaimer that it's not officially supported means "do it at your own risk, back up everything on an airgapped drive first"
CDid you uninstall/delete kwallet?
DI'm using bazzite deck gnome
CGnome, alright. Did you enable passwordless login?
DI think that's enabled by default in the deck version right?
CI'm not sure
CI don't have a deck, but passwordless login on my laptop made me enter my password upon opening my browser because it has a password manager which by design requires some escalation of privileges to cough up things like credit card info
Twhat browser?
DGoogle chrome
ZWoot? rpm-ostree slows down updates?
Hthink of it as git for your whole OS
when you update, it has to download the new image then "git rebase" all your installed applications onto the new image
in layman terms it essentially "re-installs" the programs installed with rpm-ostree with each new update to the base system
when you update, it has to download the new image then "git rebase" all your installed applications onto the new image
in layman terms it essentially "re-installs" the programs installed with rpm-ostree with each new update to the base system
DWhen using kde I just deleted kwallet and that solved the problem but I don't know what I can delete to resolve this on gnome
ZThree lines button isn't doing the trick
ZDamn. There's some essential apps I need from rpm-ostree that I can't modify any other way
Hthen keep them as rpm-ostree, we are just warning you so you dont install everything with rpm-ostree and get a system that takes hours to update 
Hor get into a situation where it breaks updates in general until you uninstall the packages that stops it from updating (imagine how fun that will be with 300+ layered packages if you went that crazy 
)
)ZI tried getting gphoto2 working through nix but I couldn't get nix to work too reliably sadly
Hyeah if neither nix or distrobox does it for you then rpm-ostree is the last resort which is why we call it last resort
Hmain point is to avoid people going straight to layering the package they want when it might not be neccessary
ZWell, if one layers 300 packages maybe it's best to setup a custom image
ZAnd let GitHub fix all of that
