I have this one system (that is now, alas, in productive use) where I could reproduce this two or three times before finding a "workaround". To actually force the issue, it seems, I had to set the password ASAP. Once the install screen shows up, press the button, set the password, BAM. If the screen shows up and I waited a while, it worked. But I've never had the time to narrow it time to how much time actually seems necessary. I tend to think anaconda is using cracklib from the installed system and if you're trying to set the password before that is installed it crashes. But that's a very wild guess :) On Wed, Nov 28, 2012 at 7:37 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > On Wed, 2012-11-28 at 12:26 -0600, Nonamedotc wrote: >> Hey! I have seen this once or twice. I *assumed* I "pulled the plug" >> on something. I think the most recent one I saw was when I was trying >> to install using RC1 on bre metal (a couple of days ago). No ABRT >> screen is shown. Everything just dies and I reboot. >> >> Frequency: I might have seen it may be twice .... > > If you hit it again, can you try and provide the info requested in the > bug? From the description, it sounds like ctrl-alt-f2 is still available > (or I guess Kamil might have been sshing in or smth). > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > > -- > test mailing list > test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe: > https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
