Uhhhh, that just gives people more reason to be depressed. Just about every young person I know is on antidepressants because life is absolutely shitty in a capitalist dystopia.
I'd focus on KDE here, it sounds like the gui auto mount service is barfing for some reason. Does the drive mount normally when you boot to the CLI and try to mount it by hand?
Per the subreddit drama thread about this a couple of days ago the accuser has publicly recanted the accusation. I feel bad for this lady, she's getting absolutely shit on by the Internet for something that sounds like it didn't happen.
Because we already know that fash eat their own and it's not shocking news so it doesn't generate views or clicks.
On the flip side MAGAts won't consume coverage that's critical of their politics so they're not interested in coverage either.
Basically one half of the population doesn't care because these behaviors are expected and the other half refuses to acknowledge that they're capable of bad behavior.
Hey, tin whiskers! I haven't seen this happen in person since my Jerry rigged Celeron 333A killed itself. I'd created a monstrous homebrew cooler with raw bar stock aluminum as an IHS with a big fat peltier cooler and a huge heatsink so I could run the thing at 550mhz. The aluminum eventually grew a tin whisker after the machine had been running in my closet for a good 4 or so years and shorted the Celeron carrier board.
Apparently this was a pretty big problem in aerospace back in the early days, their electronics were particularly prone to this failure mode.
mount -o bind /source /target or use fstab or systemd mount units
Can you explain a bit more please?
Container software often needs permission for both the virtual path (wherever the bind mount is mounted to) and the source path (wherever the original is mounted from. It's not terribly complicated but it does mean fiddling with access permissions in flatpaks.
You should read about bind mounts, they're fairly straightforward and there are many, many, many explanations available online
Lots of internet people says that one can't create mount points across different filesystems.
Citation needed. Bind mounts work just fine wherever you put them, again: you need to mount your source filesystem somewhere then you can bind mount paths from that mounted filesystem anywhere in the running VFS tree. You should Google linux bind mounts, they're quite simple.
problems that symlinks do
Can you explain more please?
Some software has problems following symlinks properly and fails to work unless given the symlink source path instead
For data like this from another filesystem I usually like to mount the entire volume somewhere private (like under /run) and then bind mount the parts I want to use into their desired locations (like /home/foo/Download, etc.)
I do this with a second ext4 drive that I use for performance sensitive storage with my primary btrfs system root. It works well, just be aware of edge cases involving containers (you may have to grant the container access to the original mount location under /run in addition to the bound path. This is definitely a gotcha when working with those paths with flatpak.)
Yup, they took the 90s era broadband grants and just pocketed them because they knew that the Bush era FCC wouldn't pursue the matter.