• 3 posts
  • 22 comments
Joined 1 year ago
Cake day: June 30th, 2025

This first happened earlier this week (after updating the system last weekend), and for the second time now. Looking it up the general consensus seems to be that any random reboots are a hardware issue, but I’ve been running this rig (7950x) without issues for years and there are no errors in the journal so I’m skeptical.

I’m not sure if calling what’s happening a reboot is correct neither, one second it shows the os, next second the bootloader without the usual indicators that it turned off and on again.

Last time the journal was very clean with a clear separation between the new boot and the old boot but this time it happened when opening a game from steam so the messages from the two boots are printed interleaved (although the timestamps aren’t). There’s exactly 0.99 seconds between the last message from old boot and the first message from new boot. What’s stranger is that my systemd-boot waits for 3 seconds before booting…

I’m asking here to see if anyone else had the same issue and knows what’s causing it. I updated the system just now to see if it will help.

Edit: Fuck me, after the update random ui elements (like the Proton version selector on Steam) started spasming. It feels like 2023 wayland+nvidia again

Edit 2: Lsi steam works

Edit 3: It didn’t happen since posting this so I assume updating fixed it.

Wrote this to reduce boilerplate when calling a function with a nullable parameter. Language is Dart. I like how concise it is but it feels weird to override []. Would you be okay with this?

extension CallMaybe<R, T> on R Function(T t) {  
  R? callMaybe(T? t) => switch (t) {  
    null => null,  
    T t => this(t),  
  };  

  R? operator [](T? t) => callMaybe(t);  
}  

void example() {  
  int? n;  
  math.sqrt[n];  
}  
  • … but people in that group are a bit of a lost cause.

    touche. I don’t think the existence of other threats is a reason to dismiss this one. And I don’t think simply prohibiting running random executables is sufficient as it isn’t ‘most users’ who are switching to Linux. The people likely to switch to Linux are also the people likely to want to run programs that aren’t yet distributed in repos. I can imagine a scenario where the malware is hidden in a program hosted on a custom flatpak repo and requires permissions for normal operation that’d make flatseal ineffective for stopping the malware.

    The ideal anti-virus in my mind would ignore programs installed from official repos and on access scan ones installed from anywhere else. It’d also keep track of critical vulnerabilities to give you a heads up about updating your system.