search

ValveSoftware / csgo-osx-linux

Counter-Strike: Global Offensive
http://counter-strike.net
774 stars 69 forks source link

Failure to start: game bundled tcmalloc crash with system glibc 2.33 #2659

Closed mahlersand closed 2 years ago

mahlersand commented 3 years ago

Your system information

Please describe your issue in as much detail as possible:

Starting CSGO results in a crash after a few seconds. I have tried removing my controller, removing all start options (-nojoy -novid -threads 8), reinstalling the steam runtime (deleting all steam related files from my home dir), switching to the steam beta (I was not on it), disabling the steam overlay.

crash_20210211121653_1.zip

Steps for reproducing this issue:

  1. Have Manjaro Linux / KDE Plasma / AMD RX 5700
  2. Start CSGO
kisak-valve commented 3 years ago

For reference, the attached minidump is a SIGSEGV in libtcmalloc_minimal.so.0 coming from libvideo.so. Similar to https://github.com/ValveSoftware/csgo-osx-linux/issues/2651#issuecomment-775429100 and https://github.com/ValveSoftware/csgo-osx-linux/issues/2651#issuecomment-775466915.

Doom972 commented 3 years ago

Same for me on Manjaro KDE. This started after the same update. After my first couple of crashes, I noticed that Manjaro changed my kernel from 5.4 to 5.10. Changing back to 5.4 didn't solve this issue.

Specs: Z390 Motherboard i5-9600K 32 GB RAM Intel® UHD Graphics 630

aniketfuryrocks commented 3 years ago

It works after disabling steam input in the properties > controller > disable steam input. I guess it's some incompatibility with the new kernel. I heard that kernel 5.10 added support for controllers.

mahlersand commented 3 years ago

It works after disabling steam input in the properties > controller > disable steam input. I guess it's some incompatibility with the new kernel. I heard that kernel 5.10 added support for controllers.

This seems to actually work. However, the kernel update doesn't really make sense, since I have been on 5.10 for a few weeks already, and everything worked fine. 🤔

aniketfuryrocks commented 3 years ago

Might be a mismatch with libraries during the update.

1m-N00b commented 3 years ago

It works after disabling steam input in the properties > controller > disable steam input. I guess it's some incompatibility with the new kernel. I heard that kernel 5.10 added support for controllers.

it didnt work for me

Doom972 commented 3 years ago

It's not unique to kernel 5.10. It happens to me in 5.4 as well and disabling Steam Input doesn't help.

1m-N00b commented 3 years ago

i could play wednesday

aniketfuryrocks commented 3 years ago

@Doom972 try setting it to 'Use Default Settings'

lionblaze55 commented 3 years ago

@kisak-valve is this not just a duplicate of #2651?

kisak-valve commented 3 years ago

Hello @lionblaze55, right now it's looking like the opening post of #2651 is a duplicate of #1757 while this issue report matches some of the more detailed information that other players have piled onto that issue report, but may be unrelated to the opening post. There isn't enough information on the other issue report to conclude they are duplicates.

Doom972 commented 3 years ago

While this issue seems like a duplicate, it's not. This one seems to be unique to Manjaro after this month's update.

@aniketfuryrocks I got the same issue after setting it to default settings.

riscie commented 3 years ago

I am having the same issue using manjaro. By the way @Doom972: Are you talking about the latest csgo update or the latest manjaro updates?

Doom972 commented 3 years ago

@riscie I was referring to the latest Manjaro update.

alifeinbinary commented 3 years ago

Read my comment from https://github.com/ValveSoftware/csgo-osx-linux/issues/2651#issuecomment-778566951

The process id seems to be changing mid-process and crashing when there's a mismatch.

riscie commented 3 years ago

Here are the latest manjaro updates. If someone can help to narrow it down, I could try to downgrade some packages and re-test. What peaks my eyes is: xf86-video-nouveau (1.0.16-2 -> 1.0.17-1)

(click to expand)

``` alsa-card-profiles(14.2-1->1:0.3.21-1) amd-ucode(20210109.r1812.d528862-1->20210119.r1813.0578970-1) archlinux-appstream-data(20201223-1->20210125-1) linux-api-headers(5.8-1->5.10.13-1) tzdata(2020f-1->2021a-1) filesystem(2020.09-2->2021.01.19-1) glibc(2.32-5->2.33-3) gcc-libs(10.2.0-4->10.2.0-6) libgcrypt(1.8.7-1->1.9.1-1) e2fsprogs(1.45.6-3->1.46.0-1) libldap(2.4.56-1->2.4.57-1) krb5(1.18.2-1->1.18.3-1) asciidoc(9.0.4-2->9.0.5-1) audit(2.8.5-9->3.0-1) autoconf(2.69-7->2.71-1) automake(1.16.2-3->1.16.3-1) sqlite(3.34.0-1->3.34.1-1) zstd(1.4.5-1->1.4.8-1) libtiff(4.1.0-2->4.2.0-1) pam(1.5.0-2->1.5.1-1) libcap(2.46-1->2.47-1) systemd-libs(247.2-1->247.3-1) glib2(2.66.4-2->2.66.6-1) libcups(1:2.3.3op1-1->1:2.3.3op2-1) wayland(1.18.0-2->1.19.0-1) libunwind(1.3.1-2->1.4.0-1) libedit(20191231_3.1-2->20191231_3.1-3) llvm-libs(11.0.1-1->11.0.1-2) findutils(4.7.0-2->4.8.0-1) ca-certificates-mozilla(3.60.1-1->3.61-1) curl(7.74.0-1->7.75.0-1) mesa(20.3.3-1->20.3.4-1) libxt(1.2.0-2->1.2.1-1) libnftnl(1.1.8-1->1.1.9-1) iptables(1:1.8.6-1->1:1.8.7-1) systemd(247.2-1->247.3-1) libevdev(1.10.1-1->1.11.0-1) libwacom(1.7-1->1.8-1) python-urllib3(1.26.1-1->1.26.3-1) python-setuptools(1:51.1.2-1->1:53.0.0-1) bauh(0.9.13-2->0.9.14-1) lmdb(0.9.27-1->0.9.28-1) bind(9.16.10-1->9.16.11-1) binutils(2.35.1-1->2.36-3) bison(3.7.2-1->3.7.3-1) dav1d(0.7.1-1->0.8.1-1) libpulse(14.2-1->14.2-2) libwebp(1.1.0-1->1.2.0-1) libibus(1.5.23+3+gaa558de8-2->1.5.23+3+gaa558de8-3) ffmpeg(2:4.3.1-3->2:4.3.1-4) nss(3.60.1-1->3.61-1) re2(1:20201101-1->1:20210202-1) pango(1:1.48.0-1->1:1.48.1-1) librsvg(2:2.50.2-1->2:2.50.3-1) gtk-update-icon-cache(1:4.0.1-2->1:4.0.2-1) js78(78.6.0-1->78.7.1-1) tar(1.32-3->1.33-1) electron9(9.4.1-1->9.4.2-3) bitwarden(1.23.1-2->1.24.6-1) btrfs-progs(5.9-3->5.10-1) cmake(3.19.3-1->3.19.4-1) poppler(21.01.0-1->21.02.0-1) imagemagick(7.0.10.58-1->7.0.10.61-1) cups(1:2.3.3op1-1->1:2.3.3op2-1) djvulibre(3.5.28-1->3.5.28-2) dnsmasq(2.82-2->2.84-1) runc(1.0.0rc92-1->1.0.0rc93-1) docker(1:20.10.2-1->1:20.10.3-1) electron(11.2.0-1->11.2.3-1) poppler-glib(21.01.0-1->21.02.0-1) libsynctex(2020.54586-9->2020.54586-10) evince(3.38.0+1+gffa3fd98-1->3.38.1-1) ttf-droid(20121017-8->20121017-9) firefox(85.0-0.1->85.0.1-1) libinstpatch(1.1.5-1->1.1.6-1) fluidsynth(2.1.6-1->2.1.7-1) foomatic-db(3:20200822-1->3:20210205-1) fzf(0.25.0-1->0.25.1-1) game-devices-udev(0.10-2->0.12-1) gcc(10.2.0-4->10.2.0-6) gd(2.3.0-1->2.3.1-1) geoip-database(20201222-1->20210126-1) glib2-docs(2.66.4-2->2.66.6-1) glibmm(2.64.5-1->2.66.0-1) liburcu(0.11.0-2->0.11.2-1) glusterfs(1:8.2-2->1:8.2-3) gnupg(2.2.26-1->2.2.27-1) go(2:1.15.6-1->2:1.15.8-1) goaccess(1.4.3-1->1.4.4-1) parted(3.3-2->3.4-1) pangomm(2.42.2-1->2.46.0-1) gparted(1.1.0-1->1.2.0-2) groff(1.22.4-3->1.22.4-4) grub(2.04-13->2.04-15) gst-plugins-bad-libs(1.18.3-1->1.18.3-2) mjpegtools(2.1.0-5->2.2.0beta-1) zbar(0.23.1-5->0.23.1-6) libshout(1:2.4.4-1->1:2.4.5-1) wavpack(5.3.0-2->5.4.0-1) procps-ng(3.3.16-2->3.3.16-3) serd(0.30.8-1->0.30.10-1) gst-plugins-bad(1.18.3-1->1.18.3-2) gtk-doc(1.33.1-1->1.33.2-1) haskell-hashable(1.3.0.0-69->1.3.0.0-86) haskell-primitive(0.7.1.0-62->0.7.1.0-80) haskell-scientific(0.3.6.2-70->0.3.6.2-79) haskell-attoparsec(0.13.2.4-53->0.13.2.4-62) haskell-base-compat-batteries(0.11.2-43->0.11.2-61) haskell-data-fix(0.3.0-44->0.3.0-53) haskell-dlist(1.0-40->1.0-49) haskell-base-orphans(0.8.4-33->0.8.4-50) haskell-distributive(0.6.2.1-11->0.6.2.1-29) haskell-comonad(5.0.8-10->5.0.8-28) haskell-bifunctors(5.5.9-8->5.5.10-13) haskell-assoc(1.0.2-44->1.0.2-53) haskell-these(1.1.1.1-45->1.1.1.1-54) haskell-strict(0.4.0.1-18->0.4.0.1-27) haskell-time-compat(1.9.5-18->1.9.5-27) haskell-unordered-containers(0.2.13.0-28->0.2.13.0-38) haskell-splitmix(0.1.0.3-38->0.1.0.3-56) haskell-random(1.2.0-108->1.2.0-136) haskell-uuid-types(1.0.3-75->1.0.3-84) haskell-vector(0.12.1.2-103->0.12.2.0-10) haskell-aeson(1.5.5.1-4->1.5.5.1-15) haskell-quickcheck(2.14.2-62->2.14.2-87) helm(3.5.0-1->3.5.2-1) perl-uri(5.05-1->5.07-1) hwinfo(21.71-1->21.72-1) i3-gaps(4.19-1->4.19.1-1) inxi(3.2.02.2-1->3.3.00.1-1) jasper(2.0.19-1->2.0.24-1) lib32-glibc(2.32-5->2.33-3) lib32-gcc-libs(10.2.0-4->10.2.0-6) lib32-glib2(2.66.4-2->2.66.6-1) jre-openjdk-headless(15.0.1.u9-1->15.0.2.u7-1) jre-openjdk(15.0.1.u9-1->15.0.2.u7-1) kustomize(3.9.1-1->3.9.2-1) lib32-e2fsprogs(1.45.6-1->1.46.0-1) lib32-libldap(2.4.56-1->2.4.57-1) lib32-curl(7.74.0-1->7.75.0-1) lib32-pango(1:1.48.0-1->1:1.48.1-1) lib32-nettle(3.6-1->3.7-1) lib32-gtk2(2.24.32-2->2.24.33-1) lib32-pam(1.4.0-1->1.5.1-1) lib32-libcap(2.46-1->2.47-1) libcurl-compat(7.74.0-1->7.75.0-1) lib32-libcurl-compat(7.74.0-1->7.75.0-1) libcurl-gnutls(7.74.0-1->7.75.0-1) lib32-libcurl-gnutls(7.74.0-1->7.75.0-1) lib32-libelf(0.181-1->0.182-1) lib32-libgpg-error(1.39-1->1.41-1) lib32-libgcrypt(1.8.7-1->1.9.1-1) lib32-systemd(247.1-1->247.3-1) lib32-libpulse(14.2-1->14.2-2) lib32-wayland(1.18.0-2->1.19.0-1) lib32-llvm-libs(11.0.1-1->11.0.1-2) lib32-mesa(20.3.3-1->20.3.4-1) lib32-libva(2.8.0-1->2.10.0-1) lib32-libwebp(1.1.0-1->1.2.0-1) lib32-libxt(1.2.0-1->1.2.1-1) lib32-mesa-vdpau(20.3.3-1->20.3.4-1) lib32-sqlite(3.33.0-1->3.34.1-1) lib32-nss(3.60.1-1->3.61-1) lib32-sdl2(2.0.12-1->2.0.14-1) lib32-vulkan-intel(20.3.3-1->20.3.4-1) lib32-vulkan-radeon(20.3.3-1->20.3.4-1) libbytesize(2.4-3->2.4-4) xfsprogs(5.8.0-2->5.10.0-1) libblockdev(2.24-3->2.25-1) libheif(1.10.0-1->1.11.0-1) libical(3.0.8-3->3.0.9-1) libmbim(1.24.4-1->1.24.6-1) libmediainfo(20.08-1->20.09-1) libnm(1.28.1dev+7+g3f5df3cdc6-1->1.28.1dev+16+gdaad4e2fee-1) libnumbertext(1.0.6-1->1.0.7-1) libodfgen(0.1.7-2->0.1.8-1) libplacebo(2.72.2-1->3.104.0-1) libreoffice-still(6.4.7-9->7.0.4-1) libsigsegv(2.12-2->2.13-1) libtorrent-rasterbar(1:1.2.10-7->1:1.2.11-1) libva-mesa-driver(20.3.3-1->20.3.4-1) libxnvctrl(460.27.04-1->460.39-1) linux-firmware(20210109.r1812.d528862-1->20210119.r1813.0578970-1) linux419(4.19.167-1->4.19.173-1) linux419-virtualbox-host-modules(6.1.16-15->6.1.18-5) linux59-virtualbox-host-modules(6.1.16-14->6.1.18-1) matcha-gtk-theme(20210112-1->20210204-1) mediainfo(20.08-1->20.09-1) mesa-vdpau(20.3.3-1->20.3.4-1) mhwd-nvidia(460.32.03-1->460.39-1) mousepad(0.5.1-1->0.5.2-1) mtpaint(3.50.01-1->3.50.03-1) mumble(1.3.3-4->1.3.3-5) net-tools(1.60.20181103git-2->2.10-1) nm-connection-editor(1.18.0-1->1.20.0-1) networkmanager(1.28.1dev+7+g3f5df3cdc6-1->1.28.1dev+16+gdaad4e2fee-1) network-manager-applet(1.18.0-1->1.20.0-1) sstp-client(1.0.14-1->1.0.14-2) network-manager-sstp(1.2.6-2->1.2.6-3) ppp(2.4.7-7->2.4.8-1) networkmanager-pptp(1.2.9dev+10+gb41b0d0-2->1.2.9dev+10+gb41b0d0-3) nodejs(15.6.0-1->15.8.0-1) node-gyp(7.1.1-1->7.1.2-1) p7zip(17.03-1->17.03-2) papirus-icon-theme(20210101-1->20210201-1) perl-image-exiftool(12.00-2->12.16-1) php(7.4.14-1->8.0.2-1) pulseaudio(14.2-1->14.2-2) pulseaudio-bluetooth(14.2-1->14.2-2) python-entrypoints(0.3-5->0.3-6) python-hyperlink(20.0.1-3->21.0.0-1) python-keyring(21.8.0-1->22.0.1-1) python-mako(1.1.3-3->1.1.4-1) python-pip(20.2.4-1->20.3.1-1) python-prompt_toolkit(3.0.10-1->3.0.14-1) python-reportlab(3.5.59-1->3.5.60-1) python-setproctitle(1.2.1-1->1.2.2-1) remmina(1:1.4.10-1->1:1.4.11-1) scrot(1.4-1->1.5-1) sdl2_mixer(2.0.4-5->2.0.4-6) shellcheck(0.7.1-251->0.7.1-271) talloc(2.3.1-5->2.3.2-1) smbclient(4.13.3-2->4.13.4-1) sudo(1.9.5.p2-0.1->1.9.5.p2-1) systemd-sysvcompat(247.2-1->247.3-1) texlive-bin(2020.54586-9->2020.54586-10) thunderbird(78.7.0-0.1->78.7.1-0.3) ventoy(1.0.32-1->1.0.34-1) vim-runtime(8.2.2347-1->8.2.2380-1) vim(8.2.2347-1->8.2.2380-1) virtualbox(6.1.16-4->6.1.18-1) vlc(3.0.11.1-6->3.0.12-1) vulkan-intel(20.3.3-1->20.3.4-1) vulkan-radeon(20.3.3-1->20.3.4-1) xarchiver(0.5.4.16-1->0.5.4.17-1) xf86-video-nouveau(1.0.16-2->1.0.17-1) xterm(363-1->365-1) yay(10.1.2-1->10.1.2-2) youtube-dl(2021.01.16-1->2021.02.04.1-1) yq(2.11.1-2->2.12.0-1) zsh-theme-powerlevel10k(1.14.5-1->1.14.6-1) obsidian-insider(0.10.12-1->0.11.0-1) visual-studio-code-bin(1.53.0-1->1.53.1-1) google-cloud-sdk(326.0.0-1->327.0.0-1) ```

Doom972 commented 3 years ago

It looks like if I try to launch it enough times, it will work. If I close it and try to launch it again, it won't. I can't tell what's different when it does work. I tried removing launch parameters, plugging/unplugging a controller and running it while offline. No consistent results so far.

riscie commented 3 years ago

I experience exactly the same issue. I use this to let it start while I am not at the computer. :o)

until pgrep -x "csgo_linux64" > /dev/null; do
    steam steam://rungameid/730 &
    sleep 30
done
echo "should be started?"
Doom972 commented 3 years ago

@riscie I tried your script, but it seems that letting it launch again and again doesn't work on my end. Perhaps there is a certain condition that causes it to sometimes work?

riscie commented 3 years ago

@Doom972 Did you try with steam already running or not? For me it only works if steam is not running and sometimes it takes 20 times or so.

Doom972 commented 3 years ago

@riscie I tried it with Steam closed. It's the same for me.

boustrophedon commented 3 years ago

I've also been having this issue for a week or so as well. I tried downgrading talloc from 2.3.2 to 2.3.1 and it didn't seem to fix the problem (although I was able to open csgo a few times but not at a high enough percentage to be sure it actually made a difference).

SIGSTKFLT commented 3 years ago

broken as fuck, haven't been able to launch for like 2 weeks now

1m-N00b commented 3 years ago

yep me too (Arch linux)

nitsvga commented 3 years ago

Same problem here. Artix running custom xanmod 5.11.

alifeinbinary commented 3 years ago

Are we screaming into the void? Can someone from Valve confirm that our reports have been heard and an update is on the way? @kisak-valve

darrenjl0 commented 3 years ago

Can confirm this happens on a recently updated OpenSuse tumbleweed system. Kernel: 5.10.16-1-default - Disabling the controller stuff fixed the crash.

chsh175 commented 3 years ago

Can confirm this happens on a recently updated OpenSuse tumbleweed system. Kernel: 5.10.16-1-default - Disabling the controller stuff fixed the crash.

It appears there are separate issues here: 1) Disabling Steam Input fixes the crashes. 2) Disabling Steam Input does not fix the crash.

I'm in the latter group and it'd be nice if we could get confirmation anyone is working to fix this. I can't play the game at the moment.

YShow commented 3 years ago

@DazAh im using opensuse with latest update too, i was able to play csgo without problem before updating to the latest snapshot that recompiled everything to a newer glibc, after this my csgo just crashes after startup too, i even tried the controller stuff but still got crash

sysofd commented 3 years ago

I have the same problem

Shijikori commented 3 years ago

I am using Arch Linux on kernel 5.10.16-arch1-1 and I encounter this issue as well. Disabling Steam Input doesn't fix it for me, rather, I will have much better odds of the game launching if I plug-in one of my controllers and unplug it only once in the game menu. Without the controller plugged in, it seems to be totally impossible to launch the game.

mahlersand commented 3 years ago

It works after disabling steam input in the properties > controller > disable steam input. I guess it's some incompatibility with the new kernel. I heard that kernel 5.10 added support for controllers.

This seems to actually work. However, the kernel update doesn't really make sense, since I have been on 5.10 for a few weeks already, and everything worked fine. thinking

Well, it is not working anymore since a few days. It worked a few times, but I cannot confirm that this once and for all fixes the issue. I would rather agree that CSGO starting is more of a random occurence than a regularity. Honestly, this might make me want my money back for the ongoing operation, since I have not been able to play for quite some time now. @kisak-valve , feel free to relay that concern to the dev team.

fagnerln commented 3 years ago

@DazAh im using opensuse with latest update too, i was able to play csgo without problem before updating to the latest snapshot that recompiled everything to a newer glibc, after this my csgo just crashes after startup too, i even tried the controller stuff but still got crash

Hey guys, this can be a clue! I play CSGO daily and use OpenSUSE too, the last week it had a huge update, just because of this glibc 2.33, I refused to update. But yesterday (after a CS session) I needed to install an application which forced the update of glibc, and now CS doesn't work, so I updated the whole system (I should rollback the installation but now its late).

Funnily that today I had a bit of success using the Steam Linux Runtime, but it inconsistently works (it doesn't right now).

samuel-cavalcanti commented 3 years ago

I observe the same fact of @fagnerln , I think new glibc version break my csgo
csgo output
system information
To play the game, I re-launch until not crash.

1m-N00b commented 3 years ago

guys how to check log?

samuel-cavalcanti commented 3 years ago

@1m-N00b, run steam on terminal and launch csgo

Jedi-Mind-Tricks commented 3 years ago

I experience exactly the same issue. I use this to let it start while I am not at the computer. :o)

until pgrep -x "csgo_linux64" > /dev/null; do
    steam steam://rungameid/730 &
    sleep 30
done
echo "should be started?"

As it turns out @riscie was actually right that the bug reproduces not every time.

You could just re-launch the game till it starts. Can confirm (@ Manjaro KDE).

rodrigofbm commented 3 years ago

Its crashing on my PC too

System:    Kernel: 5.9.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: KDE Plasma 5.20.5 Distro: Manjaro Linux 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> 
           Mobo: ASUSTeK model: PRIME H410M-E v: Rev 1.xx serial: <filter> UEFI: American Megatrends v: 1401 date: 07/27/2020 
CPU:       Info: Quad Core model: Intel Core i3-10100F bits: 64 type: MT MCP arch: Comet Lake rev: 3 L2 cache: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57616 
           Speed: 800 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: Gigabyte driver: nvidia v: 460.39 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 1366x768~60Hz 
           OpenGL: renderer: GeForce GTX 1650 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 direct render: Yes

Maybe if we pay some money to Valve they can help us. They don't give a sh*t to the players...

Keviny9 commented 3 years ago

@rodrigofbm You have wrong about this, this is a problem caused by lib Glibc this not is really a Steam/Valve problem.

riscie commented 3 years ago

I agree to some part @Keviny9. But the Glibc devs do not care about this bug if csgo is the only program triggering it. It's not very likely but in these cases it's best when both sides work together.

It would certainly be helpful if a csgo developer could reproduce the bug and then file an issue against Glibc. A csgo dev could inspect stack traces and set breakpoints where we are more or less in the dark.

alifeinbinary commented 3 years ago

I downgraded lib32-glibc and glibc to the previous release and it borked my system. I cannot boot into Manjaro any longer, so do not try downgrading glibc.

Keviny9 commented 3 years ago

I agree to some part @Keviny9. But the Glibc devs do not care about this bug if csgo is the only program triggering it. It's not very likely but in these cases it's best when both sides work together.

It would certainly be helpful if a csgo developer could reproduce the bug and then file an issue against Glibc. A csgo dev could inspect stack traces and set breakpoints where we are more or less in the dark.

I really agree, I tested others natives games like Dota2 in my library and it works wit the new Glibc, I believe there is some incompatibility between the new GLIBC and the libs used by CS GO.

Shugyousha commented 3 years ago

I downgraded lib32-glibc and glibc to the previous release and it borked my system. I cannot boot into Manjaro any longer, so do not try downgrading glibc.

I did the same on Arch thinking that pacman would warn me if the libc wouldn't be compatible but it didn't.

I managed to recover my system by compiling pacman-static (which is statically compiled and thus doesn't depend on glibc; I had to compile it on a different computer and then managed to copy it over) and using an Arch live USB I had lying around. Maybe doing the same will work for you?

fagnerln commented 3 years ago

I did some tests, on the Flatpak version it works but with a some hit on performance, maybe worth it, it's playable.

guihkx commented 3 years ago

I did some tests, on the Flatpak version it works but with a some hit on performance, maybe worth it, it's playable.

I think this may vary depending on your PC specs. Having benchmarked CS:GO myself in both 'native' and Flatpak'd versions of Steam on Arch Linux, I didn't experience a performance hit whatsoever. I'd even say that the Flatpak version of Steam has more pros than cons, so I encourage people to give it a try before making the switch. It won't hurt...

fagnerln commented 3 years ago

I did some tests, on the Flatpak version it works but with a some hit on performance, maybe worth it, it's playable.

I think this may vary depending on your PC specs. Having benchmarked CS:GO myself in both 'native' and Flatpak'd versions of Steam on Arch Linux, I didn't experience a performance hit whatsoever. I'd even say that the Flatpak version of Steam has more pros than cons, so I encourage people to give it a try before making the switch. It won't hurt...

Yeah, maybe it was just an impression or it had a bad performance because I played just a little. I played some maps after this comment and it feels better, again, maybe it was just an impression. But for sure, when I was able to open it natively, I'll try a benchmark.

But for sure the Flatpak for rolling distros is a good idea. I really think that they should make the Steam Linux Runtime run in an environment identical as Flatpak. I mean, the whole Steam runs inside that environment

ghost commented 3 years ago

seems the newest glibc 2.33-4 broke something with cs go

nitsvga commented 3 years ago

I did some tests, on the Flatpak version it works but with a some hit on performance, maybe worth it, it's playable.

I think this may vary depending on your PC specs. Having benchmarked CS:GO myself in both 'native' and Flatpak'd versions of Steam on Arch Linux, I didn't experience a performance hit whatsoever. I'd even say that the Flatpak version of Steam has more pros than cons, so I encourage people to give it a try before making the switch. It won't hurt...

Sure. https://flatkill.org/

Doom972 commented 3 years ago

seems the newest glibc 2.33-4 broke something with cs go

It was like that since the previous update to glibc. The new one doesn't seem to fix it.

Douile commented 3 years ago

Using gdb was able to get stack trace (on arch, fully updated)

It seems to be a problem with panorama but idk, cos don't have debugging symbols