On 5/3/25 10:05 AM, George N. White III
wrote:
On Fri, May 2, 2025 at 1:16 PM Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:Today, on attempting resuming after suspending my system before boarding
my plane. My system hung.
So I powered cycled, and since I have not done an update in over a week,
instead of logging into my graphical window, I switched to Term2, logged
in as root and ran "dnf update".
I have done this a lot of times when I hung like this. Don't log into
graphical window and then have all the apps start and still should do an
update.
So ~87 updates and a new kernel. Big deal. But it hangs on a scriptlet
that looked like selinux-policy.
On recent updates here, the selinux update took quite a long time with nosigns of life -- patience was rewarded with a completed update.
I felt 45min was a bit much of waiting for Gedot.
So I switch to Term3, log in as myself and run top. I see restorecon
eating up 96% cpu. I wait 30min. Still not done.
I go to my Win10 system and google Fedora and restorecon eating up
time. Found bug 1832327 on F35! The poster killed restorecon, so I did
too.
Obviously update finished. I rebooted and logged in.
Is there something I should do/check since I killed it?
"restorecon" has a "-n" (passive check) option
Just tried that and system came back immediately. I checked /var/log/messages and nothing reported there from running it.
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
