XRoar 1.6 released

[pser1]

that one was easy enough for me
-joy-right qaop -joy-left joy0
And there we go.
Now using Ctrl+Shift+J changes between 'my' AGD joystick or the AGD keys!
great!
cheers!

[Alastair]

[snip]
Issuing xroar -joy help simply opens/closes a black window and exits
[snip]
EDIT - Even issuing xroar --help I get nothing, it ends with no text shown at all

Pere, try xroar -joy help >> joyhelp.txt or xroar -help >> xroarhelp.txt. You will end up with text files that contain the expected output. (On Windows it makes no difference if you use -joy/-help or --joy/--help, also you can use whatever filename you want.)

[pser1]

[snip]
Issuing xroar -joy help simply opens/closes a black window and exits
[snip]
EDIT - Even issuing xroar --help I get nothing, it ends with no text shown at all

Pere, try xroar -joy help >> joyhelp.txt or xroar -help >> xroarhelp.txt. You will end up with text files that contain the expected output. (On Windows it makes no difference if you use -joy/-help or --joy/--help, also you can use whatever filename you want.)

thx a lot!
I didn't know
cheers!

[rolfmichelsen]

Hi Ciaran,

I'm now getting a segmentation fault when running xroar 1.6.5 on ubuntu 22.04. The console output is short and sweet...

Code: Select all

[~]$ xroar -v 3
[gtk3] GTK+ 3 UI
vo_gtk3: glXSwapIntervalMESA(1)
[gtk3] GTK+ 3 file requester
Segmentation fault (core dumped)

I'm running this under wsl2 on Windows 10 and getting xroar from the debian apt repository. This has serviced me well as a decent development environment for a long time, all through the 1.5 versions of xroar.

Any clues or hints?

-- Rolf

[sixxie]

Hi Ciaran,

I'm now getting a segmentation fault when running xroar 1.6.5 on ubuntu 22.04. The console output is short and sweet...

Code: Select all

[~]$ xroar -v 3
[gtk3] GTK+ 3 UI
vo_gtk3: glXSwapIntervalMESA(1)
[gtk3] GTK+ 3 file requester
Segmentation fault (core dumped)

I'm running this under wsl2 on Windows 10 and getting xroar from the debian apt repository. This has serviced me well as a decent development environment for a long time, all through the 1.5 versions of xroar.

Any clues or hints?

Hmm only that 1.6 introduced a GTK+ 3 UI. You could try running "configure" with "--without-gtk3" so that it builds against GTK+ 2 as it would have in the past?

The main difference between the two is that the GTK+ 2 build needed an external library - GtkGLExt, that you've doubtless installed - for graphics, where GTK+ 3 has an OpenGL draw area built in.

..ciaran

[rolfmichelsen]

I can try that.

In the meantime I dusted off my old laptop, which is still running xroar 1.5.4. That version experiences the segfault, too, but only when I exit xroar.

-- Rolf

[sixxie]

I can try that.

In the meantime I dusted off my old laptop, which is still running xroar 1.5.4. That version experiences the segfault, too, but only when I exit xroar.

-- Rolf

How curious. Are you able to run it in gdb and get a backtrace?

[rolfmichelsen]

I should be able to try that, too.

-- Rolf

[rolfmichelsen]

Hmm only that 1.6 introduced a GTK+ 3 UI. You could try running "configure" with "--without-gtk3" so that it builds against GTK+ 2 as it would have in the past?

Building xroar from the git repo using "configure --without-gtk3" works like a charm. For good measure, I built both HEAD (xroar 1.6.3) and the 1.6.5 tag.

-- Rolf

[sixxie]

Building xroar from the git repo using "configure --without-gtk3" works like a charm. For good measure, I built both HEAD (xroar 1.6.3) and the 1.6.5 tag.

So on the one hand, "hooray", glad it works for you.

On the other hand, "boo", as I just changed how the UI interacts with the rest of the code significantly and this is going to mean making sure that all works with GTK+ 2 instead of just dropping it

Unless we can get to the bottom of why GTK+ 3 isn't working in your environment, of course.

..ciaran