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

Like what? The toilet water?

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.

Hello

You completely forgot to mention it runs Arch

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.

It really depends on how the distro you’re using is integrating them and while installing them is usually the easy part, working around certain quirks they come with can be a bit tedious in my experience.

The proprietary driver comes in binary form and is shipped with a small kernel module that handles loading the binary driver. The Linux kernel modules that aren’t part of Linux itself (which most drivers are) must be compiled for specific kernel and its binary can work only for that specific kernel and nothing else. This means that even if then driver is the same but kernel changes, the nvidia module must still be recompiled. There are two ways distros handle that: 1) by running the compilation process in the background while installing or updating the driver package 2) by shipping binary form of the nvidia module, in case where it’s distro that always recommends synchronization of all packages so that kernel and modules always match. Historically this caused way more problems than it sounds, compilation might have failed for certain kernels occasionally leaving users with broken video after simple system update. Overall though it mostly works fine, especially nowadays.

Another quirk is that the user-space part of the driver that exposes OpenGL and Vulkan interfaces for applications are also proprietary and closed source, and they must also match exactly with the kernel part of the driver. This creates another problem for sandboxed applications using for instance Flatpak. Applications in container won’t use the system-wide libraries, but rather ship their own - and that’s by design for good reasons. Flatpak will automatically detect NVIDIA and install matching driver just fine, but then after installing system upades, you must always update your flatpaks as well or the ones that use GPU in any way will simply fail to launch or fall back to software rendering making it extremely slow. This doesn’t happen for open source drivers, because Mesa can work with basically any kernel, so Mesa in Flatpak can be in completely different version than the one installed as system package. Moreover, I experienced problems with storage space because Flatpak wouldn’t automatically remove old NVIDIA drivers and after a year or so it was a chunky pile of NVIDIA drivers.

And even when it works, there can still be missing functionality or integration with the OS might not be perfect. Last time I used them I was limited to X11 with many quirks regarding multi monitor setup and vertical synchronization. Wayland is technically usable now on NVIDIA, but not perfected yet.

deleted by creator

Is that juice brand actually something available in Toronto area? That could tell us more if she’s telling the truth or not

Nice

What you’re referring to as Linux is actually Uutils/Linux…

It literally hasn’t changed even a tiny bit since I first saw it in 2006 :)

I currently use Strawberry - a well maintained fork of the old Amarok player before they redone the UI for KDE 4. It does what I care the most:

• Tree view collection with artist -> album grouping
• Files view
• Lyrics
• Tag editor
• Queue
• Last, but definitely not least - gapless playback

It’s Windows 95

The guy himself, a communist legend

Because it was. Only very late right before the project was killed they renamed it

If you come with expectations that you’ll just be fully catered no matter what your setup is and expect things to just work without ever trying to understand problems, you sure can be disappointed. Believe or not, most of the time those issues are out of control for Linux or the distros, as your hardware vendor made it to work on Windows and Windows only. Community is here to help you, but with your attitude it gets difficult no matter how much others try to help.

Pretty much because for some reason it’s broken mess in native games with SDL, and works nicely when using Proton, I noticed that too.

Hi there, having two dualsense and one ps4 controller, using them for ages on Linux and they mostly run great, but your issues doesn’t sound completely new either.

It’s very important on how you installed Steam and whether it’s native package or Flatpak. For Flatpak you might need special udev rules to allow the controller inside sandbox, usually can be installed using steam-devices package.

As others said, enable Playstation Controller support in Steam’s controller settings page.

Check if Steam overlay is functioning. In-game, press Shift+Tab and you should see the overlay and then you should be able to get to controller settings. Try out both with Steam Input enabled and disabled - by default I guess it depends on the game, but mostly enabling it will make it work for games that have issues picking up ds natively.

Test your controllers using something like jstest-gtk. Perhaps there is something else connected that acts as player 1 controller.

Don’t forget that at this point X11 doesn’t have feature parity with Wayland more than the other way around. Mixed DPIs, refresh rates, multi-display VRR, virtual screen resolutions, nested compositing, direct scan-out, GPU hot plugging, DRM leasing, HDR are all exclusive or at least better on Wayland.