After updating, ./vendetta command produces a segmentation fault.

Errors.log:
wtf!archive returned 0
[Sat Jun 13 09:02:14 2009] Can't load driver /home/murad/.vendetta/drivers/gkvc.so: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /home/murad/.vendetta/drivers/gkvc.so)

I am using Debian Etch 64. In /usr/lib my system has a libc.so but no libc.so.6.

After LDD on gkvc.so:
./gkvc.so: /lib/libc.so.6: version `GLIBC_2.4' not found (required by ./gkvc.so)

ls -l /libc/libc.so.6 produces:
lrwxrwxrwx 1 root root 13 2009-02-10 19:08 /lib/libc.so.6 -> libc-2.3.6.so

Client will not load for me either, I am on Debian Lenny(AMD64)... I was on right before the update.

I opened a support ticket for this problem. One of the Developers is downloading Debian to test it. I'll keep updating on this thread as I get responses.

Maxiom, are you also getting the same segfault behaviour? Or something else?

I assume the game was working peachy in both cases, immediately before the update, correct? You guys didn't do any OS-upgrades or anything that could have contributed, around the same time?

Have either of you ever used, or attempted to use, voice chat?

I think this segfault occurs because Debian Etch (released two years ago) ships with libc 2.3.6 http://packages.debian.org/etch/libc6

The only way to fix this is to install libc > 2.4 (this may not be practical), upgrade to Debian Lenny, or get a patch/work-around from the devs so you can run the game anyway.

Debian Lenny (released a few months ago) wont fail because of this segfault as it comes with libc 2.7 http://packages.debian.org/lenny/libc6

You should be able to execute your libc as a command, it will print something like below and reveal your version.

$ /lib/libc.so.6
GNU C Library stable release version 2.9, by Roland McGrath et al.
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.3.3.
Compiled on a Linux >>2.6.24-16-server<< system on 2009-04-09.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

What doesn't make any sense is that we didn't release an update to the VO binary in this latest patch. No linking changes, no binary updates.. just a media patch.

Additionally, we link the game against glibc 2.2. Now the voice chat components are separate and out of our control, and fmod may use 2.4, but we haven't updated the library or anything in at least 6 months. None of that has changed recently.

So, if the game worked on Thursday, and doesn't today, I have no idea what is wrong.

I don't remember if I installed an update, but I do update my system regularly.

I have never used voice chat, but I think I tried and it didn't work so I gave up on it.

muradedge: What version of the game did you have before you updated? Did this launch without segfault? What vendetta binary are you executing? $HOME/bin/vendetta or $HOME/.vendetta/vendetta? I haven't tried this, does the game allow you to play with an older version?

incarnate: Why the game is failing to launch now is fairly obvious. What doesn't make sense is how it could have launched even before the update. The only explanation I can come up with is that muradedge did more than one update (to the game) or had just (re-)downloaded the game.

<OT>
glibc 2.2! Does any major distro even support that? The last 2.2 release was over 7 years ago. Not that it really matters, any plans on moving to 2.3 or beyond? Probably a 1.9 or 2.0 goal?
</OT>

I am not sure how to answer which version of the game I had before updating. It launched prior to updating earlier this week, around Monday June 7th or so. I have always launched the game with a shortcut to /home/murad/bin/vendetta, which in turn runs an update utility automatically then enables a Play Vendetta button.

Before this week I had pressed the Play Vendetta button to start the game. Since the date given above the update utility runs as in the past and the Play Vendetta button gets enabled, but nothing happens when I press the button.

I tried using ./vendetta in terminal mode from the /home/murad/bin directory. This produces a Segmentation Fault on the command line interface.

There was a time months ago when I had deleted the /home/murad/bin/vendetta file. I simply re-installed the game and it was running again as in the past with no issues.

I ran /lib/libc.so.6 and was told that the version was 2.3.6 as in my earlier reply.

Ok, seeing as how you both are running the AMD64 version, I have to revise my earlier statement. Our 32bit builds are linked against glibc 2.2 (an effort to maximize broad compatibility). Our 64bit builds are linked against.. I think 2.8. Given that 2.4 supposedly broke compatibility with 2.3, I'm not sure how our 64bit builds have ever worked on a 2.3 machine.. since we've been linking the 64bit against 2.8 for a long time. Perhaps we just don't use the incompatible functions or something. Glibc compatibility is confusing and bizarre.

Anyway, just to clarify.. muradedge, you're using the 64bit build of VO on a 64bit version of Debian Etch?

However, Maxiom is running the 64bit build of VO on 64bit Debian Lenny. And in your case, you were online right before the update on Friday, and the client worked.. but post-update it does not?

Given the fact that we didn't actually release any binary updates, this is all rather strange. Ray is installing a copy of Etch for testing, but this'll probably take us a little while to track down. Sorry for the inconvenience.. very weird.

Ttat is right, I am running the 64 bit build of VO on the 64 bit version of Debian Etch.

Thanks for the replys guys I did do a system update at same time as game was updating, stupid me.... lol I believe the update confused my system as XOrg was part of the update....

What I did to correct the problem was totally up my system kernel and vid module and all and the did a clean install of Vendetta.

In my case it was totally my fault sorry guys and THANK so much for hopping on this so quick.

Ok, after Maxiom's post I tried to re-install VO by running the installer sh file. After installing I still had the segmentation fault. I used the same install file that I had used to install VO last time.

Works fine on Fedora 10 64bit, that ships with glibc-2.9.

Well i have decided that I should upgrade to Debian Lenny. I will get around to it sometime this week or weekend. If I have any problems, i will reply to this thread again. Thanks for trying to help everyone.

If you plan on upgrading too Lenny I would suggest setting up a New Lenny partition as I have heard migration from Etch to Lenny has more issues than a fresh install.

BTW I still have an Etch partition soon to be gone, come to think of it I still have a window$ partition that has not been booted for maybe 2 years.... time to dump that one too. :))

OK, so I decided not to upgrade to Lenny for a bit due to possible problems I find people have experienced. In the meantime, unfortunately, I had to cancel my subscription due to this segmentation fault on 64 bit Etch.

I have finally upgraded from Debian Etch to Lenny and wanted to report the VO is once again running and I have renewed my subscription!