Lol wtf

That one DAW for electronic music... The logo had a hexagon or something.. Caustic maybe?

ChromeOS does this well because it's android, a walled garden that users aren't allowed to break. You can buy it at Walmart, and it works well.

Other big "consumer" distro projects (Debian, Ubuntu, fedora, rhel, etc) are similar, especially if you're installing stable releases on hardware that is supported.

The question for me is what do users want their OS to do? My guess is internet, office, print, scan, photos, games, updates, and get out of the way. Almost all big distros will give you that experience already, as long as you don't expect to play Windows games or pick a specialized gaming distro.

Users who want to step outside using supported repos are back to googling for a solution when things are broken, and should see themselves as part of the tech-savvy group that need to fend for themselves.

Gotta go count my files again... oh yeah it's PROJE~14.BAS

Idk why I feel compelled to add this info, but / doesn't have to be local as long as the necessary kernel modules for mounting it are available in the initrd or built into the kernel.

Fake news, works great for me

For me it's I can make Linux do this when I see another system perform well, in contrast with they took my vertical taskbar in windows 11 and I have to gut the system to get it back

I do have to remind myself that I'm still used to living in a world where Linux enjoyed immunity to most "consumer" malware just because it wasn't a popular desktop. Ultimately Linux is not more secure than any other system unless someone put in the work to make it that way.

That makes sense, I was thinking the executable is crashing without any output because something is wrong with the libraries available or executable itself. I should have made it clear that I don't use jellyfin and the steps above are general debugging advice for applications that crash immediately.

For possibly more information on why the core is dumping (lol) try running jellyfin from the cli (probably just typing the path to the jellyfin executable and pressing enter)

If nothing interesting is printed, try adding strace before the jellyfin executable (Google strace, it intercepts all system calls and logs them) if that doesn't work tell strace to follow forks.

Other than that you could start using binary debugging tools to see what shared libraries jellyfin is looking for? Maybe run it in gdb...

Real soft.

You could try drinking the juice out of a can of beans 😹

Maybe watch dmesg when you plug in the drive?

Or look at the logs later. Journalctl -k -f should also show more logs than dmesg when you plug it it which may be informative.