Description of problem:
Select XFCE-x8664 Install with no Swap Specified
Version-Release number of selected component (if applicable):
repeated 2x and did not occur when swap was present
Steps to Reproduce:
1. boot installer
2. choose an HD layout with no swap
3. Choose XFCE to install
crash at package xml-common
How much memory do you have?
Standard Test Default 1024MB with 12GB HD. and 1.98GB for swap
When you had no swap specified (despite what you say in comment #2), did anaconda give you a warning indicating you had no swap and that might cause problems?
Yes Sorry Chris it was a 12.28GB HD with 1024 of Memory. /boot was 500mb and /was 11.78gb and no swap. There was no warning popup except that on the main trunk of anaconda gui the partitioning PushButton Text read "warning checking software partitioning" or something close to that. The Begin Install Pushbutton was not greyed out and pressing it started the install.
Created attachment 730516 [details]
tty1 screenshot at crash
Created attachment 730517 [details]
tty2 screenshot - running top at crash
Created attachment 730518 [details]
tty3 screenshot at crash
Created attachment 730520 [details]
tty4 screenshot at crash
Created attachment 730521 [details]
tty5 screenshot at crash
Created attachment 730522 [details]
tty7 screenshot - Gui Screen at crash
Chris you now have a screenshot of every tty at crash
Just tested and gnome install faults at some point.
testing KDE and it has yet to fail, but it is installing very slowly.
Discussed at 2013-04-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alpha-blocker-review-4.2013-04-03-16.01.log.txt . Rejected as a blocker: this is essentially a self-inflicted OOM situation, and that doesn't hit any of the Alpha criteria. It would be nice to have a warning about potential OOM when installing with no swap and low system RAM, but it's not a blocker issue.
with 2048 MB Ram to VM this issue does not occur ; Also does not occur at 1536 MB ;
Turns Out 1280MB is also enough. This should probablt be tested again once closer to final and make sure that no swap install meets memory requirements established. yadda yadda yadda
If I try to reproduce this, I see a message on the hub saying "Warning checking storage configuration" and then if I go into the storage spoke again, I see the usual bar along the bottom that tells me I've not created a swap partition.
So, there is a message for this. It's just not visible enough. I'm going to treat this bug as a request to make the message more visible.
I believe 769a583f7ec94e96d7e49e63360fff0970f3ff3c on master fixes this. It was also being tracked by bug 975840.