(SOLVED) Emulation Station won't boot after font change
-
Hello! I'm very new to the Pi world and recently got a Pi 3. I'm not that great at coding, and I'm trying to take baby steps to maximize the customization of my RetroPie.
Using "futura" as a template, I decided to see if I could at least tinker with fonts. I replaced the default font the easy way (renaming the default with a "1" after it and naming the new font the old name) and restarted Emulation Station. After the boot, the new font was set! Not content with how it looked, I changed it again using the same technique, although when I restarted Emulation Station, it wouldn't boot. The RetroPie load screen happens, but not the Emulation Station load screen. I'm just left stranded on the "pi@retropie:~$" screen. Tried several reboots and watched for error messages, but I received none.
What happened? All I did was swap font files. I didn't mess with any code what-so-ever. How do I get Emulation Station to boot back up? I even went back and switched the font to default again. Still nothing!
I've been very careful not to tamper with code I don't fully understand yet, so I'd appreciate any advice. Thanks!Pi Model or other hardware: Pi 3 (B, I believe)
Power Supply used: XCX USB cable. 100-240V 50/60Hz 5V = 2.5A
RetroPie Version Used: Unsure
Built From: Pre made SD Image on RetroPie website
USB Devices connected: Keyboard and controller
Controller used: Logitech Precision USB
Error messages received: None -
What happened?
I'm not sure. I never changed the font of a theme, just some xml files and images.
How do I get Emulation Station to boot back up?
Change the font back to a working one or delete the theme folder/change the selected theme in the corresponding config
-
What happens if you run
/opt/retropie/supplementary/emulationstation/emulationstation --debug
?
Maybe you get an error message? Have you checked the contents of
~/.emulationstation/es_log.txt
?
-
Thanks for responding!
I didn't realize that es_log.txt was an error log (again, I'm very foolishly new at this), and I've located the problem! The font in question needed to be a "TrueType font," and any other type like an OpenFont is apparently cause for error, which I didn't know. I cleaned out the folder and reset all default properties, and now it works like a dream!
You guys are the best! Thanks!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.