Problem with latest update

[Linuxmage]

Originally Posted by HunterRed

I have the same problem... Tried to log in 10 minutes ago, launcher opened, downloaded something, and close it self. Now when I click on CoR icon nothing happans. Linux, Ubuntu 10.10

The latest version of the launcher requires a set of libraries only found in ubuntu 12.10, and up. Ubuntu 10.10 is 2 years out of date, which is a long time in the fast moving word of linux development. Seriously, you need to consider doing a fresh clean install of 12.10, the launcher will have no problems with that.

To all of you -- Please upgrade Ubuntu at least once a year. It uses older stable versions of libraries, and sometimes, those libraries get deprecated. Right now, the OLDEST version to be using is 12.10, and 13.04 was releasd recently. It had some teething problems, but they are sorted out.

You could also consider Linux Mint, as that stays on top of the curve fairly well, but Ubuntu 12.04 and down are considered out of date now.

[HunterRed]

Hmm...yesterday after aupdate all worked fine, but today after this small download launcher isn`t working...
Btw, i`m happy with my setup and system on 10.10, and I don`t want to upgrade it only `couse of regnum.

Is there anyway I can make this launher to work?
(Also would like to hear a few words from NGD, about this?)

[Linuxmage]

What this update did was to make the launcher dependent on a fairly recent (less than a year old) version of GCC, and more recent gtk libraries.

Like I say, whilst I appreciate that 10.10 might be running fine for you, you will start to hit problems in the very near future with things like firefox, and programs that are becoming dependent on gtk 3 and its associated libraries.

I would seriously suggest as a 14 year veteran of linux usage that you consider updating to 12.10, it will kepp you going for another year yet.

[Jardik123]

Originally Posted by HunterRed

Hmm...yesterday after aupdate all worked fine, but today after this small download launcher isn`t working...
Btw, i`m happy with my setup and system on 10.10, and I don`t want to upgrade it only `couse of regnum.

Is there anyway I can make this launher to work?
(Also would like to hear a few words from NGD, about this?)

Just downloaded libstdc++ 4.8 here, do NOT install it, but extract libstdc++ library to any directory and run regnum from terminal with exported LD_LIBRARY_PATH to the path with the library and see what happens. If it complains about old libc, do the same with libc, etc ... until it starts working.

[Cuchulainn]

Originally Posted by gwirsaeth

It seems to be a problem with surround sound - if I set sound output to 5.1 instead of analogue stereo the quality of sound improves dramatically but I only have analogue headphones so some effects sound too loud, for example the sound of an arrow hit is in the middle of my head (too loud) not in the distance. It is bearable and time to shop for 5.1 headphones!

did you take a look on the alsoft.conf file already? Perhaps it helps to change channels or sample-type.

[Lebeau]

I couldn't even run ro-launcher with 32-bit 11.10 1st week of June, so I updated to the best LTR Linux-os currently available. Launcher runs, validation worked, game gets to character selection screen, then press 'play' & POOF ... 'Crashnum' strikes again! Pardon me, but Linux 12.04 IS supposedly THE Linux LongTermRelease & is the ONLY valid xubuntu-based Linux OS to be supported until 2017. If it doesn't have these gd stupid 'required' libraries, then NGD (or someone) has royally f-ed up & really needs to update/backdate their effing compatibility. Most linux-peeps are NOT on 12.10 or higher & won't be for some time, if ever! Many will stay with 12.04 until the next LTR. I, for one, will NOT 'downgrade-forward' to 12.10 from 12.04 atm, no gd way. TOO many crap issues with POS 12.10+ (& Regnum is SO 'cutting-edge', it requires 12.10+?! How totally & ironically fitting ... birds of a feather ... crap together! W2G!) FFS! ... tired as hell of this total shit ... stupid! Stupid!! STUPID!!!

[Linuxmage]

LeBeau, I think you need some correction.

The base kernel and system that 12.04 is using is 2 years old. In the world of linux development, thats a long time. I run 12.10 with absolutely no problems, it is not cutting edge in any sense of the word, and is totally stable.

Ubuntu, even in its latest release, is roughly 6 months behind the rest of the linux development world.

But, such is the way of the Debian world.

Now, tke Arch Linux. THATS bleeding edge. I used to run my machines on Arch Multilib testing, and thats about as unstable as it gets.

It really sounds like the problems you are having with your machine are entirely on your end. There is a very real possibility that your system is crashing due to a driver restriction or update of some kind. Your system might be missing libraries.

So, I need you to do something for me. (& surak).

Can you please start the rolauncher in terminal, and tell us if the terminal spits anything out when it crashes.

To do this, go into the regnum dir (probably in ~/regnum), then run ./rolauncher.

Hopefully stdout will give us an idea of whats going on. Its almost certainly associated with OpenGL.

[Lebeau]

Originally Posted by Linuxmage

LeBeau, I think you need some correction.

The base kernel and system that 12.04 is using is 2 years old. In the world of linux development, thats a long time. I run 12.10 with absolutely no problems, it is not cutting edge in any sense of the word, and is totally stable.

Ubuntu, even in its latest release, is roughly 6 months behind the rest of the linux development world...

...It really sounds like the problems you are having with your machine are entirely on your end. There is a very real possibility that your system is crashing due to a driver restriction or update of some kind. Your system might be missing libraries...

Thanks very much for the offer of assistance, but for now at least, Icon, his help & I are working it all out, but it IS taking awhile (one issue solved, 2 more pop up, etc.). That I can't play Regnum & that Mint 13/Ubuntu 12.04 is almost 2 years old are both completely irrelevant to the point that I'm really making & immaterial to the why I am understandably upset. 12.10 & newer are ALL branch, short-term distros. True, they may be newer, even better (tho word is, they aren't) but they are NOT the FLAGSHIP LongTermRelease OS. Only 12.04 is. If what u had said b4 is true...

The latest version of the launcher requires a set of libraries only found in ubuntu 12.10, and up ... What this update did was to make the launcher dependent on a fairly recent (less than a year old) version of GCC, and more recent gtk libraries.

...then essentially, NGD has firmly decided to no longer be linux-native, which is sad. If they refuse to support the ONLY common long-term, fully-supported-til-2017 Linux OS currently available, & instead insist on ONLY these newest, branch, short-term distro os's, then CoR has now become at best only 'linux-hybrid'-in-compatibility, NOT truly linux-native any longer like b4. True, me using the only currently available still-supported-elsewhere LongTermRelease central-version of Linux IS "on my end", but choosing to not support it, definitely is not ... that was NGD's decision, & imho, it was a really "stupid! Stupid!! STUPID!!!" one.

[Lebeau]

We got RO up & running ... the launcher & os will at least speak to each other now (upgraded from mint12 11.10 linux to Xubuntu 12.04), but having a very long wait between loader & toon-slection screen. Taking like 15 to 20 times as long as was usual.

Here's y (terminal printout):
"[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.dll.
ALSA lib pcm_dsnoop.c:612:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.HDA-Intel.pcm.rear.0:CARD=0'
ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM rear
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.HDA-Intel.pcm.center_lfe.0:CARD=0'
ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM center_lfe
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition 'cards.HDA-Intel.pcm.side.0:CARD=0'
ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM side
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started"

& here's my single crash so far (terminal printout):
"Saving backtrace to crash_backtrace_2902.log
Got SIGSEGV (segmentation fault)"

Some others I spoke to ingame since returning also say their wait time between launcher & character selection is way, way up since patch in late May. Any help or advice is truly appreciated.

Edit: I've since noticed that audio is scratchy & pops ingame. 1st time in, it doesn't do this, but 2nd & all subsequent logins to game produce this issue. A reboot of os allows a fresh 1st entry & prob isn't there (but only during the 1st time in, as I said).