On 03/11/13 05:50, Fernando Cassia wrote:
On Sun, Nov 3, 2013 at 2:38 AM, Joe Zeff <j...@zeff.us <mailto:j...@zeff.us>> wrote: You may have run afoul of this: https://bugzilla.redhat.com/__show_bug.cgi?id=980543 <https://bugzilla.redhat.com/show_bug.cgi?id=980543> Yes, it refers to 18-19, but it hit me on an upgrade from 17-19. Also, the maintainers are claiming that it's caused by a process that's just taking longer than expected to complete. My suggestion is that you try using distro-sync once you get to a CLI. Thanks for the tip. Yeah it looks like it :-/ Seriously, if the devs cant create an upgrade GUI that gives some visual feedback about what is going on, they should reconsider their line of work. I would suggest agriculture... or arts.... fields where "nothing happened for hours" can be actually desirable or intended... FC
I remember that I said this as part of a post on another subject on the rpmfusion-users list in August. That was f17 > f18:
No problem with the upgrade, starting from a fully updated system with all relevant repos enabled. Really very impressive, but the screen display after the reboot into it was useless; only a static blue bar while intense disk activity went on for around 90 minutes. Hitting 'escape' brought up the rolling upgrade log, but I only realised I could do that after a long time watching nothing change and wondering about infinite loops.
John P -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
