xmoto flickers just entering it.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Hi Jean,
 Thanx for getting back to me. I have since moved to hardy > Intrepid

Hence I'm getting segfaults.

Xserver-xorg is now 1.6.3+10ubuntu11

xmoto is 0.4.2-1

Few more notes

It upgraded the database, didn't run it since gutsy

It goes till the menu and then segfaults.

If you want I could run the dbgsym and report whatever happens or can stay like this for sometime and then try again. Whichever way you say.

I can't reproduce this issue with Intrepid. Are you using compiz ?

Please can you detail the steps to reproduce the crash ?

Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report.

This will greatly help us in tracking down your problem.

Hi Jean,
 Attaching the bug-report. I'm not running compiz. I'm on an in-built i845 chipset , no graphics card. See if that is the issue

Oops, sorry wrong attachment, the real thing.

I have gdb and the xmoto-dbgsym installed, if you need any more -dbgsym symbols installed please lemme know.

Thanks, but the backtrace is incomplete. Just after the segfault you've forgotten to retrieve the backtrace

After the segfault occurs run the following gdb commands
(gdb) backtrace full
(gdb) info registers
(gdb) thread apply all backtrace
(gdb) quit

Thanks

Jean the problem is after I enter into xmoto the machine hangs, I'm unable to get the whole thing.

If there was just some way to use xmoto -win or xmoto --windowed mode while trying to make the backtrace.

This way I can see what I'm doing.

What I'm doing now is after the machine hangs, I do CTRL+ALT+Backspace and enter into session.

Any help in this regard would be helpful.

To run gdb with xmoto in windowed mode you can run:
gdb --args xmoto -win

or edit the file ~/.xmoto/config.dat and change the value of the property "DisplayWindowed" to true

Jean,
 Thanx, here's the full thing with the backtrace retrieved.

Hopefully it will give what the issue is. There is possibility that my on-board chipset is under-powered for the game to run.

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Be assured that your chipset is not to blame :)

Please can you attach the files:
~/.xmoto/config.dat
~/.xmoto/xm.db

As a workaround, I think that you can get rid of this error by moving or deleting the file ~/.xmoto/xm.db . It will be recreated next time you start xmoto but this will reset all your stats, replays and level database.

I'm closing this report regarding the issue originally described can't be reproduced.

A new bug report has been filed regarding the crash in bug #243819.

Thanks for your time.