Like the title says. I went to boot today and at the point where the login screen should show up it now just starts flashing, alternating between a black screen and a black screen with a pointer on it. It seems like it is searching for a video mode as well and sometimes it even just came up with garbled video. Right now I am waiting for my son to wake up so he can go full on tech on it. We do have a spare video card laying around in case it is a hardware failure. Also I believe there is still a copy of Windows 7 on that machine as well.
I have two computers hooked up to a KVM switch so I can share a monitor and a keyboard between the two. The one I am using right now is the newer of the two computers. A Ryzen CPU and an ASRock B450 motherboard. The other computer is much older with a Phenom II X6 CPU. But they have both always run Fedora just fine. Also the graphics cards are the same, both having a GTX 1050 Ti. When I did the recent upgrade to Fedora 43 the graphics driver installed without issue and it was working just fine. Only this morning did this issue start.
I am unable to get to a terminalâŠ
My thoughts right now are seeing if we can boot into WIndows 7 and also swapping out the GPU. He has a GTX 3060 somewhereâŠ
Neither. MATE. Looks like it was related to an issue that my son fixed yesterday concerning bubblewrap and volumeicon not showing up. He fixed that issue but inadvertently caused this issue at the same time. The new bubblewrap had the wrong SELinux contexts. Put the right contexts back on it and now it is working again.
You can find my other thread about the volumeicon issue and how that was solved. It involved bubblewrap and he applied the fix yesterday. I didnât rebbot until today when the problem showed up. He somehow got in and looked through the logs where he saw that there were errors related to SELinux and bubblewrap. Fixed that and instantly the problem vanished. I wish that I knew how to better explain. But my son is a computer genius and I am just a hack. My troubleshooting abilities are nowhere near his at all. I was 100% going down the wrong thought path. It had nothing at all to do with hardware. And I had no idea that bwrap would come into play during boot, but that did cross my mindâŠ
Thank you for chiming in. I hope that this makes sense to you. I donât quite understand bubblewrap fully but as my son explained it to me it is a container of sorts where things can be sandboxed. Is that correct? And when volumeicon was running it was affecting a child of volumeicon. I ask him how these things work and my brain only gets so far as I have a general idea what he is talking about. I did post up a screenshot in the volumeicon thread from the github page and the fix that was applied.
Also I keep getting âblocking-2â SELinux Alerts. Just got one when I took that screenshot just now. Keeps happening. Doesnât seem to affect how things work but keeps popping up.
I asked my son if bubblewrap was new or if it was in previous Fedora versions. He said it was already there before. When I asked why it was now causing problems his answer was âglycinâ. Make sense why I get SELinux alerts when doing things like taking screenshotsâŠ
Again, he knows a lot more than me so I am just trying to pass along information. After the recent upgrade I did have issues with thumbnails and that was indeed glycin relatedâŠ
Yep, I follow your meanings.
Itâs a bit difficult to troubleshoot issues when someone else helps out a lot with your PC, but soundslike youâve got great helper and (almost) on-call IT support
I donât think Bubblewrap is set-up by default on Fedora. I donât worry about sandboxing. Using Bubblewrap might give you more problems than it solves.
Firefox does itâs own sandboxing and SELinux takes care of the rest - along with the seperation between root / sudo and normal user access.
My recommendation would be to stick with default Fedora on the defaults (with your choice of desktop).
On the other hand I learnt about Linux by doing unneccesary things - so you win either way
Glycin certainly has been having issues. Glad it got fixed so quickly.
I really donât know anything about bubblewrap. It did come up when I was looking at the volumeicon issue doing a Google search about it. Also glycin came up when I had the thumbnail issue. I donât know about Fedora 43 at this moment. Maybe I should have waited a bit longer to upgrade until they got some of the bugs ironed out. Never had this many issues with an upgrade before. But hey, live and learn. As far as whether or not bubblewrap is a default I have no idea. I didnât set anything to make it part of the OS. Maybe I just never noticed it because I never had any issues with it before. All of a sudden with 43 I started having a lot more issues. Oh well. Hopefully tomorrow the only issue will be the annoying SELinux alerts that pop up when I take a screenshot. Never know what to do with those alerts anyway and usually over time they disappear.
My son just has a much better understanding of things. I am forced to use Google to see if there is something I can do and that does not always work. For example, I could not get into a console while trying to boot up. He edited GRUB, put âsingleâ in there to go into recovery mode and then he tracked down the problem from the error messages. I was unable to do that. So yeah it is awesome to have a tech living in the same household like that. Makes life a lot easier because I doubt that I would have figured it out.
Other info told me to edit GRUB but didnât mention using âsingleâ to get into recovery mode. Also they said I could get into a console by hitting Ctrl+Alt+F3 but that did not work. He knew exactly what to do and it worked.
A bit of a timeline for my upgrade to 43. First I saw that 43 was out so a few days ago I decided to go for it. Previously I would have had my son do the upgrade but now I do feel comfortable following the instructions provided by Fedora. It is quite easy and it went well.
Then after getting both computers upgraded I started to see the issues. First was the issue of thumbnails and I found the solution to that online (glycin-thumbnailer). Then came the volumeicon issue and there were no solutions posted. So I asked my son. At first he thought that he had it figured out, but that did not in fact fix the issue (he had gotten a suggestion from Chat GPT which was wrong). After a couple of days he figured it out after looking at a stack trace. Bubblewrap was in fact the issue and there was a fix. He installed the fix and it worked. The only problem was that we didnât reboot. Somehow the fix worked just fine on the newer computer but he did clean things up a bit today. The issue with the boot not getting to the login screen reared its head this morning when I booted up the older machine. Had we rebooted yesterday we would have figured that out sooner. And I did not immediately tie the volumeicon fix to the boot issue. But after getting into recovery mode and seeing the errors he did. Hooray!
