Threadtools.cpp (2423) : Assertion Failed: Function not implemented

[cmburn]

Hi,
I'm having a rather odd issue with the steam overlay. It has a similar issue if I run it through flatpak, so I'm guessing it doesn't like my kernel config, but I have no idea how to figure out why.

Running Steam on gentoo 64-bit STEAM_RUNTIME is enabled by the user Pins up-to-date! Can't find 'steam-runtime-check-requirements', continuing anyway /home/charlie/.local/share/Steam/ubuntu12_32/steam /data/src/tier0/threadtools.cpp (2423) : Assertion Failed: Function not implemented /data/src/tier0/threadtools.cpp (2423) : Assertion Failed: Function not implemented Installing breakpad exception handler for appid(steam)/version(1.0) crash_20200801222743_2.dmp[5757]: Uploading dump (out-of-process) /tmp/dumps/crash_20200801222743_2.dmp /data/src/tier0/threadtools.cpp (2020) : Assertion Failed: semaphore creation failed File exists /data/src/tier0/threadtools.cpp (2020) : Assertion Failed: semaphore creation failed File exists /data/src/tier0/threadtools.cpp (2423) : Assertion Failed: Function not implemented /data/src/tier0/threadtools.cpp (2423) : Assertion Failed: Function not implemented /data/src/tier0/threadtools.cpp (1850) : Assertion Failed: Thread synchronization object is unuseable /data/src/tier0/threadtools.cpp (1850) : Assertion Failed: Thread synchronization object is unuseable crash_20200801222743_2.dmp[5757]: Finished uploading minidump (out-of-process): success = yes crash_20200801222743_2.dmp[5757]: response: CrashID=bp-35e6664b-3a9a-4d77-99dc-4e3ca2200801 crash_20200801222743_2.dmp[5757]: file ''/tmp/dumps/crash_20200801222743_2.dmp'', upload yes: ''CrashID=bp-35e6664b-3a9a-4d77-99dc-4e3ca2200801''
I noticed an almost identical issue in #167 but I don't get any sort of message about steam being running, seeing as I haven't gotten to run at all on this install. Any tips for where to point me?

[chewi]

If it even happens with Flatpak then it probably falls outside our scope, short of checking kernel options in the ebuild. There's not much to go on here. You could try with a kernel from Fedora, which will be recent and have nearly everything enabled. I've done this to diagnose issues before.

[cmburn]

Thanks for the reply!
I ended up digging around for a few hours, and realized I hadn't actually enabled the SysV IPC in my config. Anyone else who has a similar issue and comes across this github issue, go to "General setup -> System V IPC" and enable it in menuconfig!