Inloggen
|
taal
Български (Bulgaars)
čeština (Tsjechisch)
Dansk (Deens)
English (Engels)
Suomi (Fins)
Français (Frans)
Deutsch (Duits)
Ελληνικά (Grieks)
Magyar (Hongaars)
Italiano (Italiaans)
日本語 (Japans)
한국어 (Koreaans)
Norsk (Noors)
Polski (Pools)
Português (Portugees)
Português-Brasil (Braziliaans Portugees)
Română (Roemeens)
Русский (Russisch)
简体中文 (Chinees, vereenvoudigd)
Español (Spaans)
Svenska (Zweeds)
繁體中文 (Chinees, traditioneel)
ไทย (Thais)
Türkçe (Turks)
Help ons Steam te vertalen



I ran the binary with gdb:
$ cd ~/.local/share/Steam/SteamApps/common/Cubemen
$ LD_LIBRARY_PATH=./:Cubemen_Data/Plugins gdb ./Cubemen
... and got this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xf79ae700 (LWP 7355)]
0xf35da849 in ?? () from /usr/lib32/fglrx/dri/fglrx_dri.so
(gdb) bt
#0 0xf35da849 in ?? () from /usr/lib32/fglrx/dri/fglrx_dri.so
#1 0x0b137170 in ?? ()
#2 0xf3553390 in ?? () from /usr/lib32/fglrx/dri/fglrx_dri.so
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Which... doesn't say much.
I'm using the AMD beta drivers from precise-backports. Package name: fglrx-experimental-9; Version: 2:9.010-0ubuntu0.1.
EDIT: ok, I've created issue report on GitHub https://github.com/ValveSoftware/steam-for-linux/issues/712
UPDATE: Issue closed. Valve member said we should contact developer. I will do it and give you update.
Thanks everyone for the effort in both reporting this issue and testing out different driver versions and posting your findings here. It's super helpful.
Please use my support page... http://cubementd.com/support/
Thanks
Thank you for your effort, glad to see some devs care about their ports.
I've just sent my report with my hardware info and the player.log
You probably encounter same bug as all of us. It's related to Unity Game engine (which the game is based on), not Unity desktop environment.
Yeah the error message looked similar.
Thanks for the log, I have passed it on to the Unity Game Engine devs. They have confirmed the issue, but it seems it is going to have to be up to AMD to fix the ATI driver bug as every test so far shows that ATI broke things with their latest drivers and some older drivers are working.
The main issue here is if Unity put a fix in for the bug and then ATI fix it, it might break Unity again and I dont think they are prepared to do that with AMD breaking drivers so often.