Unable to boot - "cannot open Front File True"

[Yora0]

When I try to boot, I get the error message "cannot open front file true". When I press the power button, the promt goes through a list of things it checks, then the computer powers down.

The last thing I did was to download the catalyst driver and install it, requiring a reboot.

Anything that can be done to repair that?
I do have a Live USB HD with the same version of Fedora.

[Argedion]

I do not believe the error has anything to do with your computers ability to boot. I get the same error and my computer boots fine. Seems to me that your having another issue and it could be your driver

Sent from my PC36100 using Tapatalk

[Yora0]

I'll look into other thing then.

Now, I do have a live usb and through it I can mount the drive that holds the damaged os.
Can I use commands in Konsole to fix things instead of using repair mode? This would have the major advantage that I could also have a web browser open simultaneously and don't have to write down the entire instructions every time I want to try something.
So far I can navigate the directories and even open /etc/default/grub with Kwrite, but I can't save the changes. Is there a way to enable that?

And is there a way to simply restore the original state of the graphics driver that was included in the installation?

[sea]

Dont use kwrite on system files !!!
That is like opening boot.ini or system32.ini with M$ word...
Use a simple text editor like leafpad or gedit.

Editing system files with krwite, abiword, librewrite... this WILL cause errors on your system.

[pikul]

I get the same message but my system boots and works fine, i still would like to know what that message means????? anyways, at grub menu just add a number 3 at the end of the kernel line, logon as root and run the xorg -configure command to create a new configuration file.

[sea]

i get a very smiliar issue after installing another fedora minimal install to another partiton at first boot.
This is caused by a shared /boot and customized grub2 splash screen, using a custom built font.
At least thats the reason on my system.

[DBelton]

edit your /etc/default/grub file, and on the lie with GRUB_CMDLINE_LINUX there is a parameter that says SYSFONT=True (or it might not even be on there, I forget now)

But just change that to a font that does exist. Previous versions used SYSFONT=latarcyrheb-sun16

Either change True to latarcyrheb-sun16 if the SYSFONT= parameter is already there, or add the complete SYSFONT=latarcyrheb-sun16 parameter if it doesn't exist.

Your GRUB_CMDLINE_LINUX should look similar to this afterwards:
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8

Then run

grub2-mkconfig -o /boot/grub2/grub.cfg

This will get rid of the "cannot open front file true" error message, but not being able to boot is a different problem. The "cannot open front file true" shouldn't keep it from booting.

[Yora0]

I have the system repaired now, but I also still have that error message. Had indeed nothing to do with the problem at all.
Doesn't seem to cause any actual problems though.

[nothing2lose]

I have the same problem too.
I can't repair.
I have just installed my fedora 17.

[nothing2lose]

After i installed new fedora 17. the first time i reboot, it's still message "cannot open font file true" but i can login fedora.
Why does message still?

[sentabi]

Originally Posted by nothing2lose

After i installed new fedora 17. the first time i reboot, it's still message "cannot open font file true" but i can login fedora.
Why does message still?

look at post above (http://forums.fedoraforum.org/showpo...63&postcount=7)

[JakeR]

Originally Posted by DBelton

edit your /etc/default/grub file, and on the lie with GRUB_CMDLINE_LINUX there is a parameter that says SYSFONT=True (or it might not even be on there, I forget now)

But just change that to a font that does exist. Previous versions used SYSFONT=latarcyrheb-sun16

Either change True to latarcyrheb-sun16 if the SYSFONT= parameter is already there, or add the complete SYSFONT=latarcyrheb-sun16 parameter if it doesn't exist.

Your GRUB_CMDLINE_LINUX should look similar to this afterwards:
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8

Then run

grub2-mkconfig -o /boot/grub2/grub.cfg

This will get rid of the "cannot open front file true" error message, but not being able to boot is a different problem. The "cannot open front file true" shouldn't keep it from booting.

Hi

I have this bug (#799401) on a custom livecd.

The problem is solved in this commit:
http://git.fedorahosted.org/git/?p=a...f3b9451ae8e0f0

I have anaconda-17.29-1 on my livecd, but the problem still exist? Why?

[leprendun]

Sea, how did you fix the issue? I'm a linux newbie and having a similar issue.

Originally Posted by sea

i get a very smiliar issue after installing another fedora minimal install to another partiton at first boot.
This is caused by a shared /boot and customized grub2 splash screen, using a custom built font.
At least thats the reason on my system.

[DBelton]

I showed above how to fix the "Can not find font file True" error, but here it is again:

Do all of these commands as root user:


So, first off, edit your /etc/default/grub file and add the follonwing to the GRUB_CMDLINE_LINUX line:

SYSFONT=latarcyrheb-sun16

(latarcyrheb-sun16 was used on previous Fedora versions)

You should now have a line in your /etc/default/grub that looks similar to this:

GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8

Also, you need to change the file /etc/sysconfig/i18n and make the same change there.

This is what your /etc/sysconfig/i18n file should look like once done (assuming you are using US English as your language)

LANG="en_US.UTF-8"
SYSFONT="latarcyrheb-sun16"

Once this is done, then you need to rebuild your /boot/grub2/grub.cfg file to for grub to pick up the changes.

grub2-mkconfig -o /boot/grub2/grub.cfg

Now you should not have the error when you boot.

Edit:
Fixed typo

[Jamwa]

I believe you meant /etc/default/grub and not /etc/defaults/grub