So not really sure what’s going on but when using KDE I cannot mount my android phone or connect an android controller, however if I use Wayland they work
I’m not sure what to make of this, but I assume you wanted to say KDE does what it’s supposed if you select the Wayland session. This would lead to my follow-up question: Why not just use it?
Wayland has been the preferred session for KDE since late 5.X
I use feren os, before logging in I can select Plasma(x11), which is the default, ubuntu, or I ubuntu on Wayland
Mouse recorders don’t work on Wayland
Color pickers on Wayland are janky af
Screenshot capture on Wayland is weird, if you copy an image to clipboard with Spectacle or Flameshot, it leaves the clipboard when the Screenshot captured notification disappears
My TV doesn’t detect input via HDMI on Wayland
2-4 I have never had any problems with, file bug reports if you do I guess
Pro Tip: don’t make sweeping generalizations like “KDE Breaks Bluetooth” and then claim its happening while including little to no detail.
I’ve been running KDE for over a decade without any such problems. KDE absolutely does not break bluetooth or removable devices.
Now perhaps the way you have set up and configured KDE isn’t working right and causing problems with bluetooth and removable devices. I’d believe that but hard to know what hapoened without any details.
it doesn’t do none of those things. also, you should include less details, it’s fun guessing what your software stack is, how you installed it, and the term “if I use Wayland” is way too precise. likewise, that sentence of yours is enormously protracted, you should consider shortening it.seriously, are you for real?edit: hey, if you want people to help you, provide details as to your os, software, hardware, and maybe spend a bit of time describing your issue in detail as well as stuff you’ve tried. cheers!
Why so passive aggressive? 😅 Probably OP is new to Linux and doesn’t know what’s relevant information and what isn’t.
you’re right. edited.
Bluetooth was an issue also in gnome and in sway, it has been fixed now on Arch. Somewhere read about kernel issue. Can’t confirm. Chech your distro forum.
