Still not fixed: xcb_send_fd

[cookiengineer]

When will this issue be fixed? It's marked as fixed, but not shipped yet. After over 4 months. I mean, pretty all Linux users can't use the steam runtime at the moment.

See the other issues #3231, #3238, #3204

Updated a minute ago (Ubuntu 14.04 LTS), still having the identical issues as already reported. Don't want to comment an all the re-referenced bugs as someone closes it and it seems to never get fixed otherwise. I mean, there's already an arch wiki entry for overwriting the library due to no-reaction on your side (https://wiki.archlinux.org/index.php/Steam/Game-specific_troubleshooting#Game_does_not_start_with_libxcb-dri3_error_message)

1. Why is it marked as fixed and not rolled out?
2. How can it be proven to work if not in production?
3. Why are all issues closed if it's not fixed yet?
4. Is there an official upgrade guide for a nightly build?

You currently leave Linux users no other option than fixing it themselves and patching libraries. I wanted to avoid that, but I can't, as nothing happens on your side.

(steam:20690): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
Generating new string page texture 242: 1024x256, total string texture memory is 3,06 MB
Generating new string page texture 243: 8x256, total string texture memory is 3,06 MB
CAPIJobRequestUserStats - Server response failed 2
Generating new string page texture 254: 128x256, total string texture memory is 3,19 MB
Generating new string page texture 279: 256x256, total string texture memory is 3,46 MB
CAPIJobRequestUserStats - Server response failed 2
Game update: AppID 80 "Counter-Strike: Condition Zero", ProcID 20801, IP 0.0.0.0:0
Could not load hw.so.
Please try again at a later time.Error:/usr/lib/i386-linux-gnu/libxcb-dri3.so.0: undefined symbol: xcb_send_fd
CGameStreamThread: Added instance ID 20801 for appid 80
CGameStreamThread: Set render instance ID 20801 for appid 80
Game removed: AppID 80 "Counter-Strike: Condition Zero", ProcID 20801 

[gdrewb-valve]

Are you running the Steam client beta?

[cookiengineer]

I don't know. I was taking part when Steam4Linux was beta back then. Currently, I'm running the steam.deb file that is located at http://repo.steampowered.com/steam/archive/precise/steam_latest.deb as there is still no repo available for trusty.

About Steam dialog says nothing about beta: http://i.imgur.com/2DOqHMK.png

[Plagman]

In client settings, "Account" section, switch your Beta participation to "Steam Beta Update". Can you list the contents and file sizes of ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libxcb*? If you hacked the steam runtime files manually it's possible the update hasn't applied properly and you'll need to reset your steam client install with 'steam --reset'.

[cookiengineer]

Note: I previously removed the libraries in order to fallback to the sys libraries in /usr/lib/.

Thanks for the help! Been there, done that. The update occured afterwards and all the libxcb libraries (including libxcb.so.1) were overridden with the newer ones. Afterwards I did a plain steam profile folders removal and install to verify it is working.

Issues with libxcb are gone now, but the dbus glib bindings are still outdated.

christoph@c2de:~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu$ strings ./libdbusmenu-gtk.so.4 | grep LIB
GLIBC_2.1.3
LIBDBUSMENU-GTK

christoph@c2de:~$ strings /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk.so.4 | grep LIB
GLIBC_2.2.5
LIBDBUSMENU-GTK

Summary: libxcb errors are gone with beta update from 1st May 2014, still having troubles with libdbusmenu-gtk.so.4. Using the fallback os-shipped libdbusmenu-gtk library solves the issues here.

[Plagman]

What's the symptom caused by the older libdbusmenu-gtk binaries?

[cookiengineer]

Seems as you are catching all the strace stuff after the "breakpad exception handlers" are installed. Dunno how to avoid that or disable that.

The PIDs of the processes are incorrectly maintained between the forks and the main process. The libdbusmenu-glib warnings occur a couple times and are not occuring again after a timeout.

Its behaviour is identical to the one described in the wxwidgets framework wherein they had troubles getting it to run with the global menu stuff and having some pointer/reference errors there due to segfaults: http://trac.wxwidgets.org/ticket/14292

I would guess in the blue that your behaviour is a pointer/reference error as well, might be related to the global menu, too. I would guess that because of this changeset that fixed the error in wxwidgets: http://trac.wxwidgets.org/changeset/73277

Game update: AppID 80 "Counter-Strike: Condition Zero", ProcID 4629, IP 0.0.0.0:0
ERROR: ld.so: object '/home/christoph/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/christoph/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 4632 != 4631, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/christoph/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/christoph/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

(steam:4510): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

After spawning the game, the PIDs look like this:

christoph@c2de:~$ ps -ef | grep hl
christo+  4630  4629  0 11:28 pts/1    00:00:00 /bin/sh -c "/home/christoph/.local/share/Steam/SteamApps/common/Half-Life/hl.sh" -steam -game czero
christo+  4631  4630  0 11:28 pts/1    00:00:00 /bin/bash /home/christoph/.local/share/Steam/SteamApps/common/Half-Life/hl.sh -steam -game czero
christo+  4634  4631 11 11:28 pts/1    00:00:15 /home/christoph/.local/share/Steam/SteamApps/common/Half-Life/hl_linux -steam -game czero

When closing the game, the PIDs are correctly maintained again (at least it seems so):

AppActive: active
Installing breakpad exception handler for appid(steam)/version(1398984959_client)
Installing breakpad exception handler for appid(steam)/version(1398984959_client)
0x7fff4c78af38, 0, NULL)      = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
wait4(-1, 0x7fff4c78af38, 0, NULL)      = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---
wait4(-1, AppActive: active
World module shutdown.

Server module shutdown.

Game removed: AppID 80 "Counter-Strike: Condition Zero", ProcID 4634 

[Plagman]

Sorry, I'm not following; what is the actual problem you're seeing outside of that spew?

[kisak-valve]

Closing pending feedback.