I second that about Nvidia GPUs. While Linux hardware support is really good, there is plenty of common, mainstream hardware that never was and never will be supported by Linux, usually due to uncooperative manufacturers. For Nvidia, their non-free driver is terrible and the nouveau driver in Linux is hit-or-miss. (Note, many people use either of those successfully, but the likelihood of success drops rapidly with any of: multiple displays, the need to dynamically change outputs, multi-GPU Optimus hardware or even laptops in general, and fully functional hardware acceleration.)

Dude, you don't just pump the combustion result through your house.

I wrote "LPG or natural gas could certainly contribute to humidity levels in some cases," and was thinking specifically of non-vented gas heaters, which are very common in my experience, and are in some cases used for whole-house heating where there isn't a central air circulation system. In this case, the combustion result is literally released into the house.

While this thread is about gas heating, the article is about gas cooking stoves, which in most cases can be vented only at most very poorly (with a range hood), so the risk being dicussed is literally a result of releasing the combustion result into your house.

I believe hydrocarbon fuels produce water (vapor) as a combustion byproduct, so LPG or natural gas could certainly contribute to humidity levels in some cases.

There may also be a separate effect by which the heat strips in an electric furnace dry out the air versus the heat exchanger in a gas furnace, but I don't know about that.

By not using it.

Seriously though, F-Droid (a Play Store alternative) has a lot of nice apps.

From the README at the current published commit:

The current focus is on implementing next-word suggestions, which has become complicated/hit a snag and is taking more time than originally planned. Updates will come when this issue is resolved. Thank you for being patient.

Prior to this, releases occurred quite regularly.

Thanks for posting the GitHub link.

Yes, and it is very annoying. ~~However it does not seem to be happening now with Jerboa 0.0.42.~~

Edit: This is still happening for me too, as of Jerboa 0.0.42, with the AOSP keyboard. It does not happen in any other apps.

I recommend using Molly instead if you need to communicate with Signal users. Note, the Molly-FOSS flavor excludes proprietary Google libraries entirely.

If you are interested in trying an alternative that is unrelated to Signal, I suggest looking at SimpleX Chat.

Just FYI, Signal (Open Whisper Systems) is not FOSS-friendly. The server-side software is not open source, they refuse to federate with other Signal implementations, and they are unfriendly to forks. See:

• https://forum.f-droid.org/t/we-can-include/7373
• https://forum.f-droid.org/t/signal-not-available/19953
• https://github.com/LibreSignal/LibreSignal/issues/37
• https://github.com/LibreSignal/LibreSignal

If you haven't already, check for Nouveau support. And if your card is supported, you may need a kernel parameter. I needed nouveau.config=NvClkMode=15 (but be warned some parameters like that have some risk, like possibility of overheating, and may or may not be applicable or safe for your GPU).

For me, it has worked to just set environment variable DRI_PRIME=1 to use the Nvidia GPU for that specific application. (Maybe this is what Bumblebee does; I don't know.)

In the future, though, I recommend avoiding Nvidia hardware.

As I mentioned in another comment, in my experience Nouveau does a much better job with multi-display and multi-GPU systems than Nvidia's proprietary drivers. Unfortunately Nouveau's actual hardware support is somewhat limited, so that is only relevant for a subset of Nvidia GPUs.

I, too, don't want any more Nvidia hardware.

In my experience they just work once you install proprietary drivers

That's not my experience with dual-GPU (Intel+Nvidia) hardware and multiple displays, where the standard xrandr functions are often used to modify the output configuration.

In my case, the Nvidia GPU is supported by Nouveau, so I can compare it with Nvidia's proprietary drivers "side-by-side". With Nouveau, display output configuration and per-application GPU selection both "just work" (I did add a nouveau.config kernel parameter to enable acceleration). I've never been able to make the proprietary drivers do those things reliably.

So I suggest that users with simple single-display, single-GPU systems are likely to have a better experience with the proprietary drivers.

As is the general consensus here, I do not plan to purchase any Nvidia GPU hardware in the future, especially considering that more recent Nvidia GPUs now require signed firmware, making Nouveau support impossible.