Freetube exists for Android also.

This is my solution also. I listen to audio books on my way to work, and read on an ebook-reader in the evening. Can be tricky to sync when the chapter structure is non-traditional though (e.g. Discworld).

Hm, yeah, I am connected on 5 GHz on all my devices and it is working fine. My main VLAN runs a combination of 2.4+5 GHz.

I have some light bulbs that use Zigbee which would be the only other things running on 2.4 GHz in my home. Could it be a source of congestion, and if so, why did this not happen with the previous computer?

I checked out WiFi Analyzer. What exactly would I be looking for here?

I'd like to keep it neat without anything sticking out and being visible from the cupboard. None of these devices had any issue with my previous computer that was placed in the exact same manner, so I imagine it must be possible to get it working here. But could it be that the network card is simply trash and can't output any stronger? In that case the same kind of USB BT adapter could simply be placed in the cupboard. I think that would be an acceptable backup solution if I can't resolve it with existing hardware.

EDIT: I should add, keeping the door open does not improve anything. The cupboard is wooden.

For playing on a computer and controlling with your phone? If so, there's KDE Connect that has multimedia controls. That might be what you are looking for?

I'm in a phase where I am testing out audio books for the first time, where I will read the physical book in the evening, the audio book when I travel by car and read the ebook-version when traveling to avoid lugging the physical books around. So far I like switching around a bit.

Hehe yeah, mobile gaming seems awful to me as well. Never heard about external fans. Seems like going out of your way to have a sub-par gaming experience.

Depending on how diverse your taste is, you could always try to branch out to something outside of "similar artists". Just look up genre names and start checking them out. If you find something you like, you can use the same " similar artists" approach on an entirely new search space.

Would there not be a risk of corrupting some of the repo files and dependencies lists by just killing it?

I have checked dmesg after your suggestion, but I did not see anything that tipped me off to what might be wrong. Is there anything in particular I should be looking for?

My sources.list file is pretty clean, with 3 https-sources for the Tuxedo OS mirror repos of the original Ubuntu ones. In the sources.list.d directory, there are some that have been added by me, such as for Signal, Librewolf and VS Codium. In total there are 11 files in here, each with one additional source. All except one is https, and the last one is mirror+file. In the process tree for apt-get, there are 13 subprocesses, while there are 14 sources in total (11+3). Could it be that it hangs on the last one here?

EDIT: Would this be a viable way to troubleshoot? I backup the sources and just replace them with a blank sources.list file and an empty sources.list.d directory. If that works, I add the repos back one at the time and see which one that fails. Or could I run into unintended trouble if I remove the main repos, even for a short time? I would think that it just wouldn't find anything and just be happy there are no updates.

As far as I can tell, these are the methods apt uses to get information from the repositories that is listed within sources.list and within the sources.list.d directory. The number of subprocesses almost matches the number of sources there - in reality there are 14 listed, not 13 as is seen in the ps output. I can find one entry that starts with mirror+file, but otherwise there are 13 https entries. So that last line I am not sure what is doing.

Anyways, it seems to me that it gets stuck somewhere updating the repositories list. Right now, I'm stuck with three questions:

1. I'm still unsure as to whether it would be safe to kill the process, as I could imagine that having a corrupted depencies files could be really bad?
2. Also, would killing the process automatically release the lock, or would I need to remove that myself after?
3. Is there any reason to believe that this would even work, seeing as this happens everytime on boot. I imagine that if I kill the process, delete the lock and try to run sudo apt update I just end up the same place again.

This is awesome! I've enabled this in Librewolf and Mull now, seems to work great in both cases so far.