-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault when not starting from within ES directory #4
Comments
I believe this happens because EmulationStation cannot find its font (as it's found from the current working directory). A fix would be to use a system font - but I don't do this at the moment as fonts and font locations are not really standardized across all distributions. I'll look in to it, though. Edit: Actually, I think Boost.Filesystem might have a function to get the executable's path, so this might be an easy fix. |
I have included a work around for this issue by generating a bash script durch the execution of RetroPue setup. It takes care for this. I will upload updated script tomorrow after some more testing. |
I think "/usr/share/fonts" is pretty standard font location. |
Yep, it'll fall back to something like /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf in the next commit. Unfortunately my RPi's ethernet port stopped working, my laptop is in for repairs, and my desktop just got powered off in the middle of a distribution upgrade. So it might be a while before I can commit. Sorry. |
I observed that when I try to start ES not from the ES directory a segmentation fault occurs. If I change into the ES directory via "cd" and call "emulationstation" from there, the segmentation fault does not occur.
The text was updated successfully, but these errors were encountered: