Does the build from the multilib repo give you the same error? It's build date is August 3rd.
If you could post your failure report IDs that would be helpful.
Looks like you didn't receive so many after all...
Processor Information:
Vendor: GenuineIntel
CPU Family: 0x6
CPU Model: 0x3a
CPU Stepping: 0x9
CPU Type: 0x0
Speed: 3200 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
Network Information:
Network Speed:
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 3.16.0-1-mainline
X Server Vendor: The X.Org Foundation
X Server Release: 11600000
X Window Manager: KWin
Steam Runtime Version: steam-runtime-release_2014-07-22
Video Card:
Driver: Intel Open Source Technology Center Mesa DRI Intel(R) Ivybridge Mobile
Driver Version: 3.0 Mesa 10.3.0-devel (git-3d5e247)
OpenGL Version: 3.0
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x1002
DeviceID: 0x6800
Number of Monitors: 2
Number of Logical Video Cards: 2
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 15,04" x 8,46" (17,24" diag)
38,2cm x 21,5cm (43,8cm diag)
Primary VRAM Not Detected
Sound card:
Audio device: Intel PantherPoint HDMI
Memory:
RAM: 32070 Mb
Miscellaneous:
UI Language: English
LANG: de_DE.utf8
Microphone: Not set
Total Hard Disk Space Available: 225214 Mb
Largest Free Hard Disk Block: 105686 Mb
Installed software:
Recent Failure Reports:
Sun Aug 10 21:54:03 2014 GMT: file ''/tmp/dumps/assert_20140810235347_15.dmp'', upload yes: ''CrashID=bp-a7040f9f-0466-4abf-9f04-606f92140810''
Sun Aug 10 21:54:27 2014 GMT: file ''/tmp/dumps/crash_20140810235418_4.dmp'', upload yes: ''CrashID=bp-e3b68988-27ef-4da6-b628-76aad2140810''
Mon Aug 11 08:59:08 2014 GMT: file ''/tmp/dumps/assert_20140810235336_1.dmp'', upload no: ''Couldn't resolve host name''
Mon Aug 11 20:32:30 2014 GMT: file ''/tmp/dumps/assert_20140811223219_39.dmp'', upload no: ''Failure when receiving data from the peer''
Mon Aug 11 20:36:46 2014 GMT: file ''/tmp/dumps/crash_20140811223439_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:39:09 2014 GMT: file ''/tmp/dumps/crash_20140811223702_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:39:55 2014 GMT: file ''/tmp/dumps/crash_20140811223748_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:41:10 2014 GMT: file ''/tmp/dumps/crash_20140811223902_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:43:10 2014 GMT: file ''/tmp/dumps/crash_20140811224102_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:43:39 2014 GMT: file ''/tmp/dumps/crash_20140811224132_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:52:11 2014 GMT: file ''/tmp/dumps/crash_20140811225004_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:52:29 2014 GMT: file ''/tmp/dumps/crash_20140811225021_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:57:31 2014 GMT: file ''/tmp/dumps/crash_20140811225524_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:57:55 2014 GMT: file ''/tmp/dumps/crash_20140811225548_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:58:13 2014 GMT: file ''/tmp/dumps/crash_20140811225605_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:58:57 2014 GMT: file ''/tmp/dumps/crash_20140811225649_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 20:59:37 2014 GMT: file ''/tmp/dumps/crash_20140811225729_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:00:15 2014 GMT: file ''/tmp/dumps/crash_20140811225808_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:00:33 2014 GMT: file ''/tmp/dumps/crash_20140811225826_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:03:48 2014 GMT: file ''/tmp/dumps/assert_20140811230140_16.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:03:55 2014 GMT: file ''/tmp/dumps/crash_20140811230148_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:10:05 2014 GMT: file ''/tmp/dumps/crash_20140811230758_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:16:29 2014 GMT: file ''/tmp/dumps/crash_20140811231422_2.dmp'', upload no: ''Couldn't connect to server''
Mon Aug 11 21:31:16 2014 GMT: file ''/tmp/dumps/crash_20140811232908_2.dmp'', upload no: ''Couldn't connect to server''
CrashID=bp-edad91c2-3982-4ad5-8a4e-df7b72140811
With steam beta update from today: CrashID=bp-884075e5-159b-49f0-b7a5-19ec82140812
Valve note: crash in gameoverlayui BInitializeVGui, looks like VGUI_Setup failed so it ends up using a NULL pointer.
Opted out of the steam client beta, so it's now the new current stable. Crash is still the same I think: CrashID=bp-73f5f71a-116e-4bdb-b107-ee6082140815
The only other change I have is the latest libXext from my system because of https://github.com/ValveSoftware/steam-for-linux/issues/3364
Meanwhile I was curious and had another look. LD_DEBUG=libs says nothing out of the ordinary: http://pastebin.com/raw.php?i=1aQiNZ7q
Except maybe this: gameoverlayrenderer.so: error: symbol lookup error: undefined symbol: __driDriverGetExtensions_i965 (fatal). But contrary to the word "fatal", this message is harmless as I have seen:
It brought me to think about whether there could be a library in the steam runtime breaking stuff, because I also deleted the usual libstdc++.so.6 and libgcc_s.so.1 libraries from the runtime.
And what can I say, when running with STEAM_RUNTIME=0 steam the overlay works (the message about __driDriverGetExtensions_i965 is still there). Now the trouble is finding out which of the libraries in the steam runtime causes this...
I'm on Arch and the overlay in the beta doesn't work for me either. I have the "Enable Steam overlay in-game" box checked. The only error message I can find is
ERROR: ld.so: object 'Linux/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
I tried removing the gcc, c++, and xcb Steam runtimes as other suggested with no change.
@silverhammermba to me on gentoo, that error is strange to me, as I am shown an absolute path to the the overlay library, Example: ERROR: ld.so: object '/home/<userfolder>/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
That's normal. When I start without the steam runtime and the overlay works I get these too.
64 bit applications:
32 bit applications:
wrong ELF class: ELFCLASS32 is not the strange part, it's the Linux/ubuntu12_32/ when /home/<userfolder>/.local/share/Steam/ubuntu12_32/ is expected.
@Tele42 I found that odd as well, especially since there were no directories named Linux anywhere. Turns out it was an entirely new issue: #3641.
I think it works now and I can close this.
Build from Aug 9.
Yes, there are a few other issues already but they don't seem to exactly match.
I have deleted libgcc_s.so.1 from steam runtime because it was too old to support newly compiled mesa drivers on Archlinux.
I have deleted all libxcb stuff from steam runtime because it was mentioned here: https://github.com/ValveSoftware/steam-for-linux/issues/3093#issuecomment-37022796
This one seemed to be the fault of something else, bumblebee? https://github.com/ValveSoftware/steam-for-linux/issues/3199#issuecomment-47330106
I'm sure you have received a lot of crash reports from me already from my playing around.
Looks like this in dmesg:
Happens on mesa intel graphics and offloaded to mesa radeonsi graphics in all combinations with and without dri3.
There are core files in ~/.local/share/Steam/ubuntu12_32/ that belong to the overlay but there's really not much information without debugging symbols: