I can't fucking do this anymore. Maybe Linux was a mistake. Almost a year on Ubuntu and it's still kicking my ass. This past month I lost access to my bluetooth keyboard by un-pairing it once, to troubleshoot something. Now I can't fucking get it to pair again and I've spent countless hours trying. I tried compiling a newer version of bluez like several articles said and it's not fucking installing. There are no error messages when I make and install the source, yet for some reason bluez is not showing up in my apt list or systemctl services. That is fucking bullshit
Then I decided to try running the Windows-only executable for my bluetooth keyboard's software, but wouldn't you know, Wine's been broken for almost a month. It doesn't matter what I do, switch to the stable branch or not, there appears to be some kind of display driver issue with mesa, but who knows! That's the thing with Linux. We can never be completely sure what the problem is! All I know is that nothing will open with Wine, and clearing the default prefix doesn't help. I thought only Arch was supposed to have these bullshit problems? I'm on Ubuntu. Thought it was supposed to be stable.
I'm not even going to go into how I tried installing kde-plasma-desktop and then the fucking sddm almost bricked my system, which I only installed because the fucking articles recommended me to. Currently drinking because this has drove me to alcoholism
>another filtered wintoddler bites the dust
> you have to be not “filtered” to use the OS (tool)
That’s why loonix will never be a popular operating system, and you will never be a woman.
>I thought only Arch was supposed to have these bullshit problems?
you dumb nagger. while you were crying over your gay ass wireless keyboard i was comfortably using my arch machine. maybe read a fucking manual before you start trying to use wine for device drivers.
>That's the thing with Linux. We can never be completely sure what the problem is!
i find linux much easier to find out what problems are
i don't know why you'd think wine would help with bluetooth drivers, the only time i'm aware of that you ever have been able to use windows drivers in linux was ndis network (mainly wifi) drivers with a special wrapper, but that hasn't been necessary for around 15 years, wine isn't generally designed for drivers, since it's a userspace windows emulator, it doesn't do kernel stuff outside the bare minimum glue
>using israelitetooth
>ever
i don't even trust it on windows
This. Hardwire everything and use an external audio preamp with a 1/4th" jack and xlr in.
TILt you can tap a fibre optic cable by literally bending the cable and setting up a detector to grab the escaping light.
werks on my machine
Words words words
Go back to OSX
Linux users only do that after they get aids and have to retire from the lifestyle. Then they go yep it's actually unix haha over and over again as they wither away with their fat but sadly supportive boyfriend. Many such cases! Sad!
>bluetooth on linux
>audio on linux
it was over before it started
Shouldve gone with Debian if you wanted stability.
>using Arch
There's a distro for windows refugees: Nobara OS.
>bluetooth keyboard
i hope someone strangles you with those bluetooth cables, idiot
you dont deserve to have a working system
Jesus Christ, dude, just install Linux Mint.
> wintoddler installs the worst distro
> wintoddler starts "following articles" and probably starts copy pasting random commands into their terminal with root privileges.
> wintoddler probably is 1 step away from bricking their system because of their own incompetence.
Look.
Linux allows you to fuck up your system.
It lets you change it's very core components.
You can fuck it up. If you don't know what you're doing... Stop first and figure out what the fuck you're doing.
The secret sauce that nobody tells you is that it really helps just jumping straight into the deep end. Just install a minimal distro and build it from the ground up. You will learn so much. I recommend Arch linux.
Follow MentalOutlaw and Luke Smith's youtube channels.
freetards before the switch:
>it's easy to use
>just copy and past those commands
>there is a guide for that and it works
freetards after the switch
(this dude is also a cock sucker)
correct that you should dive straight in but follow the fucking documentation not videos that cant be updated to reflect changes.
I've had a lot of trouble with bluetooth on linux, here's my general fix.
> bluetoothctl
> devices
> remove <mac-address of troublesome device>
> scan on
(Start pairing your device)
once it pops up run
> connect <mac-address>
Doing it through the cl tends to work a lot better than whatever half-baked bluetooth program ubuntu might have installed.
>bluetooth on linux
Pfft, you fucking people. What are you going to expect next, fucking thumbnails in the file picker?
Temper your damn expectations here. Baby steps, baby steps.
Here's a list of things you should expect to not work if you use Linux
- Bluetooth
- Audio
- WiFi
- nvidia
- Any hardware marketed towards gamers
- Any software with non-terminal graphics
If you get this stuff to work, great! But it's not the natural state of things in the Linux ecosystem and Linux will try its best to return to its natural state.
kek, add printers to list, my last arch install bricked my cute uwu 50$ epson printer, never had a problem in 10 years on windoze
that may have been more accurate 20 years ago
Smartest wojack poster.