Similar problem here.
Linux Mint 13 Maya
Kernel 3.4.5-030405-generic (x86_64)
Processor : 4x Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Memory : 7879MB (4355MB used)
-Display-
Resolution : 1920x1200 pixels
OpenGL Renderer : Mesa DRI Intel(R) Ivybridge Desktop
-------------
error log:
[string "CustomMaterials.lua"]:0: GL error: glCompressedTexImage2D failed (GL_INVALID_ENUM 0x0500)
stack traceback:
[C]: in function 'load'
[string "CustomMaterials.lua"]: in function 'create'
[string "Grimrock.lua"]: in function 'init'
[string "Grimrock.lua"]: in main chunk
[C]: in function 'require'
init.lua: in main chunk
Had this issue too and figured out the solution. They forgot to include the path in the desktop configuration file. The game works fine if you navigate to /usr/local/games/Grimrock/ and launch the game in a terminal or with your file manager. You can also edit the Legend of Grimrock configuration file in /usr/share/applications to include "Path=/usr/local/games/Grimrock/" and this will allow it to launch from the menu.
VonIdler wrote:Had this issue too and figured out the solution. They forgot to include the path in the desktop configuration file. The game works fine if you navigate to /usr/local/games/Grimrock/ and launch the game in a terminal or with your file manager. You can also edit the Legend of Grimrock configuration file in /usr/share/applications to include "Path=/usr/local/games/Grimrock/" and this will allow it to launch from the menu.
Well that indeed appeared to be the issue! Thanks.
Hayduke wrote:My problem must be different. Same result from /usr/local/games/Grimrock
I can't say for sure, but I would assume the issue pertains to you using integrated HD 4000 graphics. I'd try downloading the live image of Mint 14 and giving that a shot as it provides a newer kernel and version of Mesa that both have had lots of work done in regards to Ivy Bridge drivers.
The bug in the first post (core::FileOpenFailedException) is being worked on and Hayduke's issue (GL error: glCompressedTexImage2D failed) has already been resolved and the fix will be included in the next build.