@KyleGospo thanks, brightness is working again
@KyleGospo thanks, brightness is working again
CIs it possible for me to freeze auto os updates?
EOn the desktop image you can run
systemctl disable --now ublue-update.timerEOn the Deck image, just don't press the apply button
CIt doesn’t auto update on restart? Sweet thanks
EWell... Kind of. The update gets downloaded and you boot the new ostree on restart
EThe desktop image does this automatically. The Deck image just checks and it's up to you to apply it
Cyep sweet thanks
ENo problem
NAnybody using a PS5 controller with Bazzite? Does it work pretty well out of the box?
NI've mostly been using Xbox controllers and PS4 controllers.
Hit works fine, some games dont like it but that might have changed (but thats on the game not fully liking steam input).
i do think bazzite disables the touchpad mouse on the ps controller though from what i remember unless that changed (i dont use the ps5 controller very often, plus my ps5 controller is currently in for repairs as it was a custom controller)
i do think bazzite disables the touchpad mouse on the ps controller though from what i remember unless that changed (i dont use the ps5 controller very often, plus my ps5 controller is currently in for repairs as it was a custom controller)
KI do, works great
LDoes the rpm-ostree update command do pretty much the same thing as ublue-update? as far as system updates are concerned.
KYes
KUblue update does more, but rpm-ostree is directly executed by it and the most important
Li just got a weird systemd error during boot see below
Lsystemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Sat 2023-12-30 22:37:46 EST; 6min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Main PID: 1037 (code=exited, status=1/FAILURE)
CPU: 30ms
Dec 30 22:37:46 fedora systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
Dec 30 22:37:46 fedora systemd-sysctl[1037]: Couldn't write 'true' to 'net/ipv4/tcp_mtu_probing': Invalid argument
Dec 30 22:37:46 fedora systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Dec 30 22:37:46 fedora systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
Dec 30 22:37:46 fedora systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Sat 2023-12-30 22:37:46 EST; 6min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Main PID: 1037 (code=exited, status=1/FAILURE)
CPU: 30ms
Dec 30 22:37:46 fedora systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
Dec 30 22:37:46 fedora systemd-sysctl[1037]: Couldn't write 'true' to 'net/ipv4/tcp_mtu_probing': Invalid argument
Dec 30 22:37:46 fedora systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Dec 30 22:37:46 fedora systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
Dec 30 22:37:46 fedora systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
Lthis is on steam deck LCD version bazzite-deck:lateset
KThis should already be fixed, just update again
Loh ok
KFor some reason Steam isn't registering my paired controller. Are there any flatpak shenanigans or anything I need to be looking at for this?
KSteam is a layered package, not a flatpak
KIf you've installed the flatpak I would remove it and debug from there
KI have not, no
KI just assumed it was one. Okay, then why would KDE happily pair my controller but Steam seem blind to it? Or how can I start to troubleshoot this?
KWhat controller?
K8bitdo SN30 Pro Plus. paired in Xbox controller mode. Worked fine in Fedora 39, paired fine in Bazzite.
KTry
ujust use-stock-gamepadsAnd then reboot
Kokay
KThat did the trick, thank you. Can I ask what that was changing, just so I know in the future?
KDisabled xone and xpadneo
KGreat for official controllers, bad for controllers that lie about being Xbox controllers
KAhh gotcha okay
Kso if I ever buy a series X controller I'll want to switch back eh?
KPotentially, yea
KWith that change you're using 100% stock fedora drivers for controllers
KSo anything that applies upstream will apply to you
KSeems reasonable. Well it's all working happily now.
KThanks for the help!
KNp!
CIs there any way to build older Nvidia drivers, since rpmfusion won't?
CSo, i am a stupidass and it's not my motherboard being weird
Ci didn't enroll secure boot key properly
EYou can't downgrade without performing a replacement which would require the driver version be higher than the current driver which would require setting it higher than 545 in the spec file which will break things unless the version is hard coded everywhere else which isn't worth the time and effort unfortunately
Z@rodoma92 Have you gotten any updates on the bluetooth stuff? Is the keyboard still working?
Z@j0rge Sorry for the ping, but is this still the case?
The PR has been merged.
just supports include directives under the --unstable flag which is enabled by default with a shell alias set in /etc/profile.d/. If you have a posix-incompatible shell such as fish, you will need to alias just to just --unstable manually or wait until just PR #1588 merges, and you’re able to set it as an environment variable instead.
The PR has been merged.
CI GOT DROIDCAM WORKING AT 1080P
Csudo v4l2loopback-ctl set-caps h264 1920x1080@30sets the video to 1080p and with DroidcamX it just works flawlessly
