KDE Connect can transfer files over WiFi, it’s likely preinstalled on anything with KDE Plasma (eg SteamOS has it by default in the desktop mode), but it can also work with GNOME with the gsconnect extension. There’s also LocalSend, Syncthing and probably many more

Loving just the stock KDE Breeze theme

It already is GNOMEd, this is just flatpak dependencies

Sort of bad that we never tell newbies what to base their distro choice upon, but rather just tell them what we personally like.

Maybe the installer ease of use is an important factor, buy not the most. Nobody explains the biggest difference which is how up-to-date the stack is (conservative base vs. rolling base) and that the choice of the DE is even more important choice than the distro. How come that pre-installed NVIDIA drivers are selling point even when their version is behind?

I’m baffled on how many people recommend something like Nobara, just because they preinstall a ton stuff, while it’s just a hobby project with Discord server. Maybe they improved it now, but not so long ago it was very very bad at handling updates, so the system was super easy to install, but very difficult to keep in shape over time. Even if they fixed it now, this is NOT an established system that has proven over time that you can rely on it.

In case of LTT, the choice should really be immediately cut down to just Fedora or Arch with Cachy or Endeavour as an options for “easier” Arch and Plasma as the desktop.

Just in the right moment when windows got so reliable and safe /s

My usual approach when trying Debian on a desktop or workstation: if I have to install a single package from testing or sid, fuck this and just use Arch or Fedora.

It boils down to D3D12 being slower on NVIDIA on Linux and it’s a known issue. There is some work being done on this by NVIDIA and VKD3D-Proton, but I wouldn’t hold my breath knowing how long things take to improve on NVIDIA side. If you get good deal on RDNA2 or newer, it works incredibly well today.

Won’t work for me, just like anything immutable, because I rely on one DKMS driver for my motherboard PWM sensors. But the project itself is pretty cool

Don’t distrohop too much, at one point there won’t be much more to explore with other distros other than wallpapers and themes

No, not really. If it’s set up right, it pretty much just works. I use it on my work computer and never mess around with anything, just use it and sync packages every month or so.

Honestly a distro called Nobara was a huge let down for me compared to Arch. It was effortless to install and came out with cool tweaks, but in just 6 months of usage it randomly broke like 4 times, every time I was supposed to check their discord server to get info on what broke and how to fix it. From Plasma not loading and opening crash report window indefinitel, to bootloop with update screen, to experimental drivers being shipped causing hard GPU crashes. And this is recommended for newbies? I’d rather give preconfigured Arch (like CachyOS) to newbie than this.

Fedora’s almost rolling though

Yeah, I’m normally an Arch guy, but gave Fedora with KDE a shot when I bought Framework. It’s pretty sweet, does everything I want and never bothers me

You could’ve just ask ;)

To fix Xbox controller connect it to an Xbox console and update its firmware.

To fix some videos not playing in games, switch from stock Proton to GE-Proton, you can install ProtonPlus or ProtonUpQt from your desktop store for easy Proton installs, newly installed Proton versions show up after Steam restart.

That’s an excellent question, very sharp thinking

Skurvysyně bobře

Webcam is just USB device, you can passthru that to the VM and it will work. Microphone is part of your onboard audio device, but it can probably be configured somehow to also expose microphone on an emulated audio device inside vm, but idk

Find jellyfin related file in /etc/apt/sources.list.d, edit it as root and try replacing „circle” with „bookworm”. After that apt update and retry. If it doesn’t work you can also try replacing it with „noble” but the you might also need to replace debian -> ubuntu, but that’s just my guess

What you really need is one of native DAWs you mentioned combined with Windows VST plugins run using Yabridge + WINE.

I remember running even complex VSTs along with realtime MIDI processing from e-drums with really good results and low latency.

1. Make sure your distro runs Pipewire and has pipewire-jack installed. Run your DAWs with JACK backend

2. You can check https://wiki.archlinux.org/title/Professional_audio for tips regarding audio performance. Don’t worry if you don’t use Arch-based distro. Most of it applies to any distro really

3. Install wine and yabridge follow setup instructions on how sync your plugins, which essentially takes specified locations with VST2/VST3 DLLs and creates .so equivalents (Linux dll format) under specified location that under the hood calls Wine, but makes it transparent. You add that location (with .so files) in your DAWs search paths and it should scan those plugins like if they were native.

Of course some compatibility issues are possible, but you should be able to run most stuff this way when it comes to plugins.

I’m pretty sure I used SyncThing from Flatpak at one point and it run great

That depends on which GPU you’re using as nvidia-open is for Turing and newer, but that makes no practical difference as it is and will always be out-of-tree.