and those any number of things don't seem to be effecting the web browser, please explain how it cou
and those any number of things don't seem to be effecting the web browser, please explain how it could be a ntp or path issue
KWorking in the Web browser rules out neither of those
Hif it was souly a time issue the web browser wouldn't function :)
Hsince discord is just a web application especially
Hany certificate will become invalid if the client is in the future or way in the past
Hits like trying to travel with an expired passport
Hand?
KAnd your certificate is invalid
KWhen using the flatpak
Hand the date showed up wrong so the logical thing was trying ntp to correct the date
Hthe path issue is related to brew and nix as it was discovered that both could break some flatpaks
KDepending on what's been installed with them
Hyeah
Hlinux doesn't work when it just should
Hgod i hate this
C@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?
