is there any status of the bluez bug where bluetooth devices won't pair?
is there any status of the bluez bug where bluetooth devices won't pair?
KI was not able to reproduce this, if you're having errors please report them upstream
KI am happy to backport patches as they are made
Cit s a sandisk extreme pro 1tb on a legion go
Creally curious why this happened tho, wish I saved some logs
KSame here because I have the same SD card
ESame card here too. No issues with it and BTRFS
Jbazzite doesn't allow layering
etckeeper because it pulls in the dnf package which conflicts with /usr/bin/dnf. This doesn't happen in a Silverblue installation.JHow do other bazzite users version control their
/etc?
Twe're supposed to version control it?
DI don't think most of us do. I only manage my home directory and dev tools with home-manager/nix
ENo need to version control it
Pi have wondered how it would be done, but i personally don't have a need. my edits in /etc are very minimal.
CYeah I don't version control it, I have maybe one or two context specific files added and one fstab edit
JWell, I generally do it with
etckeeper, but I can't layer it on bazzite.
Pi've just layered it without issues. no idea how to configure/test/use but it's on my system.
JHmmm, I'm on bazzite-deck-gnome.
Pi'm on
bazziteJcd /etc && sudo etckeeper init sets up the repo. Then sudo etckeeper commit "initial commit" checks your /etc into the repo.Pdone, seemed to work fine.
JI like to version control it because
rpm-ostree lets me go back in time, except for /etc.Pwell, we've confirmed it can work. issue lies either in adding gnome, or something deck related.
Pi have no clue of either since i do not use gnome, and have no reason to ever install a deck image
Ptime for some digging 
JI'm checking the ublue repos on github to see if I can find where that script is coming from.
Pafter rereading this, dnf shouldn't even exist... it's an ostree system. there was no
/usr/bin/dnf prior to me installing etckeeperJThere's a shell script on my system that just wraps
rpm-ostree.Pweird. 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
