Literally almost all of my and my partner’s friends and coworkers who are in Europe (including Germany, UK, Finland, Czechia, Greece, and more) have been sick with COVID in the past couple months to (especially) right now — it’s very real in Europe still.

People are all talking about COVID right now, in messages, emails, video calls, Mastodon, and more. (It’s usually to inform others that they’re sick and can’t work or meet up. But also complaining that doing basic stuff is difficult.)

Europe is a large place, of course, but at least in a lot of it, COVID is sadly still going strong.

I basically gave up on podcasts on the desktop and only use AntennaPod on my phone. When I’m at my desktop, I have my phone paired with my computer via Bluetooth and play that way. I can pause it on my computer via KDE Connect (GSConnect on GNOME).

Bluetooth audio from phone to desktop works on Fedora Linux quite well. It probably works on other Linux distros too. I’m guessing it might also work on other OSes like Windows and macOS.

KDE Connect is available on Android, iOS, KDE (and can run on other desktops too), GNOME (via the GSConnect extension), Windows, and macOS.

This solves the syncing problem by sidestepping the need for it. My podcast state is always correct and I always have my podcasts with me, even when out and about.

Docker on Windows and Mac also runs containers through a VM though. (It’s more obvious on Windows, where you need WSL (powered by a VM) and Hyper-V (a way to run VMs on Windows). But on a Mac, VMs to run Linux are also used to run Docker containers inside the VM.)

Podman Desktop helps to abstract VMs away on Windows and macOS: https://podman-desktop.io/

For the command line, there’s “podman machine” to abstract away the VM. https://podman.io/docs/installation (installing on macOS is mentioned on that page and Windows has a link to more docs which also uses the podman machine command.)

As for Docker compose, you can use it directly with Podman too: https://www.redhat.com/sysadmin/podman-docker-compose (there’s also podman-compose as well). The only thing Docker compose doesn’t support with Podman is swarm functionality.

Docker compose can even work with rootless Podman containers on a user account. It requires an environment variable. https://major.io/p/rootless-container-management-with-docker-compose-and-podman/ (it’s basically enabling the socket for podman and using the environment variable to point at the user podman socket)

You can set up mount points on Linux, at least in GNOME, very easily. (It’s even fully automatic for external disks.) I’d be surprised if it isn’t as easy in KDE and other desktops too.

The problem here (at least from what it sounds like) isn’t setting up mount points. The problem is fixing an incorrect fstab on the disk that’s causing the system to hang on boot.

(This isn’t a typical situation, which is why I also asked about how the partition was added to the system.)

Good point! GNOME Disks can do this, actually. I didn’t think about that.

(Edit: However, I think it’ll just edit the /etc/fstab of the running system. In other words, the one of the live session, not the one on the installation.)

My first attempt to try to fix something like this would be to:

1. Download Fedora Workstation live media. (Within Windows or some other computer that boots.)
2. Flash it to a USB stick.
3. Reboot to the live desktop from the USB stick. (It might require pressing F12 or some other key combo during boot.)
4. “Try out” Fedora. (That is: do not install.)
5. Open GNOME Disks. (I think it’s included. Otherwise, you can sudo dnf install gnome-disks to install it temporarily on the live session.)
6. Try to mount the main filesystem that contains /etc/fstab (it should ask you for the LUKS password.
7. Comment out the Windows mount point. Or if you want to keep it (if the partition still exists and is just “dirty” and still needs a check from Windows) add “,nofail” after “auto” to the options in the line for the mount, so your system should still boot without that mount point.
8. Save the /etc/fstab file.
9. Shut down the computer.
10. Unplug USB stick.
11. Boot computer. Linux should successfully boot… hopefully. 😉

I’m also wondering: How did you add the Windows partition to Fedora? Was it from within Fedora’s installer (aka: “Anaconda”)? Or did you add it in a different way?

(BTW: I use Silverblue and have a long history with Fedora. 😁)

Also: Inspector Gadget.

An international US, French, and Canadian production.

Penny (the “hacker” niece) and Brain (the intelligent dog) solve all of the cases that Inspector Gadget (cyborg cop) bumbles through, even though he’s essentially RoboCop with gimmicks.

You can do this with the Flatpak version of Steam, but you have to give it access to the disks.

Flatseal is the easiest way to do this.

1. Open Flatseal
2. select Steam
3. scroll down to the “Filesystem” section
4. click on the + icon on the “Other files” area
5. either put in the full path, or use something like “/run/media” to give it access to all user-mounted storage devices (this value may vary depending on how the disk is mounted)

Restart Steam (if it was running). You should be able to access additional devices.

the driver’s for my brother laser printer

I have a Brother printer + scanner too (MFC-L2750DW). Many Brother printers (and a lot of non-Brother printers too) are supported by default in Fedora using a “driverless” method. It’s part of “IPP Everywhere” (https://www.pwg.org/ipp/everywhere.html), AirPrint (Apple), and Direct Print (Microsoft), and most printers support it these days, and Fedora supports all of these. (Other distros likely do too.)

At least in GNOME (on Silverblue here), if it doesn’t already show up and work, you can click on “Add Printer…” and it should find and add it. KDE and other desktops will likely be different — although hopefully not much different.

Scanning with “Document Scanner”, aka: “Simple-Scan”, detects my networked Brother printer for scanning without having to do anything too. https://flathub.org/apps/org.gnome.SimpleScan

I hope this helps!

undervolting requires turning off secureboot or a patch

I haven’t looked into undervolting much. I know some people have mentioned CoreCtrl; I haven’t managed to figure it out yet.

If it requires turning off secureboot or a patch, that’s a bummer and might be why I couldn’t find the settings in CoreCtrl. I haven’t seen this when looking it up a while back, however (but the Internet is big). CoreCtrl setup docs @ https://gitlab.com/corectrl/corectrl/-/wikis/Setup don’t mention either.

I do see that it requires setting a kernel flag, which on ostree-based distributions is:

rpm-ostree kargs --append=amdgpu.ppfeaturemask=0xffffffff

(And then reboot.)