Re: Upgrading to F38, setroubleshoot-server seems to be taking a long time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 25 Apr 2023 16:10:06 -0400 (EDT)
Max Pyziur <pyz@xxxxxxxxx> wrote:

> On Tue, 25 Apr 2023, Max Pyziur wrote:
> 
> >
> > Greetings,
> >
> > Upgrading F38 on my Dell XPS 13 laptop of something like 2012
> > vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server
> > is hanging.
> >
> > Seems that it's been this way for a least 5-10 minutes while
> > everything before this has been running briskly.
> >
> > Advice?  
> 
> My upgrade halted. The computer shutdown.
> 
> I hit the start button,
> 
> the selection for kernels came up only showing F37 kernels.
> 
> I hit the latest F37 kernel,
> 
> I got a login screen with the new F38 screen.
> 
> I logged in. Browser tabs are restored. Wifi connection, though, goes 
> on and off.
> 
> I checked Postgresql installation; I have two version postgresql-14
> (F37) and postgresql-15.
> 
> As best I can tell, the upgrade aborted leaving the system in, uh, 
> challenged state.
> 
> Any advice on how to proceed here would be greatly appreciated.

Did the fedora packages for f38 get installed?
fedora-release*
fedora-repos*
If they did, you can try a distro-sync using dnf
Distro-Sync Command
       Command: distro-sync
       Aliases: dsync
       Deprecated aliases: distrosync, distribution-synchronization

       dnf distro-sync [<package-spec>...]
              As  necessary  upgrades, downgrades or keeps selected
       installed packages to match the latest version available from
       any enabled repository. If no package is given, all installed
       packages are considered.

If it didn't, try restarting the sytem-upgrade process.  How resource
constrained is the laptop for memory.  I vaguely recall the minimum
required bumped to 2 GB because lower was causing problems.  There was
a discussion of minimum hardware requirements increasing, but I don't
think it went through.

If it still has problems, try manually downloading the fedora packages
from koji
https://koji.fedoraproject.org/koji/packageinfo?packageID=9
https://koji.fedoraproject.org/koji/packageinfo?packageID=18771
and installing them with  dnf -C
And then run manual dnf updates for only part of the install packages,
so that things are done in smaller batches than the full upgrade.
At the end, you could run distro-sync.
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux