I guess so. The popup is annoying but I’ve just been looking into how to filter notifications (rather than turning them all off). Turns out there are extensions out there that will do this which I wasn’t aware of before.
1 Like
Take a look at this thread. I had issues that were caused by bubblewrap. I would heve never figured out the fix myself but thankfully my son is a computer genius and tracked it down by looking at a stack trace.
1 Like
Unfortunately they start talking about things that are too technical for me.
I am now getting other crashes as well that seem to be related to bwrap. Latest one is Python crash - “python3.13 killed by SIGABRT”. This one doesn’t have a backtrace section in the problem reporting though. It does mention bwrap in the container_cmdline though.
This system is becoming unusable really. I am getting multiple different apps (I think mostly flatpak apps) that keep bringing up a popup window that states something like “this app is not responding” and then giving a wait or quit button. The quit button does nothing though - the app just continues to sit there unresponsive.
Unfortunately some of the apps I want to use only have flatpak versions.
You could install KDE or Cinnamon desktop. The problems you are having are in the current release if Gnome.
You can have two or more desktops installed, for example
sudo dnf install plasma-desktop
then log out of Gnome and select KDE or Plasma from the login manager.
I’ve already tried KDE and Cinammon. I didn’t like either of them. Gnome is the only DE I like on Linux.
If your system needs to be more game orientated you might have a look at Nobara.
As you can see they still offer F42 to adjust their system to the newer version.
Taking it easyier while you want to focus on Gaming will be a good idea.
Thanks but I already tried Nobara and Bazzite and found them even buggier than Fedora. I then decided I am only sticking to the main distros and staying away from all these others. I don’t actually game that much anyway, I was just installing stuff I will want at some point. I haven’t even opened Steam yet. It was more a case of trying the so called gaming distros to see how they differed from standard distros. I came to the conclusion that for someone like me where gaming is only minority of what I use my PC for they are pointless especially as they seem to insist on gareish themes and colours. Not for me thanks.
3 Likes
Maybe I can ask my son about it today. I am not exactly sure what he did. I do know that he downloaded something from GitHub, unpacked it and then replaced bwrap with the bwrap that was in the download. Sorry that I can not be more specific, but like you I do not understand a lot of the technical stuff. All I know is that my son is much smarter than me when it comes to this stuff and he figured it out and fixed the issue that I had with bwrap.
I will see if he is in a better mood today. Yesterday he got angry with me for bugging him with so much Fedora stuff. Oh well…
Also this could be a completely different problem because in my case bwrap was not crashing, it was simply preventing volumeicon from showing up on the desktop.
I keep getting bubblewrap crashes on F43 Workstation as well; locking the screen while Steam is running seems to be a sure way to trigger one. See also RHBZ.
@walters Any ideas what’s going on? Could it be related to glycin?
I am still having issues with bubblewrap as well. Mainly when downloading PDF files and it throws up an SELinux alert. The PDF still downloads just fine. But something is going on.
This morning after booting up I did a ps -ax command and saw two entries for bwrap. Both said “bwrap --unshare-all --die-with-parent --chdir / --r”. Then a bit later that was gone when I did another ps-ax.
Finally when I went to test for the PDF download bug (which I do have a report in at Bugzilla) I had no issue actually copying and pasting a PDF file from a folder on to the desktop. But when I tried a download the SELinux alert popped back up. This time it was only four things…
And when I did another
ps-ax, this time it came up with…bwrap --unshare-all --die-with-parent --chdir / --ro-bind /usr /usr --dev /dev --ro-bind-try /etc/ld.so.cache /etc/ld.so.cache --ro-bind-try /nix/store /nix/store --tmpfs /tmp-home --tmpfs /tmp-run --clearenv
I have a suspicion that it is related to glycin but that is all it is. Definitely buggy.
Right now I am working a new angle and trying to see what bwrap is doing. Any way that you can post up any relevant information about seeing a bwrap line when you do a ps-ax on a terminal. Maybe before you think that it is going to crash and then after…
Edit: I posted up that info in the previous post… Before and after the SELinux alert issue. However, if bwrap is crashing for you then it should not show up in the after part of it…
I am wondering if you can change SELinux to permissive before booting and then see what happens. I don’t know the specifics of how to do that other than editing a certain file…
Looks like that information is here…
I have setroubleshoot installed, and haven’t seen any bubblewrap-related alerts so far; yours might be a separate bug.
In any case, I doubt there’s much we can do unless a maintainer chimes in.
I agree. Also I don’t have the level of proficiency that my son does. He was able to look at a stack trace and figure out the previous issue with bwrap and volumeicon. Using journalctl with the --since option can at least get you some information after a crash. See a coredump or whatever. But that is beyond me…