Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Every time I try to start Tux Racer a window pops up for half a second, then X crashes, and I end up being returned to the GDM screen. Aside from any possible explanations for this crash, shouldn't there be a core dump saved somewhere or a message than I can analyze? I've tried running it after using the bash command ulimit -c unlimited, but I still don't see a dump file anywhere.
Distribution: PCLinuxOS 0.93 and 0.92, Vector sometimes
Posts: 825
Rep:
If you open a console, and start tuxracer from the console, using the command tuxracer, once the program crashes, the console should still be open and contain some error messages for you to analyse.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
tc said it was crashing his X, so the console would
be dead too.
i guess he could start it in a console with standard
error redirected to a file.
it almost has to be some feature in X crashing, like
the glcore module. you can comment that module
out in your XF86Config, by the way, and start tux without
gl, and see if it crashes.
...and if you want more verbosity in your Xfree logging, try starting X as "startx -- -verbose 0 -logverbose 9". This should dump minimal info on the commandline, but max info in the logfile.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.