[1.2.2] Game disrupts Cinnamon windows manager theme engine

[randomseb]

When I play and then close the t-engine version 1.2.2, the cinnamon windows system on linux has gone all corrupted, as shown in the screen shot..

corrupt.png (91.96 KiB) Viewed 1726 times

Top is before running t-engine, bottom is after. This was just opening to the opening screen menu and then quitting

Also the windows action sounds turn back on, so I guess somehow the theme engine of Cinnamon is getting messed up.

Previous version 1.1.5 did not do this.

OS: Linux Mint 64 running 64 bit Cinnamon desktop manager

[randomseb]

As a side note even the launcher is doing this. As soon as I hit close on it (or the game) it crashes the underlying window decorations of Cinnamon or whatever that's called as seen in the screenshot above

[Aksarov]

I'm not fan of Linux(I havent ever used one), but it does not seems to be getting corrupted, more like switching theme to something, that(for me) seems not so intense on GPU than standart one. So, my guess is it may be, that your GPU cant handle some aspects of ToME and standart theme simultaneously, therefore changing theme. Let me just remind, that this is only a wild guess.

[Suslik]

1.1.5-1.2.2 is a period when t-engine switched to the new SDL version, that may be the case. apparently it's very unlikely to be t-engine fault, just yet another cinnamon instability, but an interesting one nonetheless.

[randomseb]

Of course, it must be the OS's fault that one and only one program is crashing the theme engine (because it won't switch themes anymore after this happens, and restarting the destop manager doesn't fix it.. the linux itself has to be rebooted)



Anyway as mentioned 1.1.5 did not do this, and other games are not doing this kind of thing, just this particular version of the Tome engine.

I'll try updating to the 1.2.3 to see.

[Suslik]

Of course, it must be the OS's fault that one and only one program is crashing the theme engine

Well, actually yes because if any user program can crash desktop manager(intentionally or not) it's desctop manager's/os's fault. Saying that tome is responsible for it is like saying that viruses are responsible for system vulnerabilities. But again since it's not intended if we track what exactly causes it we can make some kind of a workaround.

[randomseb]

Mostly what would be helpful at this point is knowing what the troubleshooting triggers are for t-engine4 - like if there's a debugging command line switch and such

Side note, 1.2.3 does the same thing