Nivve
Nivve
UBUniversal Blue
Created by Nivve on 7/1/2024 in #🛟bazzite-help
8bitdo Adapter 2 does not work in Bazzite 3.5
Since updating my steam deck (Bazzite-Deck-Gnome version) and my main desktop (Bazzite-Gnome) today, both systems stopped recognizing the 8BitDo adapters, with which I connect my Dualsense controllers. The Dualsense still works wired and over bluetooth (both on my desktop and the deck), so the issue is specifically the 8BitDo adapters which are not recognised by Bazzite anymore. Also note, they are two separate adapters for two separate controllers, for two separate systems. On the nintendo switch the dualsense still works fine over de 8bitdo adapters. I have not been able to scrounge the changelog in details for xinput, xpad, xone, or udev rule related updates, but wanted to already create the issue in case someone already knows why this happened.
17 replies
UBUniversal Blue
Created by Nivve on 6/26/2024 in #🛟bazzite-help
Automatic updating fails, but manually it works fine
My system fails to update automatically, but manually updating works fine, both application and ujust. - Checking the timer, it is activated and does try to run the service.
shell
stefanvandenberg@stefan-desktop:~$ systemctl status ublue-update.timer
● ublue-update.timer - Auto Update System Timer For Universal Blue
Loaded: loaded (/usr/lib/systemd/system/ublue-update.timer; enabled; preset: enabled)
Active: active (waiting) since Wed 2024-06-26 07:36:28 CEST; 20min ago
Trigger: Wed 2024-06-26 13:56:27 CEST; 5h 59min left
Triggers: ● ublue-update.service

jun 26 07:36:28 stefan-desktop systemd[1]: Started ublue-update.timer - Auto Update System Timer For Universal Blue.
shell
stefanvandenberg@stefan-desktop:~$ systemctl status ublue-update.timer
● ublue-update.timer - Auto Update System Timer For Universal Blue
Loaded: loaded (/usr/lib/systemd/system/ublue-update.timer; enabled; preset: enabled)
Active: active (waiting) since Wed 2024-06-26 07:36:28 CEST; 20min ago
Trigger: Wed 2024-06-26 13:56:27 CEST; 5h 59min left
Triggers: ● ublue-update.service

jun 26 07:36:28 stefan-desktop systemd[1]: Started ublue-update.timer - Auto Update System Timer For Universal Blue.
However, the service fails with a generic error exit-code returned after finding the update. See attached the output of journalctl -xeu ublue-update.service and systemctl status ublue-update.service, although they give no actual error message, just the fact it fails.
7 replies
UBUniversal Blue
Created by Nivve on 1/24/2024 in #🛟bazzite-help
Provided LibreOffice cannot print as the flatpak lacks permission to cups
Although it is just a permission issue, for a casual user (read: my partner whom I just installed bazzite for) this is a bug in core functionality of the application. The 'bug' is this one on the LibreOffice issue list: https://github.com/flathub/org.libreoffice.LibreOffice/issues/190 Of course, this is not a bug in bazzite, however for ease of use of the user it is best that this is worked around in bazzite for the time being. Quick workarounds I can think of: - Bazzite adds the required permissions post-install of Libre-Office flatpak: socket=cups and socket=session-bus - Bazzite ships with the rpm version instead until the flatpak version fixes its lack of permissions. For now I cannot yet confirm the permissions suggested above indeed fix it completely. They were mentioned in the LibreOffice flatpak issue linked above. I will confirm this in an edit and a comment later today.
4 replies
UBUniversal Blue
Created by Nivve on 1/5/2024 in #🛟bazzite-help
LACT install fails with Zstd decompression error
Freshly installed Bazzite (39, Gnome, desktop image) two days ago. When going through the portal, the LACT section fails with an error about Zstd decompression. I have rerun the script with ujust install-lact, as I read elsewhere in discord (when searching for LACT) that this is exactly what the portal does in the background. This resulted in the attached error log. I was uncertain whether it is a Bazzite bug, ostree bug, or a LACT-side bug. But in any case I drop it here in case a workaround is known. Just now I also retried, as there was an update in the meantime, but the error is still there with the above command.
md
# System Details Report
---

## Report details
- **Date generated:** 2024-01-05 15:17:37

## Hardware Information:
- **Hardware Model:** Micro-Star International Co., Ltd. MS-7C56
- **Memory:** 32,0 GiB
- **Processor:** AMD Ryzen™ 7 5800X3D × 16
- **Graphics:** AMD Radeon™ RX 6950 XT
- **Disk Capacity:** 3,0 TB

## Software Information:
- **Firmware Version:** A.E0
- **OS Name:** Fedora Linux 39.20240104.0 (Bazzite GNOME)
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 45.2
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.6.8-200.fc39.x86_64
md
# System Details Report
---

## Report details
- **Date generated:** 2024-01-05 15:17:37

## Hardware Information:
- **Hardware Model:** Micro-Star International Co., Ltd. MS-7C56
- **Memory:** 32,0 GiB
- **Processor:** AMD Ryzen™ 7 5800X3D × 16
- **Graphics:** AMD Radeon™ RX 6950 XT
- **Disk Capacity:** 3,0 TB

## Software Information:
- **Firmware Version:** A.E0
- **OS Name:** Fedora Linux 39.20240104.0 (Bazzite GNOME)
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 45.2
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.6.8-200.fc39.x86_64
32 replies