If you can't sysrq then you're down to bisecting kernel releases to find the patch that introduced the issue. You could also review for any new features that are enabled by default in 6.7
Have you upgraded all bios / fw versions?
Yes. It works great, including sso.
Compressed into a set of small archives, then each one is posted.
Usually par files are included so you can regenerate a few missing archives. https://en.m.wikipedia.org/wiki/Parchive
We're trialing migrating windows workload to hyperv. We pay for windows licenses anyways so hyperv is free, and it's come a long way. Veeam supports it, so keeps the change minimal.
In the case of an explosive decompression, you can't have that wall trying to resist the pressure difference. It'll blow in a horrible way and probably destroy a ton of circuitry / wiring.
It needs to fail open like this, that design makes sense. The pilots should have been informed though.
An attacker could probably leverage that though to get into the cockpit.
Valid. I'll just have to accept that.
I'm sorry that's how you interpreted my post, as I did not want to imply this was an issue specific to lemmy.world or mean it as an attack upon them.
I've edited my post to not name the instance and try to make it more clear about my concerns for the fediverse as a whole, rather than their admin activities.
I'm looking for more of a conversation with the community here on what we want to see from the Fediverse.
I don't think this is a lemmy.world specific issue at all, and I don't think they meant any harm by removing the thread. They were just being good admins and trying to stay on top of reports.
I don't need to move to another instance, I help run lemmy.ca. I don't like that external users may be seeing a censored version of our / other peoples communities, and I think the community as a whole should be aware of this so they can discuss if they are ok with it.
I'm not sure what you're referring to here? If a post violates local laws of an instance then sure the admins are justified in removing it, but that wasn't the case here. Am I misunderstanding you?
In a post, the security firm said the username and “ridiculously weak” password were harvested by information-stealing malware that had been installed on an Orange computer since September.
So the password being weak was actually irrelevant here, even if it was 32 random characters they would have pulled it off that pc.
Also, can try moving the ssd to another pc to rule out hardware.