Linux Mint - problems with freezing since v5.0

[revevil]

Hello,

I don't think I've told anyone this before, but I've been running this in Windows for a while now. It used to run great in Linux Mint in version 4, but ever since 5.0, it always freezes up after starting the game usually about 30 seconds to 2 minutes after running it. I have tested it with and without mods and get the same results. I also tried switching the driver under "Advanced Options" from OpenGL to OpenGL 3.0, but it made no difference.

I just wanted to ask if anyone else using Linux Mint has had an issue with Luanti freezing up. I am using v22.1, the latest release so far, but this issue has been persisting for a while. I just installed the latest version of Luanti, and it still freezes up in Linux Mint. I wish I knew for sure what the cause was, but I don't. I have run other software, and it runs just fine, but I do have this freezup issue with certain things, Luanti being one of them.

[Blockhead]

5.0.0 has been out since 2019-03-04. Even allowing for a reasonable delay to put it into the package archives for a new version of Linux Mint, you should have used *something* past that version. Have you been on a hiatus, or have you been using a really old distro?

What does ~/.minetest/debug.txt say before and after that lockup? Anything at all?

Have you considered compiling from source to see if it's a problem with the distro package?

[revevil]

No, I have been updating every single version since 5.0, because I have always wanted to test the newer versions. I was just saying that I have had the problem ever since version 5.0, but the problem was absent during the 4.x versions. I did take a look at the debug.txt file, but it did not directly indicate any graphics issues. I may need to make the debug.txt more verbose (I believe I saw an option in the settings for that.) It would be nice if it gave an indicator if it was having any graphics driver issues. I'll go do that and get right back to you. And no, I have not tried compiling from source yet either.

Edit: I have just located the options for OpenGL debug and Verbose debug. I will let you know if I find out anything.

[revevil]

I have just ran Luanti with OpenGL debugging turned on, once with verbose debugging, and once with error debugging. I have looked through both logs and have not seen any direct errors with OpenGL yet. One thing I will say is that when Luanti freezes, it locks my system up cold. What I mean is, at that point the only thing I can do is hold the power button to shut down. I cannot Crtl-C out of the program, or do anything else at all. One more thing, I have 2 quadcore CPUs that run at 3 ghz. But they are old, from 2007. I'm not sure if my CPU instruction set might be too outdated. I ran CPU-X and copied this line from the instruction set: MMX, SSE(1, 2, 3, 3S, 4.1), VT-x, x86-64. I checked both debug.txt files and have not located any CPU errors either.

[goats]

i've run probably every release version since 4.12 on some version of Mint, on quite a few machines, and never had an issue*. i either compile or grab an Appimage as i prefer run-in-place builds.

*There can be issues running versions of Luanti/MT that are too old to be supported by a newer OS version, but it would unlikely look like your issue at all.

It's possible, if you use a spinning disk, that there are bad drive sectors or other issues that just don't turn up when using drive tools and are not automatically caught by drive firmware which can cause similar behavior, but not that consistently, and there should be a warning on some occasions at least.

It could be a fairly unique issue. Sometimes it seems like most of the computer issues i have ever dealt with are weird edge cases.

[Blockhead]

... It's possible, if you use a spinning disk, that there are bad drive sectors ...

Possible on an SSD too, a bad sector is bad whether it's a NAND cell or magnetically stored information.

[Linuxdirk]

Maybe it has something to do with Wayland? Since Luanti uses SDL2, the client runs as native Wayland client … BUT most likely runs using an SDL2 compatibility package for SDL3.

Something in this chain could cause the freeze.

[goats]

[quote=Blockhead post_id=446855 time=1758643084 user_id=24958
Possible on an SSD too, a bad sector is bad whether it's a NAND cell or magnetically stored information.
[/quote]
There was a reason for the rest of the sentence qualifying the quoted bit, but maybe i am making terrible assumptions about devices which literally wear out their sectors as part of their design. One would hope they were better at marking bad sectors. If not, this is very sad. Something for me to keep in mind for the future, thanks.

Maybe it has something to do with Wayland? Since Luanti uses SDL2, the client runs as native Wayland client … BUT most likely runs using an SDL2 compatibility package for SDL3.

Something in this chain could cause the freeze.

Blergh! i have never had Mint install a Wayland server/compositor on me, but this is something else i will remember for the future should i ever have to live with a Wayland stack.