"No pain, no gain"
Some notes on the process of heading off the next upgrade apocalypse.
Loosely acknowledges the existence of the official Linux Mint Installation Guide.
"No pain, no gain"
Some notes on the process of heading off the next upgrade apocalypse.
Loosely acknowledges the existence of the official Linux Mint Installation Guide.
Brave is a fork of Google's Chromium that provides a privacy-respecting alternative to the commercial Google Chrome browser. I use it where LibreWolf won't work at all or without unreasonable effort, like when I need WebUSB or a site's code spectacularly fails to conform to web professional best practices.
It goes without saying that what follows reflects my experience on Ubuntu 22.04 LTS desktop at a moment in time. Like many other software apps, the availability and configuration of some features change over time: so YMMV!
Brave works on all platforms. Since I'm currently on Ubuntu desktop, I follow the installation instructions for that distribution.
The defaults for Brave are pretty reasonable, but here are the changes I make in Settings:
IronFox is a privacy-minded fork of Firefox mobile for Android. It comes recommended by the LibreWolf project, who have a similar privacy focus for the desktop. What I like most about both of these forks is that their choice of defaults requires minimal effort on my part to set up and maintain my primary browser.
Because I already make use of F-Droid for installing open source apps that are not included by Google's Play Store, I have added IronFox's standalone F-Droid repository to the F-Droid app on my Android devices and use that to install IronFox.
Here are the changes I make to Settings in IronFox after installing:
LibreWolf is my standard desktop browser. It is a Firefox fork that makes my llfe easier by having sensible privacy defaults out of the box.
As I am currently on a Debian based distribution (Ubuntu, likely transitioning to Mint), following these instructions.
Because of its shipping defaults, I have found LibreWolf quick and painless to configure. Here are the changes I make in Settings after installing:
The decision to disable/change the venerable Ctrl-Alt-Backspace keyboard shortcut for killing the X server in the Ubuntu/Gnome desktop has been a persistently unwise one.
At least for now, the most straighforward way to restore it is to install gnome-tweaks. Then go to:
Keyboard & Mouse > Additional Layout Options > Key sequence to kill the X server
Ctrl+Alt+Backspace: checked
References:
Recent releases of Android famously ignore/bypass any local (i.e., self-hosted) nameserver passed along by DHCP or specified in a wifi profile, in favor of Google's own public nameservers. The only other option is to enable "Private DNS" (DNS over HTTPS, or DoH) in the global network settings for your devices. The stated reason for this are easy to understand: to avoid compromising security or privacy when connecting to random wifi networks. But we all know there's more to it than that. The most charitable explanation would be that Google (and others, including Mozilla) is fixated on getting everyone on DoH, even at the cost of frustrating we few peasants who want to run our own local DNS. Let them eat cake.
There are a few alternatives available to those of us who would like to address local hosts and services on our home networks by name, rather than IP address:
Alexandre Lotte, the author of icsp describes it as a "Small, fast and simple command-line tool to conver calendar exports (.ics files) into TSV/CSV files for easy analysis and usage in broader use-cases."
And so it is.
I had accidentally imported a holiday calendar into my default Proton Calendar, when I realized two very horrible things: (1) I had no backup; and (2) no one really provides tools for removing entries from calendars in bulk. Later, I would add "Proton Calendar doesn't have a versioning system". But then, no one else does either.
I was screwed.
A few minutes (OK, about a half hour) of searching the Internet, and I found icsp: which turned out to be everything its author wrote that it is.
NOTE: This was written while experimenting with using podman in lieu of docker. But please be aware that not all docker solutions are compatible with podman, and some may still require root even under podman.
Going rootless is one of the main reasons for switching to podman. But if you're running shared services on server for internal users and don't want a separate account for each app, creating a special (non-privileged) account for all pods may be the answer.
This work was done on Ubuntu 22.04 LTS using the shipping Ubuntu package for podman (podman-3.4.4+ds1-1ubuntu1).
Install podman and enable the podman.socket service (I'm using the version in my distro's official repository):
NOTE: This was written while I was experimenting with using podman in lieu of docker, something I'm now looking at again. Not all docker images work with podman, so be prepared to struggle with the system and to engage in many fruitless Internet searches.
OK, so who knew podman containers won't automatically start on reboot? Yeah. Me neither.
Found out after a family member complained about getting a 500 error when trying to reach a PiGallery2 instance I had set up on the home server.
Fixing this is easy, as detailed in Pratham Patel's "How to Autostart Podman Containers?" over on Linux Handbook: A systemd servic
Running Ubuntu 22.04 LTS with Ubuntu Desktop on X11.
After setting dock (dash to dock extension) to auto-hide, it won't reappear if any app is full screen.
Turn off "require-pressure-to-show" in dconf settings for dock.