They are popping up every time I download a photo or I save a png screenshot. It isn’t affecting performance at all but it is annoying…
1 Like
I know people say not to turn off SELinux, but this is really annoying. Popped up tonight when I was downloading a PDF file. Also it pops up when I copy and paste a photo. Whatever it is doing is ridiculous. So far I am not very impressed with 43… I believe the message I get is something like AVC Denial…
In the past it seems like this has corrected over time. Maybe it will.
I guess you are using a spin, not Workstation or KDE? I am having this only on XFCE spin.
Maybe the flagships are better configured and maintained? And these default policies need adjustments for other environments?
Then it would be better to file a bug report?
Fedora Workstation simply doesn’t install the setroubleshoot package so any selinux issues are not shown to the user. That doesn’t mean they are not there.
it seems a fix is underway:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f9000e422c
2 Likes
Yeah, I figure it will probably get fixed soon. At least I hope so… Got this again last night while downloading a PDF file as well. It really is annoying.
Not sure what a “spin” is. My Fedora uses MATE.
you could run the “sudo dnf upgrade …” command from the above link in an terminal and soon should be now
Is there any reason to use upgrade vs. update? I always assumed that upgrade was for new versions vs. just updating packages. I usually do the update via dnfdragora but sometimes I do them off the command line as well using “sudo dnf update”. Since this is just more annoying than anything at the moment I just figured I would wait and it would probably right itself like it has in the past. This isn’t the first time that I have gotten those AVC Denial messages. They show up and then one day they are gone…
I really am a bit of a hack. I understand the basics but not everything that goes on under the hood…
Someone just mentioned setroubleshoot. Is that a package that I can install? Looking at that now…
Edit: Looks like I already have it installed.
LOL. I get it now. That is the part that shows up when you hit “show”… Yeah, I am slow and a hack.
Sorry. My son just told me that update and upgrade are basically the same thing. Aliases for one another… I pretty much run updates as soon as they show up. Also today I ran updates from dnfdragora. Then I went to a terminal and did sudo dnf --refresh update and more packages showed up. So I did those as well. They were mainly nvidia driver and X11 related.
Well, there was an update today that I did but it did not make things any better. Still happening whenever I do a screenshot or even just copy and paste a photo. Makes me wonder if this is glycin related? Here is todays details on the latest notification. Still “blocking-2” and something called connectto…
OK, I just filed the Bugzilla report. My son helped me set up an account so I did that. Will report back.. I meant to post the link to that but now I can’t find it. Found it…
Posted as relating to glycin. Not sure if that is exactly the case or not.
Also as you can see before it said it was related to “write” and now it says it is related to “connectto”. So there is that. It has changed.
I tried this one and it did not work… The fix that you linked to. Said it could not find that advisory. Same as before.
When troubleshooting SELinux, you should start with relabeling:
sudo fixfiles -F onboot
sudo reboot
If the issue persists, try reproducing it in permissive mode:
sudo setenforce 0
Then collect the relevant logs:
journalctl --no-pager -b -g avc
Also note that screenshots are discouraged:
2 Likes
Interesting thing just happened. I did the updates on the newer computer and now the issue has disappeared on that machine. So it makes me wonder if there were extra updates that I installed this evening that were not available this morning when I updated the older computer. That is possible. There were some X11 updates. I will check in the morning and then report back. But right now everything is working 100% on the newer computer so I am quite happy about that.
Morning update. The behavior is still occurring on the older computer but not on the newer one. Which is strange because they both use the same graphics card. Right now I am trying to look at the all the information on both computers to compare. Will just have to wait and see for now. This bug is just more of a pain than something that prevents me from doing what I want to do.