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 859307 - GRUB2 error: file '/grub2/locale/es.mo.gz' not found. [GRUB2 Fedora 18 Alpha KDE]
Summary: GRUB2 error: file '/grub2/locale/es.mo.gz' not found. [GRUB2 Fedora 18 Alpha ...
Keywords:
Status: CLOSED DUPLICATE of bug 817187
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-21 04:05 UTC by xset1980
Modified: 2012-09-21 08:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-21 08:47:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
GRUB es.mo.gz error F18 (23.21 KB, image/png)
2012-09-21 04:05 UTC, xset1980
no flags Details

Description xset1980 2012-09-21 04:05:57 UTC
Created attachment 615275 [details]
GRUB es.mo.gz error F18

Description of problem:

-Every time grub2 loads before showing its menu it shows this error message: error: file '/boot/grub2/locale/es.mo.gz' not found


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

-System up to date at moment of report this bug
-Fedora 18 LiveCD KDE Alpha up to date
-grub2-2.00-5.fc18.i696

How reproducible: Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Same bug that https://bugzilla.redhat.com/show_bug.cgi?id=817187 not fixed yet.
Attach Screenshot, but in this case is with es.mo.gz language.

Comment 1 Mads Kiilerich 2012-09-21 08:47:21 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.