I was able to play the game for about an hour initially, and then my ubuntu 22.04 system hard-crashed to power off. Since then, I’ve either crashed on load, or a few minutes into gameplay.
The first time the crash happened, I experienced a few momentary lags, and which got worse before finally locking up entirely requiring a REISUB to reboot. Subsequent crashes have not had warning.
Swapping to the proton version had the same problem. I also tried lowering graphics to medium, but didn’t see an improvement.
Looking at your logfile, you are experiencing the Logitech RGB Keyboard error. This is a known issue on some linux configurations where the system doesnt gracefully handle the issue and continually tries to reload the appropriate DLLs when it should not.
Over time, on Linux systems especially, this causes a slow down, hogs RAM and eventually crashes.
To fix it, you need to disable this setting. RGB Support.
Note that you may have to open and close the settings window to ensure that the status is correctly showing when you change it.
That should improve the overall stability for you.
Proton etc - whatever version you find works. Unfortunately with all the different Linux distributions there doesnt seem to be a recommended solution for everyone - some have great performance on native or vice versa. And stability can also be very different.
Re your system - I am assuming that you are aware of the bottleneck between your CPU & GPU (i.e. CPU too slow). There are instances in LE where its more CPU intensive and you are likely to experience issues that graphics settings are unlikely to make any difference with. From what I can see online, the bottleneck is close to 20% and while running at higher resolution will use your GPU more, your CPU is going to struggle “feeding” it what it needs - this is likely to exhibit as big lag spikes or long load times/instability when loading into new maps or problems with situations with a lot of minions/mobs/screenwide procs… All I am saying is that with a CPU bottleneck, LE is going to do odd frustrating things.
Thanks for that, I had seen some threads mentioning it but wasn’t sure where that setting was. I confirmed that it’s off by looking at the prefs file and restarting the game.
For others finding this thread, the RGB setting is under Settings > Gameplay > RGB Support - it’s not under graphics. For whatever reason the RGB checkbox doesn’t actually change when clicked, which is why opening and closing the settings window was recommended.
Unfortunately, I got another hard lock crash after disabling both RGB options. The Logitech error log is gone from the log, so that’s good, but something else is happening.
My save also got set back about 20 minutes, which is frustrating. I’ll try on a smaller window to see if it behaves differently, and then try on Proton again with the RGB setting changed, and report back.
Until it crashes, gameplay is smooth - I see the CPU issue you mention but I don’t think I’m seeing symptoms, and “CPU is a little slow” should definitely not be what’s causing permanent whole system lockups.
Glad the Logitech issue is no longer occuring. Settings not updating on th UI is a known issue that the devs will hopefully deal with.
Your latest log doesnt show any crashes or anything I can see that I can attribute to any crashing. This usually means that the game froze rather than crashed with a trappable error. Unfortunately this also makes it much harder to figure out the potential cause.
The CPU performance issues can cause crashes - and do so on windows on older hardware. - especially with certain known issues - like heavy minion mob builds etc. So thats not entirely out of the question as a potential issue but I dont think it, at least not on its own, is the root cause of your instability. The issue I have found with slower CPUs is that it can cause stuttering in the game and depending on when this happens, it can cause stability issues that the game is unable to recover from. I.e. it may cause an fps spike at just the wrong moment.
Resolution will obviously impact on what the GPU asks for from the CPU and if the CPU takes too long/longer than the game expects it to do, you may get some sort of timeout which could end up locking things up.
Any reduction in settings can help - so if you drop the res to non-ultrawide, you may see more stability in play. Its easy to try, so worth doing so.
As for Linux itself. I would advise you to try various options native/proton etc to find what seems the best for you. I will reiterate that Linux has proven hard to have a surefire default for everyone so it does require fiddling and testing to find a good default. Sometimes its as simple as chosing proton or native, other times it can be as odd as very specific subsystem versions needing to work together for LE to be stable or a specific GPu driver version /config that needs updating.
There are plenty of people playing LE on Linux successfully, so its very possible but needs a bit of work. I know there are a few Linux users regularly on Discord, so you may want to post there and see what other people are using for best stability.
Running on Proton does not appear to mitigate this with my current situation, and neither does running in a small window. I get about 10 minutes of game play before a crash, and it doesn’t appear to be specifically correlated with any in-game events or having too many mobs on screen.
Files are not corrupted, thank heavens.
I’ll check out the discord for more advice and post here if something does work.
Thanks! I hope you folks can find time to diagnose these things better. One recommendation: you folks would probably find diagnostic value in prepending a timestamp onto your logs. That’d make it a lot easier to tell what’s relevant and what isn’t for crashes.
FYI - I dont work for EHG. I am a normal player like yourself.
File corruption would have been a simple solution to the problem tho. Oh well.
Based on what you are saying, I have a feeling that this issue is going to end up being a combination of underlying factors unique to your setup.
Timestamps in the logs would be very useful… I find that deleting the player.log before a test session is the simplest way around the issue - you just have to immediately view / save it after a crash as its recycled on restarting.
