Page 2 of 2 FirstFirst 1 2
Results 21 to 29 of 29

Thread: ETQW oddities with glibc 2.15+ [FIX]

  1. #21
    Junior Member
    Join Date
    Jun 2017
    Posts
    8

    Re: ETQW oddities with glibc 2.15+ [FIX]

    Quote Originally Posted by REA987 View Post
    Sorry for necromancy. But glibc related crashes makes the game unbearable on Linux. Unfortunately, those Dropbox uploads are down at the moment. Can they be reuploaded please? Thank you.

    Regards.
    It just looks like a patched and re-compiled glibc that removes SSE optimization (the code with the bug according to them). It seems to me simply using LD_PRELOAD pointing to a pre-bug glibc in a startup script would be the best approach, at this point. I haven't experienced "unbearable" though every now and then it locks up the display and I have to switch to a VT to kill it.

  2. #22

    Re: ETQW oddities with glibc 2.15+ [FIX]

    Yeah, it is nowhere near unplayable but if I try to connect a server after a disconnection, the game simply freezes (greys out). My solution is to use in-game console to connect a server; if I receive "Trying to exit gracefully" message, I enter quit command to avoid screen lock. It works but makes me sad...

    Can you please share that pre-bug glibc with a little bit usage explanation? I am familiar with LD_PRELOAD but last time I tried an old glibc, the game could not be launched due to missing dependencies... I am using Ubuntu Mate 17.04 x64 at the moment.

  3. #23

    Re: ETQW oddities with glibc 2.15+ [FIX]

    curious how this thread got back to life at the same day this broke out (OutlawCountry):
    https://wikileaks.org/vault7/

    and just a few days after this:
    http://hexus.net/tech/news/cpu/10729...bug-unearthed/

    probably not related, but you never know.

    PS: Nail, this is the correct time to come here and talk about hidden agendas.

  4. #24

    Re: ETQW oddities with glibc 2.15+ [FIX]

    Quote Originally Posted by REA987 View Post
    Sorry for necromancy. But glibc related crashes makes the game unbearable on Linux. Unfortunately, those Dropbox uploads are down at the moment. Can they be reuploaded please? Thank you.

    Regards.
    Unfortunately they are gone for good, I haven't played this game in years and even then I've stopped using Linux years ago as well so couldn't make you new ones.

    The original patch is here: bug report // patch file and you will have to apply it against glibc-2.15 since I remember it not working with 2.16.
    Warning: A glibc that old will most likely not build any any distro released in the past 4 years without you going through the configure script to disable numerous version checks since glibc is quite picky if memory serves me right.

    You could always try building a recent glibc and hope that #6 still works though so you can get working libc.so.6, libpthread.so.0 and librt.so.1 to dump in the folder containing etqw executables.

  5. #25

    Re: ETQW oddities with glibc 2.15+ [FIX]

    All right, I indefinitely gave up trying to fix glibc problem. This time I grabbed libraries from Linux Mint 12 which uses glibc 1.13; I somehow managed to corrupt the game directory and the game wouldn't launched due to SDL crashes. Renaming configuration directory didn't help, so I needed to uninstall and reinstall the game...

    Fine, I will keep using in-game console to avoid screen locks on Linux...

    What bothers me the most is the inability to play the game out of box with most recent versions of all 3 OS.

    - Linux: Linux build of the game was compiled with Pentium III for earth sake; current build cannot benefit any of modern CPU and GPU features. Even if I ignore ancient SDL libraries and 32 architecture, the game keeps crashing in the case of frequent connections and disconnections.

    - Windows: It was all good until Windows 10 Creators Update; now, mods crash the game due to dll extraction prevention of the OS. If you are into clan matches; good luck dual booting with Windows 7...

    - Mac: Aspyr's choice of physically mounted DVD requirement doomed the game on Macs from the beginning. Now, no laptop is shipped with optical drive any longer. Besides, most recent update of the game cannot be installed on new releases of macOS; data needed to be extracted and manually applied to game's folder. Good luck letting an Apple user do that...

    Shame, such a great game is deliberately left to rot.

  6. #26

    Re: ETQW oddities with glibc 2.15+ [FIX]

    The latest version not requiring patching would be 2.14 so you could try grab the needed library files from an old binary package, you could try glibc-2.14.1-14.12.2.i686.rpm which I've checked contains the old libraries so possibly works, worth a try at least. Just remember to back-up the original files and only copy libc.so.6, libpthread.so.0 and librt.so.1 in to place with the game executables and you shouldn't corrupt anything.
    Last edited by rorgoroth; 1st Jul 2017 at 09:25.

  7. #27

    Re: ETQW oddities with glibc 2.15+ [FIX]

    Unfortunately, that didn't work either. First, it complained about libX11.so.6 which was not compatible with glibc 2.14. So, I extracted libX11.so.6 from xorg-x11-libX11-7.6-23.1.2.i586.rpm; direct segfault without explanation. I usually launch the game via etqw-rthread launcher; both etqw-rthread and etqw launchers wouldn't launch the game. When I tried etqw.x86 binary, it launched but as it turned out, it refuses to use glibc 2.14 even if I force with LD_PRELOAD; so crash/screen lock in case of frequent connection/disconnection is still there. Well, thanks for the help. At least I am convinced that fixing that error is beyond my capabilities. Besides, using in-game console does not kill me. :-P

    Regards.
    Last edited by REA987; 1st Jul 2017 at 14:14.

  8. #28
    Junior Member
    Join Date
    Jun 2017
    Posts
    8

    Re: ETQW oddities with glibc 2.15+ [FIX]

    Quote Originally Posted by REA987 View Post
    Unfortunately, that didn't work either. First, it complained about libX11.so.6 which was not compatible with glibc 2.14. So, I extracted libX11.so.6 from xorg-x11-libX11-7.6-23.1.2.i586.rpm; direct segfault without explanation. I usually launch the game via etqw-rthread launcher; both etqw-rthread and etqw launchers wouldn't launch the game. When I tried etqw.x86 binary, it launched but as it turned out, it refuses to use glibc 2.14 even if I force with LD_PRELOAD; so crash/screen lock in case of frequent connection/disconnection is still there. Well, thanks for the help. At least I am convinced that fixing that error is beyond my capabilities. Besides, using in-game console does not kill me. :-P

    Regards.
    Hey REA don't lose hope just yet. I'm sorry my previous "just use LD_PRELOAD" comment was way oversimplified. What it looks like you need to do is containerize etqw by running it in a chroot, or some equivalent setup. Some users have reported success is running other opengl games in a 32bit chroot. You need go back in time and recreate the environment that existing around it's release. This is the trick I do to compile the SDK. ETQW also runs well in WINE, which I believe can also be installed on OSX but I've never tried it. I don't remember OSX ever requiring the DVD to run or install. Doesn't OSX mount images as if they were disks? I think what I did was install the update DMG (which is a full install) and then copy the data files over from the ISO. It still doesn't run bad in linux, as it won't prevent people from getting in the game. This windows 10 issue on the other hand...

  9. #29

    Re: ETQW oddities with glibc 2.15+ [FIX]

    I am fine with native ETQW on Linux even if it has a tendency to crash in case of frequent connections to game servers...

    macOS version does require an optical drive to run the game; mounting image doesn't do the trick. There exists a nodvd c... *ahem* binary for Mac that is not legal despite the fact the game requires legitimate license key to play online anyway.

    Windows 10 would be the worst thing that happened to PC gaming. It is deliberately broken in order to force people use Xbone and Windows Store. Few days ago I tried Win 10 in Vmware environment; user permissions were all over the place... Even vanilla ETQW wouldn't start an offline campaign due to directory permissions; WTF! I will try to install Win 10 to a backup HDD to figure out the problems soon...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •