Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 851356 - error: file '/grub2/locale/en.mo.gz' not found
Summary: error: file '/grub2/locale/en.mo.gz' not found
Keywords:
Status: CLOSED DUPLICATE of bug 817187
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-23 22:09 UTC by Frank Simmons
Modified: 2012-08-25 11:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-25 11:00:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Frank Simmons 2012-08-23 22:09:57 UTC 
Description of problem: error message appears just before the screen clears and the grub menu appears.


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


How reproducible: every time


Steps to Reproduce:
1. turn on the computer
2. allow bios to parse devices
3. error message appears
  
Actual results:


Expected results:


Additional info: I have used Ubuntu as an operating system before and wanted to see how Fedora had changed over time. I downloaded the release yesterday and had some issues with the install. Once I finally got a good install, I thought that all errors were handled until I noticed this error message just before the grub menu came up. I looked at some previous bug reports and haven't seen a real fix yet. Is one coming? Or am I just going to have to use a work-around?( Which I don't like to do )
Comment 1 Mads Kiilerich 2012-08-25 11:00:07 UTC 

*** This bug has been marked as a duplicate of bug 817187 ***
Note You need to log in before you can comment on or make changes to this bug.