It works totally fine at 120Hz but switching to 240Hz causes instant and extreme screen flicker/static:

Some steps I have tried already:

• Adding custom resolution with crh. These custom settings are not reflected in the settings:

• Verified display is using the latest firmware from Samsung
• Disable VRR, both in the display and in GNOME settings
• Use LACT to manually change the power profile to COMPUTE
• Applying this custom EDID that seems to be created for this exact problem, but I’m really not sure how to apply it since it seems to be made for Arch and the .bin file I downloaded doesn’t seem to be visible by crh(see image above again). Tried to just paste the .bin file into /usr/lib/firmware/edid but it said I was not permitted, presumably due to immutable filesystem?

Thanks in advance.

3 posts - 2 participants

Read full topic

I don’t understand English very well, so I’m using Google Translate.

I just installed Bazzit and so far everything is working correctly, but I’m coming from Windows and I can’t find the software that allows me to change the RGB colors of my Fusion RGB RAM stick. So I installed OpenRGB, and things get complicated when it asks me to install an openrgb-udev-install.sh script.

This isn’t something I usually do.

1 post - 1 participant

Read full topic

This was running prior to the latest update, does anyone know what could cause this and the potential fix? Happy to share more details and apologies if this is vague

1 post - 1 participant

Read full topic

I am getting very slow download speeds on wifi while using Bazzite specifically. I’m dual booted with Window 11 on its own separate drive and the issue isn’t a problem there, nor am I experiencing generally slow internet on any other device. Here is my wifi speed test on Bazzite when communicating to the most local server to me:

Due to the age of my account here, I can’t post images of my other speed tests. The speed test for wifi on Bazzite is clocking about 23.60 Mbps and Win 11 is clocking 472.65 Mbps which is the expected speed range I should be getting. I’m also getting around 470 Mbps on my other devices (phone, tablet, other computers). Ethernet speed tests are more or less the same between the OSs: 90-95 Mbps.

I looked around to find some troubleshooting steps on reddit, github, discord, and this forum and attempted those steps from people running into similar issues. Here is what I’ve tried:

-Set metered connection to “no”. Issue persists.

-Turned off IPv6. Issue persists

-Turned off power-saver mode. Issue persists.

-Tested with iwd on and off. issue persists regardless.

-Did a system update yesterday. issue persists.

I use the built in wifi card that shipped with my mobo. Mobo is ROG MAXIMUS Z790 HERO BTF and built in card is Intel WiFi AX211. The only primary difference between the Windows 11 and Bazzite installation unique to wifi is that I had to install the asus driver for the wifi card to get it to connect to my network. Bazzite worked OOB. But since I’m getting expected speeds on everything else, it doesn’t seem like the asus driver is doing anything uniquely special.

Does anybody have any ideas on some additional troubleshooting steps I can take to improve the wifi performance short of doing a full reinstall of the distro? I’m not quiet sure where to go from here beyond doing the distro reinstall hail mary. Also if anybody needs anymore info about my system for troubleshooting, let me know.

3 posts - 3 participants

Read full topic

CPU Information
Name AMD Ryzen 5 5600X
Topology 1 Processor, 6 Cores, 12 Threads
Identifier AuthenticAMD Family 25 Model 33 Stepping 2
Base Frequency 4.65 GHz
L1 Instruction Cache 32.0 KB x 6
L1 Data Cache 32.0 KB x 6
L2 Cache 512 KB x 6
L3 Cache 32.0 MB
Instruction Sets sse2 sse3 pclmul fma3 sse41 aesni avx avx2 shani vaes

Memory Information
Size 15.5 GB
DIMM DDR4 Synchronous Unbuffered (Unregistered) 3600 MHz (0.3 ns)

Device Name NVIDIA GeForce RTX 3070
Driver Version: 595.58.03 CUDA Version: 13.2
Max Clocks
Graphics : 2100 MHz
SM : 2100 MHz
Memory : 7001 MHz
Video : 1950 MHz
Temperature
GPU Current Temp : 45 C
GPU T.Limit Temp : N/A
GPU Shutdown Temp : 98 C
GPU Slowdown Temp : 95 C
GPU Max Operating Temp : 93 C
GPU Target Temperature : 83 C
Memory Current Temp : N/A
Memory Max Operating Temp : N/A
GPU Power Readings
Average Power Draw : 24.58 W
Instantaneous Power Draw : 24.54 W
Current Power Limit : 280.00 W
Requested Power Limit : 280.00 W
Default Power Limit : 280.00 W
Min Power Limit : 100.00 W
Max Power Limit : 350.00 W

3 posts - 2 participants

Read full topic

I want to provide the image ready to use for my team so toolbox may not work.

Any Ideas, best practices?

Kind regards

Martin

3 posts - 2 participants

Read full topic

Running bazzite on my ROG ally x docked through an hdmi 2.1 capable dock, with an hdmi 2.1 cable, to an LG C5 and no matter what I do I cannot get it all to work at the same time.

If I turn on VRR, and 4k 120hz, then turn on HDR last, the tv does not turn on hdr (can check in the settings if it is currently active) and all the colors look very muted .

If i turn on HDR first and set the resolution, when i turn VRR on in game mode settings, it also doesnt turn on.

No matter what I do I cannot get it to work, even on 4:2:2, even on 4k 100hz instead of 120 or 144.

It does work on 4k 60hz.

Does anyone have any ideas on how to get this to work, hdmi 2.1 limitation on linux? Can I use a different dock of some sort.

2 posts - 2 participants

Read full topic

What is the most effective method for determining whether this is a software or hardware issue?

3 posts - 2 participants

Read full topic

Now I have downloaded a printer driver rpm package which I did not find in the Fedora package list or on COPR.

Question: Where do I need to put that package so that I can install it in my build_files/build.sh?

3 posts - 2 participants

Read full topic

What i made is pretty amasing atleast for me since i am huge atomic fan boy and also nix fan boy and desktop side hyprland. So what if i combine all of these together with bootable container… and from idea it is the reality.

Using base-nvidia as base image i started to make progress adding Noctalia shell from copr repo meta package and there adding more hyprland what i wanted that wasent on meta package and the first boots always succesfull. there was time to go the nix way and adding nix easy as it is always on builder, but the small first boot setup had to do changing some stuff due immutale nature and then it was all good again.

Temporary Resolution (Immediate Execution):
sudo mkdir -p /var/nix
sudo mount --bind /var/nix /nix
sudo systemctl restart nix-daemon
Permanent Resolution (Persistence Across System Reboots):

A systemd mount unit must be created to ensure the persistence of the bind mount.
sudo nano /etc/systemd/system/nix.mount
Insert the following configuration into the file:
[Unit]
Description=Mount /var/nix to /nix
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target

[Mount]
What=/var/nix
Where=/nix
Type=none
Options=bind

[Install]
WantedBy=local-fs.target
Activate the newly created mount unit:
sudo systemctl daemon-reload
sudo systemctl enable nix.mount

this made nix setup work so now i dont need to figure anything about flatpaks or permissions no need to have brew or other stuff and i can manage dotfiles and nix all as decalrative way and backup all as repo. Nix is flake centric using flakes and home-manager so all settings always in hand on fresh boot or recovery way.

The build is still in baby steps and i will eventually make more tweaks and stuff so it has everything i want on my workflow and yes no distrobox or toolbox needed since nix is working on user level.

It took sometime to figure how to sign nvidia, but that was easy as it can after reading ujust and there it was after 1 minute all signed all good. only thing not sure yet does base-nvidia use open drivers or still on propriatery ones not like that is huge thing more like want to know only.

Any way nice to be here and hope we have good time.

About me little Older grumpy person already back to school in mid life. Third degree coming now on IT field and programming. Focussing on UNI Bachelor of Applied Sciences and Bachelor of Business Administration. Freelancer programmer sort of i guess been doing some stuff when i have energy and motivation and messing around with Linux and Tech stuff with self hosting and server maintance.

1 post - 1 participant

Read full topic

I’d like to switch from that to an AMD gpu.

Is there any chance I can switch without having to reinstall? I’d like to do some benchmarks first… Thanks!

4 posts - 2 participants

Read full topic

Once installed, I am not sure if I should use Docker-in-Docker (Ramalama within the container?); or, if exporting Ramalama, llama.cpp, and other tools to run on the host is ideal.

Ideally, I’d want to follow best practices to isolate me from malicious models. Ramalama already runs and hosts models using podman/containers.

I like the “ujust bbrew” Ai list. However, this also feels a lot like polluting my host OS, instead of using distrobox for Ai tooling. I’m new to Aurora-DX so if I am missing a workflow, please elaborate.

4 posts - 3 participants

Read full topic

However unlike on windows(As far back as the early versions of windows NT workstation and Windows XP) or on MacOS. when Atomic Fedora(At least if im aware. This might just be a bazzite thing but I will take the doubt and say that it might also happen on Base Fedora Atomic as well)/Bazzite runs out of memory the entire system goes down, everything freezes and im forced to force restart(flick the psu switch) the computer losing my work, Typically this happens sometimes almost everyday for me and it affects my work. Im here to report that OOM is not working on bazzite or whatever is happening when the system runs out of memory is not enough to prevent the entire system breaking. I mean this nicely and just wish for bazzite to improve of course

11 posts - 6 participants

Read full topic

I’m excited to share that the new kernel has officially landed in the :testing branch for our Desktop users! This brings a number of improvements to Bazzite 43 as we gear up for the major Bazzite 44 release. Here’s what’s new:

1. 6.19.10 OGC Kernel
2. Mesa 26.0.4
3. SBOMs (Which now power our changelogs), Build Attestation, OpenSSF security scanning, and signed ISOs.
4. Images reduced by 1GB thanks to moving in-image QEMU and ROCM to Bazzite-DX for users who need them
5. A brand‑new rechunker that further shrinks image size, with Red Hat’s Chunkah and ZSTD compression coming soon for even leaner images and updates
6. Expanded steering wheel support via additional drivers.
7. Built in support for Elgato 4K capture cards
8. Access to the latest and greatest ASUS Linux patches for use with ASUSCtl
9. New brew installer for Sunshine via ujust. Sunshine is no longer preinstalled in-image.

Builds with these improvements based on Fedora 44 will hit unstable in the very near future, and should land in stable the same-day as Fedora 44’s launch assuming no major regressions are found.

As a quick reminder, Fedora 44 means the latest versions of both KDE & GNOME, and the new Plasma Login Manager.

If you want to give these desktop builds a try you can run brh rebase testing in your Terminal. Use brh rebase stable or brh rollback if you need to return to :stable for any reason.

Our main focus is now on the Gamemode/Handheld/HTPC images of Bazzite which are undergoing major changes and improvements to bring them in sync with what Valve and others are shipping today.

Some of the improvements (beyond what’s listed above) we’re working on include:

1. An OpenGamepadUI‑based overlay for options not exposed in the Steam UI
2. Accurate changelogs displayed directly in the Steam Update UI
3. A smoother update experience from game mode
4. The latest gamescope with additional fixes from the OGC branch and working streaming on Nvidia hardware.
5. TDP control entirely through the Steam UI and powered by SteamOS-Manager and PowerStation
6. Numerous bug fixes for the Legion GO 2 and other recent handhelds thanks to Input Plumber.

Our plan is for the -deck images to receive all of these enhancements, plus the Fedora 44 base and new kernel, slightly later. This gives us time to test across our large ecosystem of supported handhelds with community feedback. We appreciate your patience and support during this transition, and we’ll announce when these images are ready for broader testing.

We’d love to hear your feedback. Every issue reported against these testing builds helps us deliver a smoother, more polished stable release.

Lastly I just want to give a shout-out to our contributors, you’ve all been rockstars through this process and I can’t thank you all enough!

14 posts - 9 participants

Read full topic

I’ve noticed that after the most recent update, Waydroid, Lutris, and Web Apps have reappeared in my system image. I had previously uninstalled these packages in early January using rpm-ostree.

It seems the update ignored or reverted the local overrides. Is this a known behavior in the latest Bazzite build, or has there been a change in the image manifest (package renaming or dependencies) that might have triggered this?

I would like to know the best practice to ensure these packages remain uninstalled permanently across updates.

System Info:

OS: Bazzite Gnome Stable| Linux 6.17.7-ba29.fc43.x86_64
Hardware: B650E-I | AMD Ryzen 5 9600X | RX 9060 XT

2 posts - 2 participants

Read full topic

What do you think the requirements should be for having an app be part of the image? Steam, obviously, since gaming is central to Bazzite, but why was Firefox changed to a Flatpak? It does cause issues with Plasma browser integration. And it’s so puzzling to me that that was perceived as necessary, while a random app like webapp-manager isn’t replaced with one of the many Flatpak PWA managers available. Thoughts?

2 posts - 2 participants

Read full topic

the setting shown in the image below hasn’t fixed it

1 post - 1 participant

Read full topic

upstream bug filed, workaround documented

POST TO

https://universal-blue.discourse.group (Bazzite/Universal Blue forums)

and/or Bazzite Discord #bug-reports

TL;DR: Screen sharing and OBS PipeWire capture are silently broken on
Bazzite KDE due to a bug in xdg-desktop-portal 1.20.3. KWin’s screencast
plugin never initialises because the portal fails to open a /proc path
using invalid syscall flags. Bug filed upstream. Temporary workaround below.

What’s broken

On Bazzite 43.20260406 (KDE Plasma 6.6.3, xdg-desktop-portal 1.20.3), screen
sharing fails silently:

• OBS PipeWire screen capture: chooser never appears
• Browser WebRTC screen share: nothing happens
• Discord/Electron screen share: black frames or no dialog

No error is shown to the user. The failure is only visible in journalctl.

Root cause

wayland-info | grep zkde_screencast returns nothing — the
zkde_screencast_unstable_v1 Wayland protocol that enables screencasting is
never registered by KWin. This happens because:

1. KWin’s screencast plugin registers with xdg-desktop-portal at startup
2. The portal tries to open /proc/<kwin-pid>/root using
   O_RDONLY | O_NOFOLLOW
3. /proc/<pid>/root is a kernel symlink; O_NOFOLLOW always returns ELOOP
4. Portal reports “Unable to open /proc//root” and rejects registration
5. KWin never creates the Wayland screencasting global
6. All screen sharing silently fails

This is a bug in xdg-desktop-portal 1.20.3 (filed upstream). It affects all
unsandboxed processes on composefs/immutable systems. Bazzite is particularly
affected because the composefs root filesystem layout is what triggers the
portal’s crash-and-restart cycle at session start, which is when KWin fires
its registration attempt.

How to confirm you’re affected

# Should return a line with zkde_screencast_unstable_v1 if working
wayland-info | grep zkde_screencast

# If blank, check KWin journal for the error
journalctl --user -u plasma-kwin_wayland --boot --no-pager \
    | grep "register\|portal\|screencast"
# Look for: "Unable to open /proc/<pid>/root"

Workaround (until xdg-desktop-portal is patched)

No clean session-safe workaround exists. The only fix that works is to ensure
the portal is fully stable before KWin fires its registration attempt —
currently they start almost simultaneously (within 16ms of each other).

A sleep drop-in on the portal causes other Plasma services to time out.
A sleep drop-in on KWin restarts the compositor (logs you out).

The permanent fix requires a patch in either:

• xdg-desktop-portal: use O_PATH | O_NOFOLLOW instead of
  O_RDONLY | O_NOFOLLOW (primary fix, filed upstream)
• KWin: create zkde_screencast_unstable_v1 regardless of portal
  registration success (defensive fix, filed at bugs.kde.org)

Upstream reports

• freedesktop/xdg-desktop-portal: #XXXX (primary — wrong syscall flags)
• KDE Bugzilla: #XXXXX (secondary — KWin should not hard-depend on
  portal registration)

Useful diagnostic tool

If you want to check your own system’s full portal stack status:

# Checks all seven known screensharing failure modes, outputs JSON
bash wayland-screenshare-diag.sh

Script available at: [link to repo when published]

Tested on: Bazzite 43.20260406, KDE Plasma 6.6.3, NVIDIA RTX 5090,
driver 595.58.03 open modules, kernel 6.17.7-ba29.fc43.x86_64

2 posts - 1 participant

Read full topic

• Motherboard: ASUS TUF Gaming B650-PLUS WIFI

• BIOS Version: 0421 (American Megatrends Inc., 19/08/2022)

• SMBIOS Version: 3.5

• Embedded Controller Version: 255.255

• CPU: AMD Ryzen 9 7900X (has integrated GPU)

• Drive 1: NVMe SSD — Windows (working)

• Drive 2: SSD (non-M.2) — Bazzite Linux (working individually)

• Secure Boot: Enabled (required for Battlefield anti-cheat)

• MOK Keys: Enrolled during Bazzite install to keep Secure Boot enabled for Windows

The Problem

After installing Bazzite on a second SSD alongside an existing Windows install, it is no longer possible to enter the UEFI/BIOS setup. Pressing the BIOS key (DEL/F2) at POST results in an infinite black screen instead of the BIOS menu.

Behavior with different drive configurations:

Drives Installed	Boot to OS	Enter BIOS
Windows SSD only	Windows boots	BIOS works
Bazzite SSD only	Bazzite boots	Black screen
Both SSDs	Boots to Windows (boot order resets)	Black screen

Key observation: BIOS access fails whenever the Bazzite SSD is present, even if it’s the only drive. However, Bazzite itself boots and runs fine when it’s the only drive installed.

What Has Been Tried

1. systemctl reboot --firmware-setup — Command executes but reboots into a black screen instead of BIOS.

2. HDMI directly to motherboard (iGPU output) — No change, still black screen.

3. CMOS reset (battery removal / jumper short) — Did not fix the issue. After CMOS reset, the board prompted “Press F1 to enter setup,” but pressing F1 still resulted in a black screen.

4. Swapping SSD slots — Not possible due to different form factors (one is M.2, the other is not).

Installation Details

• Bazzite was installed using the “wipe the SSD” option, which created a separate EFI System Partition on the Linux drive (so there are now two ESPs — one on each drive)

• MOK keys were enrolled during setup so that Bazzite could boot with Secure Boot enabled (Secure Boot needs to stay on for Windows/Battlefield anti-cheat)

• Before the Bazzite install, BIOS access worked without any issues

• Current BIOS version (0421) is from August 2022 — significantly behind the latest available version (3842, released March 2026)

What I’m Looking For

Any guidance on what’s causing the BIOS lockout and how to fix it without losing either OS. Happy to run diagnostic commands from Bazzite (booted alone with Windows drive removed) if that helps narrow things down.

3 posts - 2 participants

Read full topic

• OS: Bazzite (KDE Desktop)
• Motherboard: ASRock B550 Phantom Gaming 4
• GPU: NVIDIA RTX 2070
• Audio chip: Realtek ALCS1200A

Problem:

After a fresh install of Bazzite, only the NVIDIA HDMI audio outputs are visible in the sound settings. My speakers and headphones connected via 3.5mm jack on the motherboard are not showing up at all. Everything worked fine on Windows.

pactl list cards short only returns 2 cards (both NVIDIA HDMI):

50    alsa_card.pci-0000_06_00.1    alsa
51    alsa_card.pci-0000_08_00.4    alsa

lspci | grep -i audio also only shows the NVIDIA cards — the Realtek does not appear.

What I tried:

• Enabled HD Audio in BIOS (was set to Auto)
• Installed pavucontrol — only Digital/Pro profiles visible, no Analog
• Tried options snd-hda-intel model=auto in /etc/modprobe.d/alsa.conf → no change
• Tried options snd-hda-intel model=alc1200 → no change
• Tried options snd-hda-intel model=dell-headset-multi → no change

However, dmesg | grep -i snd shows the Realtek IS detected at boot:

snd_hda_codec_alc882 hdaudioC1D0: ALCS1200A: SKU not ready 0x00000000
snd_hda_codec_alc882 hdaudioC1D0: autoconfig for ALCS1200A: line_outs=1 (0x14) type:line
snd_hda_codec_alc882 hdaudioC1D0: hp_outs=1 (0x1b)
input: HD-Audio Generic Front Headphone
input: HD-Audio Generic Line Out

The “SKU not ready 0x00000000” line seems to be the root cause — the driver detects the chip but fails to configure it, so PipeWire ignores it entirely.

Any idea how to fix this? Is there a known workaround for the ALCS1200A SKU issue on this motherboard?

Thank you!

1 post - 1 participant

Read full topic

8 posts - 3 participants

Read full topic

Using 84% GPU

1 post - 1 participant

Read full topic

1 post - 1 participant

Read full topic

I just installed Bazzite alongside Windows, coming from Zorin OS.

So far, I got everything set up. One thing, which is really annoying me, is the Steam seems to be very slow for me.

• If I start a game, e.g. Witcher 3, it takes up to one minute to start the game at all.

• If I right click on a game on Steam for example, it takes up to 3 seconds to open the window.

• Got also a weird bug that when I right click on a certian game “Foundation”, Steam crashes. Only happens with this game.

Already tried ujust fix-reset-steam but it doesnt seem to change anything.

Moreover I am getting this error: ERROR: ld.so: object '/usr/lib/extest/libextest.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Can anybody help me with that?

My fastfetch info:

bazzite-nvidia-open:stable 
Bazzite
Linux 6.17.7-ba29.fc43.x86_64
AMD Ryzen 9 7900X3D (24) @ 5.66 GHz
AMD Raphael [Integrated]
NVIDIA GeForce RTX 4080 SUPER [Discrete]
8.40 GiB / 30.55 GiB (28%)
107.58 GiB / 2.23 TiB (5%) - btrfs
3440x1440 in 34", 165 Hz [External]
KDE Plasma 6.6.3
KWin (Wayland)
bash 5.3.0
konsole 25.12.3
2927 (rpm), 57 (flatpak-system), 9 (flatpak-user)

Thanks for any help!

4 posts - 2 participants

Read full topic

3 posts - 3 participants

Read full topic

Recently midway through typing my password to login my keyboard seemed to stop working. I had installed pipewire through Bold Brew and restarted then the issue started.

I tried troubleshooting and was able to come up with the following information:
The keyboard seems to be recognized as a USB device, it appears with lsusb
when I try evtest the device it’s recognized, the event codes seem to be all present, and keys are picked up when clicked
*Properties:
Testing … (interrupt to exit)
Event: time 1775182104.278304, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70004
Event: time 1775182104.278304, type 1 (EV_KEY), code 30 (KEY_A), value 1
Event: time 1775182104.278304, -------------- SYN_REPORT ------------
Event: time 1775182104.356299, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70016
Event: time 1775182104.356299, type 1 (EV_KEY), code 31 (KEY_S), value 1
Event: time 1775182104.356299, -------------- SYN_REPORT ------------
Event: time 1775182104.401297, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70007
Event: time 1775182104.401297, type 1 (EV_KEY), code 32 (KEY_D), value 1

uname -a returns
Linux bazzite 6.17.7-ba29.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 25 07:35:02 UTC 2026 x86_64 GNU/Linux

system information:
System Details Report

Report details

• Date generated: 2026-04-04 00:31:22

Hardware Information:

• Hardware Model: ASUS PRIME B550-PLUS
• Memory: 32.0 GiB
• Processor: AMD Ryzen™ 5 5600X × 12
• Graphics: NVIDIA GeForce RTX™ 3070
• Disk Capacity: 8.0 TB

Software Information:

• Firmware Version: 2423
• OS Name: Bazzite
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 49
• Windowing System: Wayland
• Kernel Version: Linux 6.17.7-ba29.fc43.x86_64

I tried resetting bazzite to no success, uninstalled pipewire, reset keyboard settings, all to no avail.

Apologies for poor formatting, this was typed through KDE connect and copied out from terminal. Any help or insight would be appreciated, I’d like to avoid reinstalling.

Thanks

1 post - 1 participant

Read full topic

1. ujust _toggle-autologin doesn’t work, isn’t an included script anymore. Changing the sddm boot to plasma wayland from KDE also doesn’t work.
2. ujust setup-sunshine is missing completely, even though it’s part of the gui and ujust help menu.

2 posts - 2 participants

Read full topic

I did see @j0rge earlier post about AI, and that answered the broader question pretty well. It seems clear that Universal Blue is supportive of AI workloads and sees them as an important part of the space.

What I am more curious about is the development and contribution side of it.

I know there are pretty strong opinions out there about AI in general, especially around development work. Personally, I take a more pragmatic approach. I see real value in where it can save time or help unblock things, and it has definitely helped me learn. At the same time, I’m also aware it can produce bad or misleading results, and there’s no substitute for actually understanding what you’re doing (and actually doing it yourself!).

So I was curious how AI is currently viewed, if at all, in the actual development and maintenance of Universal Blue. Is it being used in any meaningful way for image development, infrastructure, repo maintenance, or related work? Is there a general philosophy from the team on where it is appropriate versus not appropriate on the development side?

From a contributor perspective, I’m also interested in how AI-assisted work is viewed. If someone finds a bug, uses AI to help generate a fix, and submits a PR, is that just evaluated on its merit like any other PR as long as it’s correct and tested?

I did see references in Bluefin docs around AI attribution, so I wasn’t sure if that reflects the broader Universal Blue stance or just that specific project.

I tend to treat AI-generated code and fixes VERY carefully. If I don’t fully understand what is being done, I simply don’t submit a PR. It would be crazy embarrassing to submit a PR, even if it works, and then have somebody ask a question, only to have to say “well, IDK… didn’t write it!” lol. On my own personal repos I’ve let it go wild and it’s created some monstrously complicated workflows and logic, but on somebody else’s repos I would never submit a PR with something like that.

Mostly just trying to understand the expectations and norms here before contributing more actively.

So… before looking at my Claude and OpenAI Codex percentages left for the week and pointing it at all the Universal Blue repos and saying “look for any and all bugs, and submit PRs” … NO… I would not do that ROFL, but I hope you can get what I’m asking in a roundabout way

I really appreciate the proofread function in Discourse! So, AI for the win there!

BTW… in case anybody else knows about this (stumbled across it the other day), this automated wiki scans repos and tries to understand them, very cool and useful (if right!). Example: ublue-os/main | DeepWiki

1 post - 1 participant

Read full topic

Directories as shown:

PixInsight will be installed with the following parameters:

Source installation directory … PixInsight_install
PixInsight core application … /opt/PixInsight
Application desktop entry … /usr/share/applications/PixInsight.desktop
Application icons directory … /usr/share/icons/hicolor
MIME type description file … /usr/share/mime/packages/PixInsight.xml
Create /bin launcher script … yes
Remove previous installation … yes

It errors out with:

Please wait while PixInsight is being installed…
*** Error: Unable to create file: Read-only file system: /bin/PixInsight

I am very much a noob with Bazzite, but a long time Windows user. I’m sure the solution is simple, I’m just not sure what it is. Any help out there?

3 posts - 3 participants

Read full topic

chrisdown.name

Debunking zswap and zram myths

zswap and zram are fundamentally different approaches with different philosophies. If in doubt, use zswap.

If in doubt, prefer to use zswap. Only use zram if you have a highly specific reason to.

4 posts - 2 participants

Read full topic