rolauncher crash : double free or corruption (out): 0x08648a70 ***

[Maharatschi]

just installed gutsy tribe 5 and i can't start rolauncher now. See text file.

[DeepThought]

Originally Posted by Maharatschi

just installed gutsy tribe 5 and i can't start rolauncher now. See text file.

Yeah, it seems like this fault exists for those of us who are running Gutsy.. at least it's something some of us seems to have in common.

[saxtro]

to play just launch the game with an export

$ export MALLOC_CHECK_=0
$ ./rolauncher

a little bash script to make it easy
N.B. regnum online must be in your home
fix this script with your path

#! /bin/sh
## Script to launch regnum online with export fix to play with latest lic6

regnum_launcher () { 
export MALLOC_CHECK_=0
/home/$user/Regnum/rolauncher
}


whoami | while read user; do
regnum_launcher
done

[DeepThought]

Thanks saxtro! Unfortunately it didn't make the game start, but at least I got the "ToU"-screen, but as soon as I push the Accept-button I get a Seg-fault (core dumped)..

EDIT: After some minute it seems to work. Hm, odd. But then again, when I close the terminal it takes yet some minute after exporting the variable, before the game starts.

Well, thanks anyway, at least it seems to work (from time to time).

[einalex]

try:
MALLOC_CHECK_=0 ./rolauncher

that should get you going.

[castorgris]

I also run on Ubuntu gusty, and i have the same problem as all of you.
I try to use the Saxtro tips :

$ export MALLOC_CHECK_=0
$ ./rolauncher

Then the login fenster appear normaly, i enter my password, And i have an error message hich tell me thaht " he can't connect to autopatch server"
So I can't play.
If anyone has an idea .....

[saxtro]

Originally Posted by castorgris

[..]Then the login fenster appear normaly, i enter my password, And i have an error message hich tell me thaht " he can't connect to autopatch server"
[...]

fenster = window ?

if you cant connect to autopatch server you must configure the network connection
look at router's or/and iptable's rulez
you can paste the output of

# iptables -L

to help us helping you
i think is better if you open a new topic, this problem is out of topic here