Maratis forum - Player segmantation fault on linux when fullscreen

Re: Player segmantation fault on linux when fullscreen

dummy@example.com (anael) — Tue, 19 Feb 2013 11:32:09 +0000

good, that's corrected,
thank you for the report.

Re: Player segmantation fault on linux when fullscreen

dummy@example.com (Lamberto) — Tue, 19 Feb 2013 11:10:47 +0000

it works great!!!
you just forgot the semicolon at the end of line 555
thank you for the quick fix.

Re: Player segmantation fault on linux when fullscreen

dummy@example.com (anael) — Tue, 19 Feb 2013 09:58:03 +0000

Thank you, I found something wrong in this line and made a fix available on svn, can you test if it works ?

Re: Player segmantation fault on linux when fullscreen

dummy@example.com (Lamberto) — Tue, 19 Feb 2013 09:37:29 +0000

this is what the debugger outputs:

Program received signal SIGSEGV, Segmentation fault.
0x080cc62c in MWindow::create (this=0x8397e60, title=0x82d6695 "Maratis", 
    width=800, height=600, colorBits=32, fullscreen=true)
    at MSDK/MGui/Sources/X11/MX11Window.cpp:587
587                rootWindow = RootWindow(display,vi->screen);

Re: Player segmantation fault on linux when fullscreen

dummy@example.com (anael) — Tue, 19 Feb 2013 06:25:59 +0000

Be sure the resolution is supported by your screen, you can set the resolution from the command line.

Right now I don't have a way to test on linux unfortunately,
is it possible for you to compile and run the sources in debug mode ?

The fullscreen mode in linux is initialized in MGUI/X11 here (MWindow::create) :
http://code.google.com/p/maratis/source … Window.cpp

Player segmantation fault on linux when fullscreen

dummy@example.com (Lamberto) — Mon, 18 Feb 2013 12:19:35 +0000

I get a segmentation fault when passing the fullscreen parameter to the player.
this happen on 2 machines equipped with ubuntu 12.10 and 12.04 and nvidia graphic cards
searching in the forum I found there was a similar problem in past in this topic http://forum.maratis3d.com/viewtopic.php?id=3&p=2 and it seems it was solved.
is there anybody else experiencing the same error?

Lamberto