Makes sense. Well, best of luck with it. That’s super annoying, sorry I couldn’t help. If you do figure it out and remember this, I would love to know what the answer was!
Makes sense. Well, best of luck with it. That’s super annoying, sorry I couldn’t help. If you do figure it out and remember this, I would love to know what the answer was!
Did some looking around and what I found is it could be a sign that the cable is starting to fail:
https://askubuntu.com/questions/1118738/whats-the-likely-cause-of-a-get-monitor-geometry-assertion
Do you have another cable you could try?
It could also be a bug in Gnome, since you said it only happens after something like a kernel update. I wonder if it would happen if you used a live usb of gnome, and if so, would it happen if you used a live usb of KDE or some other desktop manager.
Any system logs that might be related to the display not being detected properly?
Since you’re using AMD graphics, you’re using the open source drivers right? The proprietary AMD drivers are not good.
Well, issues 1-3 could all easily be GPU driver related. Which GPU are you using, and what drivers?
The Steam UI thing sounds like an issue like maybe hardware acceleration being disabled?
They generally have really great linux support for all of their hardware (touchpads, fingerprint readers, etc.), and provide bios updates via fwdup. They are also just nice laptops.
This is making me realize that I have never encountered this equivalent of a blue screen of death on Linux.
Ubuntu/Canonical is the Microsoft of Linux distros. It’s no surprise they were the choice for WSL.
Ubuntu has been forcing decisions on users and embedding advertisements for a long time.
Examples that immediately come to mind…
apt install
I had similar issues. When first booting into plasma6, my bottom panel was changed to floating. Changing it to not float made it spaced from the bottom of the screen.
While trying to fix that, I somehow managed to move the pinned icons all off the panel and onto the desktop, but they were unable to be clicked or moved. I ended up restarting for unrelated reasons and they snapped back to the panel.
I think there were other wonky issues with the edit session, but I don’t recall specifics. Good luck!
Edit: this was on a wayland session with integrated amd graphics.
Their CEO has gone out of his way to shit talk Linux multiple times on Twitter/X, spreading false information, he is also vehemently against doing the bare minimum to allow their games to work on Linux (enabling EAC support for proton in their games, which by their own words is just a checkbox). They also have no Linux support in their embarrassment of a launcher, which is why everyone recommends Heroic, even when using Windows because it actually has features.
A one time donation of what amounts to an insignificant rounding error for them to try to appease people unhappy with their stance on Linux does not mean they are not “against” Linux.
I found this amusing enough to try it out. It does actually compile (I used g++ for this). However, the current implementation just goes into an infinite loop if you enter a number >= 2.
I think the original author meant to do n -= 1 rn
in the tweakin
loop that is inside the bussin
loop. That way, at some point n % i finna cap
will be false, and i
will bouta
. Which then makes the expression i <= n
in the bussin
loop eventually false, so we stop bussin
and yeet cap rn
.
However, that would mean that the intention of the program isn’t to output prime factors, because even with this fix it does not do so. The structure of mf chief()
also doesn’t suggest that is the purpose as it is missing another tweakin
and sussin
like this example of calculating prime factors in C++.
Example run:
$ ./zpp.exe
Enter a number larger than 1: 50
2
7
8
47
That is huge. The power management changes and being able to set brightness per monitor are pretty nice too.