Are you sure S3 sleep is enabled in the bios? On most machines it’s one or the other, not both at the same time. On some Intel machines you can still enable S3 standby, but I know AMD killed it a lot sooner than Intel did.
Windows has powercfg /availablesleepstates to show what states are supported. I’m sure there’s something like that for linux but I’m not 100% sure. You could try dmesg | grep -i “acpi: (supports”
Microsoft says it’s more secure. and that since it stays on its 100% the OSes control which is supposed to be much more secure”reliable” than S3 standby.
Nevermind that S0 standby is so incredibly buggy and awful on windows where it’s supposed to be best. My i9 Thinkpad drops 20% battery in 15 minutes, then goes into hibernation. It has a 50% chance of overheating in my bag and crashing when trying to get in to hibernation.
I can’t say I’m a huge fan of btrfs, in my limited sample size of one I had several episodes of esoteric errors and data loss. It’s anecdotal but filesystems have never been something to give me trouble in any other scenario to date. They just exist and do their job silently in my experience, except for btrfs.
This is what I thought too, but in my case it turned out my drive was busted and btrfs detected an error and went read only… which was super annoying and my initial reaction was “ugh, piece of shit filesystem!” But ultimately I’m grateful it noticed something was wrong with the drive. If I was just using ext4 I just would have had silent data corruption. In that sense other filesystems do silently do their jobs… but they also potentially fail silently which is a little scary. Checksums are nice.
I honestly don’t get these posts, there’s a couple of things that is super weird.
Why does every discussion about Wayland include trashing xorg?
Isn’t the solution pretty obvious, stop mainting xorg if you don’t like to maintain xorg, who is forcing you to maintain xorg?
I really don’t care if I’m using xorg or wayland, I just want something that works, and I have tried wayland and that isn’t the case as of the moment. And I don’t care about the why, because I can’t be like yeah I use Wayland that’s why I can’t be on this video conference.
Just stop mainting it if you don’t want to maintain it, problem solved, move on.
Seems like a redhat problem, so why is he complaining. It wasn’t the developer who signed an agreement to maintain xorg, so I don’t get the argument. Either you do it for the money you get paid, and if you don’t feel like it’s enough, then don’t do it. The developer can just quit and do something else, ask for another project. The only one who is making him work on xorg is redhat.
But why even mention m it in the same context as Wayland, make Wayland work for the end user and 90% of people would not care if thier Linux machine was using Wayland or xorg.
Yes I’ve had multiple issues with video conferencing on Wayland, but my experience is 1 - 2 years old. I just use what works, I don’t have any technical problems with xorg and that is why I use it.
Why does every discussion about Wayland include trashing xorg?
I don’t know, really, but it’s something I feel I’ve seen before. I thought about it and it’s just fanboyism.
Some people get legitimately angry when they see someone using something they don’t like, and I think Wayland fanboys fit in this category to a tee.
I see the exact same kind of backlash whenever someone brings up Nvidia or Manjaro. The fanboys come out and all take it as an opportunity to recommend what they like because they believe their tastes are superior to everyone else’s.
I don't know what's worse, that this is real or that it appears to be relatively serious and not just taking Ubuntu and doing an UwU text transform on every localized string.
Oh, I have no issues with pony people. I was more disappointed that UwUntu wasn't as UwU as I really hoped it would be after I discovered it was a real thing.
At some level I just wanted it to commit to the bit, even if it's at the cost of usability. Maybe only on 1 Apr or something.
Firejail has some big security flaws. There us bubblejail, which uses the way better bubblewrap also used for Flatpaks.
But the Bubblewrap and Flatpak Situation is quite complex. Flatpaks, as well as Podman containers, require user namespaces. Through these namespaces programs can get privileged access to system components, which is why secureblue now has bubblewrap-suid installed.
bubblejail maybe uses that binary already, or it needs to be patched too.
To add to this systemd can do everything they can. You can isolate network, do fire-walling, and sandboxing pretty easily. Any OCI container can be used too if you don’t want to install something too.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.