Forums » Bugs
linux client needs glibc 2.4, crashes on start (EEEPC)
My connection is wonky, therefore I don't know whether the bug reporter managed to get the bug report to you, so I thought I'd mention this here. On an asus eeepc, the freshly-installed vendetta 32bit client folds and gives you the bug reporter immediately after being started. The line from errors.log that caught my eye was
[Sun Oct 18 01:04:27 2009] Can't load driver /home/user/.vendetta/drivers/gkvc.so: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /home/user/.vendetta/drivers/gkvc.so)
Further below there is also a nice
caught SIGSEGV; generating stack trace
fault address 00000084, b7f1b020, 00000001
but I am not sure the two are related. Whole error.log on request in case the bug reporter failed.
[Sun Oct 18 01:04:27 2009] Can't load driver /home/user/.vendetta/drivers/gkvc.so: /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /home/user/.vendetta/drivers/gkvc.so)
Further below there is also a nice
caught SIGSEGV; generating stack trace
fault address 00000084, b7f1b020, 00000001
but I am not sure the two are related. Whole error.log on request in case the bug reporter failed.
Your bug report made it through fine.
It doesn't start the updater at all? From the report, it looks like it ran the installed version without updating.
The glibc problem just prevents voice chat from working, it looks like Vo still tried to load and crashed in the os's OpenGL driver. What are the first 100 or so lines of glxinfo command-line command?
It doesn't start the updater at all? From the report, it looks like it ran the installed version without updating.
The glibc problem just prevents voice chat from working, it looks like Vo still tried to load and crashed in the os's OpenGL driver. What are the first 100 or so lines of glxinfo command-line command?
updater: nope. BTW: I just found the $HOME/bin/vendetta file (have been starting through $HOME/.vendetta/vendetta), and it crashes right away without giving me either the updater OR the bug reporter.
... EDIT: I just tried it ($HOME/bin/vendetta) again after posting this, and it is updating. I am curious what will happen.
... EDIT 2: Crashed pressing [Play], bug report sent. I am aware my config is not exactly top of the line, but I am not sure Sigsegv is a healthy reaction nevertheless.
glxinfo: "No such file or directory". Seriously, there is no official mesa-utils or mesa-demos package for eeepc p701, as it seems, despite there being a bunch of other mesa packages installed (and crack attack working which won't run without libgl1 / libglu1 ).
Can I supply anything else without replacing my OS or heavily relying on packages from foreighn distros? (If not, screw it, it doesn't HAVE to run there if it would be just for me).
... EDIT: I just tried it ($HOME/bin/vendetta) again after posting this, and it is updating. I am curious what will happen.
... EDIT 2: Crashed pressing [Play], bug report sent. I am aware my config is not exactly top of the line, but I am not sure Sigsegv is a healthy reaction nevertheless.
glxinfo: "No such file or directory". Seriously, there is no official mesa-utils or mesa-demos package for eeepc p701, as it seems, despite there being a bunch of other mesa packages installed (and crack attack working which won't run without libgl1 / libglu1 ).
Can I supply anything else without replacing my OS or heavily relying on packages from foreighn distros? (If not, screw it, it doesn't HAVE to run there if it would be just for me).
Setting tc to 0 in the refgl section in $HOME/.vendetta/config.ini might help. If it isn't already that is.
YQ, try what mr_spuck said, and a couple of other settings.
You may need to create the config.ini file.
[refgl]
tc=0
dovertexbuffers=0
doindexbuffers=0
You may need to create the config.ini file.
[refgl]
tc=0
dovertexbuffers=0
doindexbuffers=0
Same result.
Well, almost, now I do get the bug reporter even when starting from $HOME/.vendetta/vendetta (but the updater only appears when starting from $HOME/bin/vendetta, which I assume is normal. Then it crashes when I click on "play").
EDIT: The new version still does that.
Well, almost, now I do get the bug reporter even when starting from $HOME/.vendetta/vendetta (but the updater only appears when starting from $HOME/bin/vendetta, which I assume is normal. Then it crashes when I click on "play").
EDIT: The new version still does that.