Skip to content
This repository has been archived by the owner on Jul 19, 2022. It is now read-only.

Glest fails to create a user .glest directory and fails to crash when it cannot launch. #298

Open
Jammyjamjamman opened this issue Apr 8, 2019 · 3 comments
Labels
bug Something isn't working priority: high

Comments

@Jammyjamjamman
Copy link
Collaborator

Jammyjamjamman commented Apr 8, 2019

If glest cannot access resources e.g. user files, it stops working but doesn't crash. This means glest has to be killed using kill -kill <glest-pid>.

It also fails to generate a .glest user directory freezes soon after due to this.

@Jammyjamjamman Jammyjamjamman changed the title Glest fails to create a user .glest directory and fails to crash when it cannot launch. Glest fails to create a user .glest directory and fails to crash when it cannot launch. Apr 8, 2019
@Jammyjamjamman Jammyjamjamman added the bug Something isn't working label Apr 8, 2019
@andy5995
Copy link
Contributor

andy5995 commented Apr 24, 2019

I think that might be related to this:

andy@oceanus:~/Downloads$ ./Glest-2.0-x86_64.AppImage

File NOT FOUND, can't open file: [/home/andy/.glest/glestuser.ini]

shows in the terminal, nothing happens. no crash, doesn't go back to the prompt.

@andy5995
Copy link
Contributor

That should be easy enough to fix, btw. I wrote a function that'll first check for the existence of a directory, and create it if it doesn't exist: https://github.com/theimpossibleastronaut/rmw/blob/master/src/utils_rmw.c#L36

Another option is to use the boost library... But I tend to think there may already be a function in the existing code base that does that (I never had that problem with MegaGlest).

@Jammyjamjamman
Copy link
Collaborator Author

Just thought I'd leave an update here: afaik, @mathusummut has a plan to replace current file loading/ saving code with something better on this project, which is why a bugfix is not being rushed out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working priority: high
Projects
None yet
Development

No branches or pull requests

2 participants