Every time I try to open it, it will open for 15 seconds sometimes having random freezes and then close.
When trying to run it from a terminal we see its because of a segmentation fault
Segmentation fault (core dumped)
There needs to be a switch to something else because its literally unusable right now and unstable. I can not install anything
I wish I could say something but it is so broken that simply hitting the BACK button crashes the whole software.
Ive been trying for the past 5 mintues to install kdenlive. I cant do it. Like it crashes even before I hit the install button in some cases
Okay let’s take it slow and try to troubleshoot this.
Can you type the following command in terminal and post the results:
rpm-ostree status
so we can make sure nothing is layered that might be messing with the system. After that please post your system specs. Until we manage to fix the issue, you can use terminal command:
flatpak install appname
to install things. In this case, try “flatpak install kdenlive” and see if it works.
rpm-ostree status
State: idle
Deployments:
â—Ź ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable
Digest: sha256:5d00e03454fd904f942ef14ecd68f63cb3a1541575ba770120b7c9756b352ea6
Version: 42.20250915 (2025-09-15T05:11:56Z)
LocalPackages: nordvpn-3.17.0-1.x86_64
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable
Digest: sha256:5d00e03454fd904f942ef14ecd68f63cb3a1541575ba770120b7c9756b352ea6
Version: 42.20250915 (2025-09-15T05:11:56Z)
LocalPackages: nordvpn-3.17.0-1.x86_64
Okay, you will not like this but I would suggest resetting ostree to get rid of layered packages. This will mean nordvpn has to go.
You might think it has nothing to do with bazaar, but if possible, run
rpm-ostree reset
to reset your system and try and see if Bazaar works that way. Honestly that’s the only thing that comes to mind at the moment.
Also, googling gave this result:
“OK, I fixed the problem. Apparently I had some other flatpak repo’s installed in Warehouse. I deleted them, and Bazaar works now. Not a fan of this new app store, but then again, I hardly use it.”
So if you have any other flatpak repos installed, I recommend removing it.
Only distro where installing software is a problem. fine ill do it. but I dont think that repo would cause a segmentation fault.
You are also on very old image, probably because you have nordvpn and for some reason its blocking background updates
This atomic immutable stuff is really getting annoying. All these hoops and problems. Simply having old software now means that it can block entire updates.
I manually updated via flatpak and am now going to do a system updtae hopefully that fixes it
You have to realize that older image has for example older version of Bazaar for example, so might have fixes for your specific issue for example.
Well, you are using the OS for what it’s not designed for. Honestly, that is your problem, not reading documentation and understanding what the OS is designed for.
Honestly friend, pick a tool that meets your needs instead of forcing it to do things it is not supposed to. Also, when you ask for help with a bug, give some information instead of just saying “x stuff is not working.”
If I didn’t ask, you wouldn’t say if you had anything layered, if you had any extra repos added, you didn’t even tell me which version of Bazzite you are using or your PC hardware. I had to look at your rpm-ostree status to understand you are using the dock version. You get the idea.
Simply having old software now means that it can block entire updates.
It’s not having old software that’s blocking entire updates. If you actually spent some time reading the documentation you would know. When you layer stuff, which you did with nordvpn, you block system updates. Because your system is no longer immutable.
You can read this for more information. Here’s the gist of it though:
rpm-ostree(System-Level Packages) - Layer Fedora packages at a system-level (not recommended, use as a last resort)
Use this method as a last resort and for anything at a “system-level” only.
MAJOR caveats using
rpm-ostree¶Layering packages can cause severe consequences including:
Pause system updates until package(s) are uninstalled.
Prevent rebasing to different images until package(s) are uninstalled.
Conflict with existing packages as part of the image leading to dependency issues.
Updates taking longer to download as you layer more packages to your system.
Again, you’re using Bazzite in ways it’s not designed for.
Only distro where you cant install a package file without it pausing all system updates award.
“Well, you are using the OS for what it’s not designed for.”
Because theres no other option thats why. this immutable stuff sure as hell does not make the thing more stable. Heck ive used alot of dsitros and this is one of the most unstable one. I never imagined installing a manual package to literally be almost system breaking.
I cant even figure out WHY it needs to be immutable. Like it does not make the system more idiot proof. If anything it just makes it less idiot proof. And all the “Benfits” of a immutable operating system come with massive downfalls like not being able to install package files that aren’t 100x layered high level flatpaks.
Im to lazy to cancel my subscription. But also I use it for torrenting and other stuff because im to lazy to learn how to do it without it. Thats why I use nordvpn
Ill reset Rpm-ostree and maybe make a SH script to add nordvpn back that i can run every update.
it would be easier to customize your own image based off of bazzite. it’s not as hard as it looks. GitHub - ublue-os/image-template: Build your own custom Universal Blue Image!
it also may be possible to route all the traffic of your host system through a nordvpn distrobox container if you would want to go through that hassle.
alright ill try that thanks.
What hardware are you on? People have reported issues related to libdex in the past on their older Quad Cores and more recently Bazaar crashes shortly after loading · Issue #995 · ublue-os/aurora · GitHub.
Ryzen 5 5700x and a 9600xt
If people are going to be layering a large number of packages, they should follow the proper instructions and, instead of repeatedly layering software, create their own custom image based on whichever distribution they prefer, Aurora, Bluefin, or Bazzite. From there, they can install all the packages they need, then use GitHub Actions to rebuild and keep their image up to date with upstream changes. Using a custom image won’t guarantee that every issue is fixed, but it’s a far more stable and maintainable approach than constantly layering new packages. If I needed to add that many components (or components that are significant), I’d do exactly that or move to a non container based distro. There’s no shame in that; I run both uBlue and traditional non-containerized distributions.
I know that not everyone can do that or is ready to dive into that, but I think that is the recommended approach.
The uBlue team can’t make a single distribution that will cater to all situations, and unfortunately the system level stuff that is being managed by bootc/rpm-ostree is NOT intended to be mucked with. That’s the whole point. If you need to muck with it, then you are back in the land where you are working on your own car. This is fine, you may need to, but uBlue really isn’t that car unless you intend to do the work the uBlue team is doing with the base container images, which is to test them and make sure they work.
The real issue is not informing users that an update is available, reboot when it suits you.
Then you can also inform them that the update failed.
Not communicating AT ALL, not informing the user at all, is an OS that doesn’t go out of the way of the user. It will inevitably cause issues in the long run and that’s the complete opposite of having benefits of auto update.
I totally understand his frustration and him blaming things that are irrelevant. But it could have been easily prevented. In this case he didn’t even know auto update was failing. Thats the real cause.