Bug 891127 - Live CD hangs or freezes on systems with < 1.5 GB RAM
Summary: Live CD hangs or freezes on systems with < 1.5 GB RAM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-01 23:12 UTC by Bharath Mohan
Modified: 2013-08-01 04:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 04:38:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The mentioned "log out" message screenshot (25.59 KB, image/png)
2013-01-01 23:12 UTC, Bharath Mohan
no flags Details

Description Bharath Mohan 2013-01-01 23:12:36 UTC
Created attachment 671150 [details]
The mentioned "log out" message screenshot

Description of problem:
The Live CD has a tendency to hang or completely fail when running on systems that have less than 1.5 GB of RAM despite a listed minimum of 1 GB of RAM.

Version-Release number of selected component (if applicable):


How reproducible:
Shouldn't be too hard.

Steps to Reproduce:
1. Find a machine with less than 1.5 GB RAM/use a VM
2. Boot up Live CD/Image
3.
  
Actual results: Hangs, freezes


Expected results: Not hanging and freezing


Additional info: Tested on an (old) physical system and with Virtualbox.

For example, if at the opening menu, one selects "Install to hard drive," the installer will not even open. GNOME 3 will also not start up, and seems to cause some kind of chain failure that forces a full log out (The specific message is something along the lines of "The system has encountered an unexpected error. Please log out and try again."). Not sure if this is a GNOME 3 problem/message or not.

Comment 1 Fedora End Of Life 2013-07-04 00:41:19 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2013-08-01 04:38:26 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.