I used unstable for years (don't anymore). It broke itself in minor and major ways every couple of months. Maybe it wouldn't boot or X wouldn't start, or the package dependencies were broken and I couldn't install certain packages for a couple of days. Stuff like that.
You will have manually to fix these things from time to time, or do a workaround (like manually downgrading certain packages), or wait a week so stuff gets sorted. Most of the time it works fine though. I imagine the experience is somewhat similar to running arch.
You do not get security fixes, but it's not a massive problem usually, since you'll get the newest version of most software after a couple of days (occasionally longer) after it is released.
Anyway do not recommend unless you want to be a beta tester. I did report bugs sometimes, but almost always by the time I encountered an issue, it was already reported and a fix was already in the works.
I have never used the Steam beta or Proton-GE or whatever information is spreading out there to noobs about what they should do, and I've been gaming exclusively on Linux for more than 20 years. Only do this beta or bleeding edge stuff if you have a problem, and a good reason to believe that will help (like people reporting your specific issue is fixed in beta). Or I guess if you're bored out of your mind. And expect other issues since it's fucking beta.
Reportedly the Russian factory workers are being paid quite well. And the lack of quality is just a myth I think. There's no indication that's actually true.
The real reason prices in the West are so high is that there's a shortage, and shells are supplied overwhelmingly by private contractors, and so the price has multiplied thanks to supply-and-demand market logic.
You may think the Efficient Free Market Knows Best™, so shouldn't they increase production? Think again. They're making record profits right now. Meaningfully increasing production involves building new factories for billions of dollars/euros, which might be ready in a year or two. By then the war will be over and they would have overcapacity, which would be inefficient and prices would plummet. Why would they do that to themselves?
So they're in a great negotiating position vis a vis desperate Western governments. They want guaranteed profits, of the same sort they're making right now, or else the shortage continues.
Maybe it's fine with now, but I looked into a Ryzen Thinkpad a couple of years ago and Linux users reported problems with something (maybe power management?).
I haven't kept up with all the various lines they're up to now, but that looks about right. Also obviously doesn't hurt to google the exact model. Someone I know got an old tabletty Thinkpad with a touchscreen (don't know what model) and on that one the webcam doesn't work on Linux, so something like that can happen.
Not all Thinkpads work equally well. For the best experience, get an all-Intel one, from one of the more expensive business lines, like the T-series. Consumer models are definitely worse, because employees of big Linux-using tech firms are getting the pro models.
You can set the default brightness in mpv in ~/.config/mpv/mpv.conf like this:
brightness=-10
Look in the manpage (man mpv) for other settings. I think any option like --brightness=-10 can also be put into mpv.conf by removing the -- at the beginning.
I don't know if there's a way to make mpv autosave this.
I don't know how to figure out on vlc what sort of output method, codec, or hardware acceleration it's currently using, so I second the other person who recommended mpv.
Because HTTP is simpler, faster, easier, more reliable.
The motivation for a a lot of p2p is to make it harder to shut down, but there is no danger of that for Linux distros. The other would be to save money, but Debian/Arch/etc. get more than enough bandwidth/server donations, so they're not paying for that anyway.
Listen to the parent, this is almost certainly something to do with DNS (i.e. Firefox is not getting an answer for some reason, then timing out, then using maybe a backup DNS server; maybe there are multiple rounds of this). Who knows how your distro and that flatpak produce this interaction, but something is going on there.
I think the hibernation image is compressed by default (all of it). Also, some of what is in your RAM is just files from disk. I think those don't need to be saved into the hibernation image, since they're already on disk. For example, libc.so.6 would definitely be in RAM and in use, but it's also on disk, so no need to save it during hibernate.
So the hibernation image should be substantially smaller than your used RAM.
Yes. You can use lvresize to reduce the size of your logical volumes.
You first need to shrink the filesystems using e.g. resize2fs (exact command depends on filesystem). See the manpage for details, but for shrinking the filesystem it needs to be unmounted, so you'll need to do this from a live usb or something.
After that you can use lvresize to resize the logical volumes. Pro tip: You can shrink the filesystem to e.g. 20 GiB, but shrink the partition to 30 GiB, just to make sure you're not cutting off the filesystem due to some slight error or inexactness, and then afterwards run resize2fs again to resize the filesystem back to fill the whole partition, which it does by default if you don't specify any size.
Also note, since you have LVM-on-LUKS, when you boot into a live cd, you will need to first use cryptsetup to decrypt your partition, and then run vgscan to make lvm find the unecrypted partition.
extension design and strong content filters make AdBlock for Firefox a solid choice for people who don’t necessarily despise all ads
Do these people exist and if so, have they been checked for brainworms?
The rest is also stupid, ublock origin can and does block trackers, and can be made to block more stuff if you want. It's strictly better in every way than the competition, which lets through more stuff, and/or sells your info. The article would be very short though if they just said that.
I think what's going on there is that your suspend thingy looks at the "idle time" (kept track of by the X server or (I assume) wayland compositor) to know when to do its thing. This idle time gets reset whenever you use the keyboard or mouse, but not when you use a controller, because games talk directly to the kernel for controller input, not X. This used to be a serious annoyance because screensavers/lockscreens/dpms kept enabling themselves while playing with a game controller.
Steam "fixed" this some years back, by interfering with this idle time in some way, so your screensaver/dpms/lock wouldn't start. But, annoyingly, steam does this all the time, not just while playing a game.
This seems to work with regular Proton these days, it's even SteamDeck verified.