SecondFaceSoftware / PortalRevolution-Issues

Issue tracker for Portal: Revolution
https://www.portalrevolution.com
6 stars 2 forks source link

Segmentation fault at startup in `shaderapix11.so` #177

Closed quarthex closed 9 months ago

quarthex commented 9 months ago

Describe the bug

The game issues a segmentation fault at startup.

To Reproduce

Start the game from Steam or via the launch_game.sh script in the directory of the game.

Desktop

Stack trace

#0  0x00007bf46a2997e5 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/shaderapidx11.so + 0x997e5)
#1  0x00007bf46a2996f1 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/shaderapidx11.so + 0x996f1)
#2  0x00007bf4524c2a33 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/materialsystem.so + 0xc2a33)
#3  0x00007bf47828932e n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/launcher.so + 0x2c32e)
#4  0x00007bf478289625 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/launcher.so + 0x2c625)
#5  0x00007bf478289665 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/launcher.so + 0x2c665)
#6  0x00007bf47827c763 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/launcher.so + 0x1f763)
#7  0x00007bf478281c24 n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/launcher.so + 0x24c24)
#8  0x00007bf478433cd0 n/a (libc.so.6 + 0x27cd0)
#9  0x00007bf478433d8a __libc_start_main (libc.so.6 + 0x27d8a)
#10 0x000063dfe53850ba n/a (~/.local/share/Steam/steamapps/common/Portal Revolution/bin/linux64/revolution + 0x10ba)
quarthex commented 9 months ago

Here is the output of the launch_game.sh script for additional context: launch_game.log

quarthex commented 9 months ago

I close this report, as the crash is not reproduced with the last update, and open a new one, for I am still unable to launch the game.

quarthex commented 9 months ago

I noticed an update of shaderapix11.so. I guess it has been fixed. There is no mention of it in the changelog.