Not an expert but: tldr don’t.

Battery calibration is supposed to help the battery’s firmware figure out how low the battery can go. It also tends to hurt your battery, so you should avoid performing these calibrations and keep the charge between 20% and 80% as much as you can.

It seems what you’re trying to do is improve battery estimation by the OS on a new machine. And in that case, Is just trey trip love* I’d just try to live with possible insecurity of not knowing whether the machine has 15 or 25 minutes left.

• Thanks, auto-correct!

I never bothered with banking apps. (Outside of the virtual debit card app from my bank. That one did install successfully. However, I never got try out in store because it deleted my virtual card after a few days and I didn’t care enough to set it up again.)

I use Calyx on a Fairphone 4. It’s not totally degooglified, since it comes with MicroG which is used to connect to Google services. I use Aurora Store and a couple of original Google Apps like Gboard too (none of my Google apps can access the internet, since they’re behind the built-in firewall). It works well except call functionality which can be wonky and there’s the issue that a lot of apps from Play don’t work well with MicroG. I only use a small selection of Play apps though, so it doesn’t bother me too much.

X11 is not made with security in mind. At the point where you disable Wayland, you can basically use native apps rather than flatpaked apps.

You have a point to some degree, yet I still think it is defensible to make this post. He majorly altered software

• downstream
• against user expectations
• for somewhat spurious reasons
• seemingly quite ad-hoc

He then went on to defend that decision in a less-than-graceful way before announcing there will be a second, new package.

But, to make it clear: I certainly don’t approve of hate directed toward him and I don’t have a personal issue with him.

Yes, these are off-by-default features.

Afaiu it, he added a second package with (quote) “all the crap” later, after the storm.

And no, it wasn’t just the favicons feature that was removed (which like … is that really such a big privacy issue that you need to remove it from the binary?). Support for Yubikey was removed as well — which is not a privacy issue. The reasoning mentioned by the Debian maintainer is that all of these features might turn out to be security issues in the long run. Thus, in his view, a password manager application must do nothing but provide access to the database within the app.

I find it an interesting example of diverging upstream, maintainer, and user interests in any case.

GIMP has had a GTK 3 port in development for years. They just lack the developer bandwidth to finish it. And in general, using EOLed libraries for your very popular application is not great, not for security, not for usability, and not for compatibility with modern systems.

Porting Wayland compatibility to GTK 2 would be incredibly out of scope for GIMP developers. :)

GTK is a UI toolkit, i.e. a piece of software that draws uniform-looking buttons and scrollbars and the like.

GTK used to stand for “GIMP toolkit” but GTK and GIMP development are now entirely separate, so much so, in fact, that 13 years after the release of GTK 3 and 3 years after the release of GTK 4, GIMP still hasn’t upgraded to either.

I guess it’s an appropriate name if the file collects the URLs of sites that trick you into installing malware.

.db is usually short for “database”. I’d suspect this file is part of an anti-virus tool or similar. Where did you find the file? Edit: phishingurl indicates that it’s part of some URL checking functionality of a browser. Not sure which browser puts that straight into .local/share though. Might be a KDE thing.

Edit 2: Qkall’s answer says it’s KMail.

Is not up to SUSE’s marketing department, most of which is from the US, either. The company has a German origin, had German founders (they’re all out of the company at this point though), and the company name used to be a German acronym. The correct pronunciation is the German one.

(See the update @barbara added. Lisa Sherwell actually took the effort to learn the correct pronunciation. Part of the reason why is that she was actually involved in planning the new German office of SUSE.)

That depends but many people will be familiar with the absolute basics of English pronunciation and likely recognize the word as English too, I think.

It’s wrong nonetheless.

Well, “nome”, with a silent G is the correct pronunciation of “gnome”, as in e.g. “garden gnome”.

SUSE originated in Germany, where it’s just the normal pronunciation. “Suse” also pre-existed as a nickname for “Susanne” (of course, the company name was derived from an acronym which isn’t used anymore).

The issue comes in when non-Germans, especially English-language natives try to pronounce the word. English pronunciation is incredibly inconsistent. Hence English speakers tend to fail (very confidently) when pronouncing foreign-language words.

(Fwiw, Germans and many others don’t know anything about the silent G in “gnome” and will happily pronounce GNOME the way the project intends without being told. Similar things are true for the I in Linux.)

The marketing idiots who published this are Americans. The pronunciation is borderline correct but not quite.

You can’t even read the title of the window properly, and it’s a short one! And there’s this ugly scramble of icons all clustered on the left. This may work and you may be used to it but Gnome is certainly not designed to be used like that.

Hiding all the buttons as the poster above told you to do is worse though.

So this is what happens when package maintainers fail to find the problematic bits during package updates. I’ll be honest, after seeing how Linux package management is done (automation and semi-automation galore) and by whom (people who often don’t know the programming language of the source and who don’t have much time either), I am more surprised that it took this long.