On Tue, Jun 5, 2012 at 3:59 PM, M A Young <m.a.young@xxxxxxxxxxxx> wrote: > On Tue, 5 Jun 2012, Manuel Gonzalez Montoya wrote: > >> Hi, >> >> I just did a fresh install of F17 on a ESXi 5.0 VM, and it crash on >> first boot with the message >> >> "Oh no! Something have gone wrong. >> A problem ocurred and the system can't recover. Please contact the >> system administrator" > > > Try rpm -e fprintd from a text console, as you might be hitting bug 810040 > https://bugzilla.redhat.com/show_bug.cgi?id=810040 > > Michael Young > > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org I can now confirm that it was indeed the same bug Michael Young suggested. Alternatively we can run 'yum remove fprintd' to get rid of the offending package. After reboot I got a nice login screen. Thank you all -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
