That doesn’t mean anything. I once had an issue where every few hours, a random application would crash on Arch Linux, but not on e.g. Debian or Windows. But this wasn’t an Arch issue per se, but was instead related to an UEFI overclock setting (which defaulted to on). After turning it off, everything worked fine.

So while it seemed like an Arch issue, it was actually hardware/overclock related, it’s just that the other OS wouldn’t run into the trigger for the crash.

Isn’t this what Flatpaks are doing?

While this is good advice in general, it doesn’t apply as much in OPs use case since he’s using an immutable distro.

Don’t feed the troll…

From the Hyprland wiki:

A special workspace is what is called a “scratchpad” in some other places. A workspace that you can toggle on/off on any monitor.

Since GNOME definitely doesn’t support workspaces per monitor (and I haven’t seen an extension that does), I don’t think this is possible.

Because there is only one alternative (Xorg/X11), and it’s pretty outdated and not really maintained anymore.

For now it’s probably still fine, but in a couple of years everything will probably use Wayland.

That’s what I tried, it never showed up, even though the repo was enabled. Had to install it via terminal.

Why won’t they just use Calamares?

it doesn’t even host it’s own repos

Yes, and that’s a good thing, otherwise it would be like Manjaro.

EndeavourOS is perfect if you already know your way around a Linux system but don’t want to spend the time and effort to setup Arch.

I think 535 is the only option for Wayland gaming right now, everything else is a flickery mess.

AFAIK we still need this merge request here for it to actually affect 99% of games, because they all run with Xwayland, right? https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967

Just take a look at the video on the main page, it demonstrates it pretty well: https://hyprland.org/

EndeavourOS. Can’t you see the original comment from blackstrat?

It’s basically base Arch with a graphical installer and some reasonable (but optional) default packages.

I already did a UEFI reset, that didn’t help. As far as I can tell, it’s only GUI applications, I haven’t seen a segfault for something else so far. Unfortunately I don’t have any other GPU right now.

It seems that a solution was found though (at least for now, it didn’t crash since a few hours) here: https://lemm.ee/comment/8161085

I’m not sure, here’s the entire dmesg output: https://pastebin.com/MZfhB0xK

I’m a bit speechless right now. I’ve disabled PBO and didn’t have a single crash since then, everything’s been running fine for hours. Just to make sure that this really was the issue, I’ve enabled PBO again - but still haven’t experienced any crashes in the last hours. I have no idea how simply disabling and then enabling the feature again fixed my issue, but for now it seems like all is well.

Do you have any explanation for this weird behavior?

Anyway, thank you very much for your suggestion, looks like this actually did the trick!

But I also ran a live EndeavourOS from USB and the same crashes happened.

What voltage should I try? It’s currently at 1.35V, and I’ve read somewhere that this is the highest “safe” voltage.

Motherboard firmware is up-to-date, and I’ve already tried disabling XMP. I’ll give disabling PBO a try, thanks!

I don’t necessarily have to run at 3200MHz, if it means that the system is finally stable. But since it’s already crashing at the default 2133MHz, I suppose there’s no use in playing with the voltages?