Audio is fixed by just using pipewire.
Displays is fixed by using Wayland (sway).
Bluetooth is indeed an unsolved problem. I suppose the skilled hacker types have just declared the whole protocol as broken and use wires.
Displays is fixed by using Wayland (sway).
Bluetooth is indeed an unsolved problem. I suppose the skilled hacker types have just declared the whole protocol as broken and use wires.
My experience with Pipewire has definitely been excellent.
> Displays is fixed by using Wayland (sway).
I still have some tooling that requires X11 -- but whenever I've used Wayland I feel like there is still a lot that relies on X11. For me, Rofi is one of those tools that I just haven't been able to totally replace in Wayland (even with the Wayland forks of Rofi). Some other day-to-day examples are Zoom[1] and Nvidia graphics cards[2]. While I am aware that these are third parties lagging behind Wayland support and not really an issue with Wayland itself, it still demonstrates how everything is not magically "just fixed" simply because you are on Wayland.
[1] https://support.zoom.us/hc/en-us/articles/6634039380877-Shar...
[2] https://forums.developer.nvidia.com/t/wayland-information-fo...
Do I read parent as saying that these things are best managed through GUI widgets attached to the desktop environment
100% you are reading my original comment correctly. An example I ran into recently: I start up bluetoothctl, I power on the adapter, start scanning for Blueooth devices and am spammed by a bluetooth device nearby to the point where I can't see the one I am trying to pair to (even after turning off scanning). In contrast, blueman-applet or GNOME's control-center neatly organizes each unique Bluetooth device as individual icons and makes it easy to see each of those. Lots of little papercuts like that can make it frustrating when you're just trying to get work done.
This is also true things like displays -- sure I could take 20 minutes write a script to rearrange my displays the way I prefer -- or I could just open GNOME's control center and take two minutes using the display setting.
There are lots of little things like this that can get in the way when you just need to get something done.
And this is totally subjective to my experience, my opinion and what I currently value so please don't take this like I am saying everyone should prioritize things the way I do. For those more comfortable in i3 or something else -- great! :)
What would cause friction is if the display plain didn't work, or had bad aspect ratio or fonts. Wayland (in combination with kernel graphics probably) seems to have fixed those problems.
exec_always --no-startup-id blueman-applet
exec_always --no-startup-id nm-applet --indicator
Though note I basically only use Windows as a fat driver layer unless I'm playing games (Wintendo!)
> unless I'm playing games
This is one area I've not been able to completely ditch Windows. Valve is doing some great work to get Windows games running on Linux in Steam but I find myself playing a bunch of games that are not in Steam with an anti-cheat engine that sucks in Proton. I hope more external game launchers/stores and anti cheat engines are motivated by Valve to implement Linux (or emulated) support.
I totally cannot be arsed being a desktop admin for either.
So I use WSL2+Xsrv to give me my -client- environment on windows and then use that to ssh into servers to actually do stuff.
Meanwhile, windows acts as a fat driver layer that provides firefox and my X11 setup and easy access to games.
I am in no way recommending this. But it works for me.