[youngheart80]

Hey all.  First post and before getting into the problem, just wanted to say I've really been enjoying the game and say thanks to all who support it.  

Now, my issue - first, system specs:

OS: Ubuntu 9.04 x86_64
fs2 Build: Compiled from SVN 5385(?)  - (compiled about 15 hours ago, but I forgot the exact SVN revision it listed when I checked-out and I'm not home at the moment to look and see)
Laucher: YAL 0.1.4 (also compiled from SVN)
Mods: MediaVP 3.6.10 ONLY, just retail FS2 with the pretty upgrades.

Problem:
I'm running the game in 1028x786 but my standard desktop resolution 1920x1080 (wide screen monitor, but that's not the problem).  When I exit the game, the resolution doesn't reset back to the 1920x1080.

What I've Tried:
I looked first on some Ubuntu forums to see if it might be a system error - it was suggested that this might be caused by a game/program "crashing" on exit and preventing the computer from resetting the resolution.  The recommended course from the forum post was to run the program from console and look for any error messages.  Sure enough, segmentation fault message upon exit of the program.  Also ran without MediaVPs and at different resolutions - same results.

I went ahead and compiled and ran a debug build to try and see if anything would show in the fs2_open.log, but I can't seem to find the log - not showing in /FreeSpace2/data that I can see anyway.  (I think I built the debug right - still new to Linux so I could have screwed it up.)


Any thoughts on where the log file might be (searched the folders, but came up with zilch)?

Further, any thoughts on the seg fault?

At this point I'm looking more for discussion/education rather than a solution, sort of a "help-me-help-myself" kind of approach.  The reset of the resolution is easy and I enjoy the game enough that it doesn't put me off.  I'm hoping I can learn enough to start contributing to the project.  Anything that might help is appreciated.

Thanks
yh80

[General Battuta]

I don't have the code know-how to help you out (way out of my league), but let me just say welcome! Hopefully we can get you working on something.

I reckon somebody with real know-how will be along shortly.

[chief1983]

When you run autogen.sh, pass it --enable-debug, and it should say debug is enabled at the end.  Then you should have a debug build.  Plus, in /code/, the build would be fs2_open_d instead of fs2_open_r.

I've just become aware of what's now several Ubuntu users having issues.  This will be looked into.

You might consider running in windowed mode with -window, if you're not going to play in a very high res.  Although, you could probably run the game at the native resolution, unless your system is somewhat old.  Oddly, others are having crashes with regular builds, and not with the debug build.  Those users are using 3.6.10 base builds though, something might have changed between then and the latest trunk code.

[youngheart80]

Well, good, I did build the debug version right.  Still, haven't found a log.  Is one only generated if the system actually crashes during game play, or should there always be one regardless?

On the 3.6.10 build, I'm a little ashamed to say I haven't figured out how to get the binary to work - I think I may have seen my problem in another thread.  Going to go test it out now.

Thanks for the replies.

[chief1983]

There should always be a debug log when running debug builds, it starts as soon as you run the game.  If you have locate installed, try using that to find it, or a recursive 'find' on possible directories.  It could be in your user folder, in something like .fs2_open or something, check for any folders like that.