I used to have my son do the upgrades but now I do them. This last one went surprisingly well. That is until I started running it and the issues started creeping in. First I noticed the icon issue and fixed it. Then I noticed the issue with volumeicon not showing up and it took my son a couple fo days to fix that (related to bubblewrap). And then finally he didn’t do a full test on the volumeicon/bubblewrap fix so the next day I had a boot issue. Everything seems to be working OK right now with the exception of SELinux and I do have a thread up about that and hopefully that will get fixed soon. I love using Fedora and have not seen Windows in years. But this release seemed to be more like a beta, not fully tested. I think next release I am going to wait a bit longer to do the upgrade…
Here are links to my son’s bug report concerning volumeicon and also his comments on the github page concerning bubblewrap and volumeicon. I really don’t understand his comments because he is a computer genius and I am a hack. He started programming in OS/2 on my 486 DX266 when he was only ten years old.
I always wait for the dust to settle on a new release and then upgrade my systems from least important to most important. (I have a home lab).
At this point I’m happily running a router/firewall and KDE desktop systems.
I think I will just wait a bit longer next time. I just saw that 43 was out so I went for it. And the upgrade itself went very well. Right now the only issue that I seem to be having is with the SELinux alerts. But they are not affecting funtionality at all. Just annoying. I do have another thread up about that.
Just did a quick screenshot and sure enough the alert came up… AVC Denial. Had that one before and eventually it went away. When I look at details it is “blocking-2”, which doesn’t mean a whole lot to me.
It’s gone through the same testing as previous releases. That does not, however, mean that every package in Fedora has been tested. volumeicon would certainly not be part of the test matrix—it’s not part of any of the release blocking artefacts that are produced.
Can you please click “show” to see what details it shows about the denial? setroubleshoot usually suggests a fix, or helps to file a bug:
For general information, this is what is tested before a Fedora release:
The more people we have testing, the more bugs get caught.
I really appreciate the community here. It is a community effort that makes things tick. It’s also great to have my son as my personal computer tech. Give me a minute and I will get it to come up again and then screenshot the details. Someone said that they are already working on a fix for the SELinux issues…
Not really trying to have duplicate threads about the SELinux issue but here is that screenshot with the details…
I knew volumeicon would not be currently tested because it has not been updated in some time now… My son told me that. But what he figured out was that the icon was not showing up because of issues with bubblewrap. And I also did have the glycin related thumbnail issue which I fixed by installing glycin-thumbnailer.
You know, I used to consider myself pretty computer proficient back about 30 years ago. At that time I had a 486 DX2 66 with 16 meg of ram and two 540 meg hard drives. On that computer I was running three different operating systems… Dos/Windows 3.11 was one. OS/2 Warp was the second and finally I got Slackware running on that as well. I remember when I had to do the config file to get X11 working with my Hercules video card which had all of 1 meg of video ram. LOL. Never went to Windows 95. In 2008 I finally built a new computer with a Phenom II X2 545 processor. The Biostar motherboard allowed me to unlock that to a four core, but that we never stable so I went back to the dual core. Now that computer is long gone. The computer I am using right now is running a Phenom II X6 processor and I have another computer running a Ryzen processor.
I guess what I am saying is that I am trying to stay relevant and up to date. But my knowledge base at the moment is limited. I will try to learn as much as I can. But I will never go back to WIndows ever again. Perfectly happy using Linux.
I think I said something similar around 2016; and never say never 
I just put some information from your son’s bugzilla ticket here to see what’s all about:
James Coonradt 2025-11-11 03:39:50 UTC
Additional Information:
I am using the MATE+Compiz spin, and have not tested it on other Desktop Environments
To be honest, I’m maintaining volumeicon for legacy reason. Project is very legacy indeed, based on Gtk2, and since those times package existed for usage mostly in early Xfce desktop (now Gtk3 though). Therefore conflicts should not wonder.
Last release 0.5.1 of upstream is from 2015. Maybe migration of volumeicon for Gtk3 is not really expected neither announced anyhow, sorry. :o(
James Coonradt 2025-11-11 19:49:52 UTC
volumeicon is not a gtk2 application, it links to gtk3.
Because nowadays wayland instead of Xorg see also Volumeicon crashes on Wayland/Sway/Waybar · Issue #79 · Maato/volumeicon · GitHub .
Issues list of volumecontrol:
And now the Answer to your question from the Title (I changed it, to show the real picture)
-
Is 43 a hot steaming mess?
To this question I have to say, no it is not F43, which is the mess, it is the DE (Desktop environment) you are using. -
Is F43 Mate Compiz a hot steaming mess?
Unfortunately software is aging, as we do. If there are to much new technologies to keep up with, this kind of project get abandoned just because of never ending issues, missing manpower, or the missing same love, as they did put in when the software was newer.
p.s.
I also moved from Windows to Linux and my First productive DE was the Mate Desktop. It was quite similar as Windows7 when I left. Everithing had his place and everithing worked as long you used x11.
However with the fast advancing changes for the Gnome 4 Desktop, the mate desktop lost attraction because of issues which not had preference as the “Cinnamon Desktop” had (The younger Brother of Mate; the default of the Mint Project.)
If you want to have all this issues fixed now, ASAP, you will need to support the Mate desktop financially and or Sponsor a Developer, which has the know how to fix all this issues. Why I do tell you this? It is because Fedora Linux uses the Mate Desktop as a Spin, this means it is as it is upstream = Mate Project. It is not really relevant for the Fedora workflow and it’s errors are also not considered as obstacle when releasing a new Fedora Version. Unfortunately for older hardware, but I guess you got the picture I tried to paint for you, right?
- An alternative as already mentioned above would be the “Cinnamon Desktop” . We do have also a Live ISO for that which you could ask your son, making a pen drive which allows you to test before installing it.
As an Idiea how fast and when exactly you have to look for the beta version you can use the command:
hostnamectl |grep "OS Support Remaining"
OS Support Remaining: 5month 3w 5d #F42
#or just
hostnamectl #for all entries.
p.s.
I passed already the 50ties and I do understand the comfort of something you’ve gotten used to 
I am getting some very weird errors now. I was having issues with SELinux and it seems those issues are persisting even after an update to those packages today. First off I just did a screenshot and it didn’t show up on the desktop. So my son did a refresh and lo and behold they were there. OK, then the next time I do a screenshot it goes right back to an SELinux alert again. Here is that…
Still “blocking-2”.
I was going to report but then when I tried that my son told me that I needed a Bugzilla account in order to do that. So I just gave up. Why make it so hard to report? I still might do that. The issue persists.
Well, I have to say that right now 43 is working pretty damn well. Also a strange thing happened tonight. I applied what I believe are the same updates to my “new computer”. I have two computers hooked up to a KVM switch so I can share a keyboard and monitor. Earlier today after doing the latest updates on the older computer, I was still getting those SELinux alerts when doing screenshots or copying and pasting photos. However, tonight I am not having the issue on the newer computer. So I will see what happens tomorrow when I go back to the other computer. This has my head spinning a bit but frankly I am happy not to see those SELinux alerts all of the time. I also did file a bug report but I have not checked on that again.
If you want some help from us, we would need to get the “details” of the SELlinux alerts.
You get them while clicking on details (see screenshot you posted).
Then please paste it as text, see in menu </>. So we can cat and paste to help you search.
Well, as of this morning the SELinux Alerts are only coming up on my older computer and not on the newer one. Which is a bit strange because they both get updated daily and also they both use the same graphics card. I am not trying to put too much information in this thread because I have a separate thread about the SELinux issue.
The SELinux thread is here: