bluez stacks are installed, with no blueman to manage.
Once installed, the bluetooth service needs to be both enabled and started; a reboot will not do (in my case).
For the curious, that is: systemctl enable --now bluetooth (the --now flag starts it).
The bluetooth icon in the panel is hideous.
Not really sure what the question is. Or is this a bug report?
I guess not everyone uses/has bluetooth hardware on their devices, so it makes sense to not have anything bluetooth related preinstalled. I remember I needed to install blueman on Antergos also.
It’s not likely installed on Arch either. Where do we draw the line on what is going to come preinstalled? Can’t just keep adding things because it’s not there and someone needs it. I think it’s better to lay this out in the wiki under bluetooth.
I will say that I think it is way more important to add the things needed so that users have no difficulties booting on the live ISO and installing Endeavour. That is priority in order to have good feedback and good reputation.
hello, all is said
Common hardware, conforming to the majority, has bluetooth integration.
The majority of users of every distribution, linux or otherwise, “need it”.
Bluetooth support is needed. Know what’s not “technically” needed for Arch to boot? A DE, WM, WIFI drivers, touchpad/mouse support, tlp, power manager, an internet browser, media player, etc. Yet, they are present in Endeavour OS! Know why? Because Endeavour OS is NOT Arch Linux, it a distribution based on it!
Want bare minimum? Leave EOS and go be an Arch purist somewhere else. Users want distributions that are reliable. Having built-in support for a most basic hardware meets the needs of average users.
Here’s a little detail you overlooked.
warning: bluez-5.50-6 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) bluez-5.50-6
Total Installed Size: 1.85 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
Support is present, with no front-end. According to your way of thinking, EOS ought to be rid of “Network Manager”. After all, one can always configure a network connection by terminal, same way you would a bluetooth device. Easy right?
Don’t waste any more of my time, please.
A bug. As in, a front-end for preinstalled bluetooth stacks (bluez) is missing. bluez 5.50-6 as of now.
I don’t remember ever needing to install front-ends to manage my network connections.
We appreciate your feedback and we’re going to look into it.
The next thing I’m going to say is meant in general.
We’re happy when the community is giving us feedback, but when doing so, just propose the idea and we’re happy to look into it. Keep the conversation civil towards your fellow community members, like you, everyone else over here is giving advice in their spare time, nobody here is a trained and paid helpdesk employee, so treat other people with the same respect you would like to be treated.
As for us, the devs, we’re not that different in that respect. Like you, we’re running this distro in our own spare time, next to our daily routine. There’s no big corporation funding us, so this means that slip-ups and imperfections are present in the entire project. Again you can point us in a direction, but don’t demand things from us.
We are very open to suggestions from everyone, but we kindly ask to avoid words like: the distro should… or EOS ought to do…
We’ve released two stable releases without demanding anything from you, keep that in mind before coming across too strong in asking a feature for the distro, that almost leans towards demanding.
We’re doing this for the love and fun for the Linux community and we invest a lot of time in that. The words used as above can diminish that enthusiasm.
Just keep it civil that’s all we ask from you and in return, we are striving to give you a smooth-rolling distro.
It is infuriating when fellow users derive ball-park statements from plain feedback. It’s all it was, some feedback on partial bluetooth support. A different way to phrase it is: bluez is present without a “manager”. Add some more details and you have my post.
I’m aftraid the context was lost in translation; no demands were made. Quote if you will, but please reconsider.
@Bryanpwo the user reached conclusions too fast without due diligence. Elaborated my discontent thoroughly, free from personal attacks I’d argue.
I was referring to the way you’ve answered back to the other members. using " Don’t waste any more of my time, please" and highlighting words in your answer, certainly come across as demanding and a certain level of disrespect towards your fellow members.
I’ve highlighted words in my answer as a reaction on your contribution till then.
I’m not saying everyone has to agree with each other, but just read your post back before posting (and this is addressed to everyone.)
Your suggestion has reached us and we’re going to look into it, thank you for pointing us into that direction and now it’s clear that it wasn’t your intention to demand this issue.
bluetoothctl help
https://wiki.archlinux.org/index.php/Bluetooth#Console
sudo pacman -S bluez bluez-utils
sudo systemctl start bluetooth // start the service till next reboot
sudo systemctl enable bluetooth // enable bluetooth to start automatic on every boot
If you want a GUI to handle BT:
install one of these:
blueberry
blueman
both will integrate into XFCE4 setting GUI also.
It is personal choice if you need/want to run a graphical tool for it, but it is not needed.
XFCE is not having a BT-GUI tool included.
We will not enable bluetooth by default, as it is a risk on security and wrong for powersavings.
See here how to connect to BT-Headset:
https://wiki.archlinux.org/index.php/Bluetooth_headset
They are many ways to automate connections.
Well KDE/Gnome have bluetooth out the box.
The user has to enable bluetooth to use it.
That makes it a sane choice security is the utmost importance.
As does KDE Plasma install on Arch, if I remember correctly.
Yep they like Gnome its part off the install you the user decides on to enable bluetooth.
I’ve had the same little issue today installing EOS with Cinnamon. Only blueberry was installed. Maybe it is part of the Cinnamon-packages. It set me on the wrong foot. After a couple of moments I realized bluez and bluez-utils where not installed. After installing those packages (same commands as above in the post from joekamprad) I could use my BT-headset.
Quick look at the wiki is all you need
I’ll keep that in mind the next time I install EOS. Thanks!
I enjoy that the distro comes as bare-bones as possible.
sudo systemctl enable bluetooth (permanent)
sudo systemctl start bluetooth (only active until next reboot)
Also, don’t forget you have bluetoothctl help as a command line utility.
The wiki lists the following graphical GUIS to configure and manage bluetooth:
blueberry (gtk) [recommended for XFCE]
bluedevil (qt)
blueman (gtk)
Thank you! I gave up trying to get bluetooth to work until I saw this …and it worked. 
What security threat is there if bluetooth is supported by default ?