mirror of
https://github.com/Qubes-Community/Contents.git
synced 2025-04-14 12:43:19 -04:00
Merge pull request #219 from aronowski/bluetooth-graphical
Graphical Bluetooth management with Blueman
This commit is contained in:
commit
d9356cfb0c
@ -22,6 +22,7 @@
|
||||
-  [Newer Pihole qube, with cloudflared or NextDNS servers](https://github.com/92VV3M42d3v8/PiHole/blob/master/PiHole%20Cloudflared)
|
||||
-  [qubes-dns](https://github.com/3hhh/qubes-dns/)
|
||||
- [Using multiple languages in dom0](localization/multi-language-support-dom0.md)
|
||||
- [How to manage Bluetooth graphically](configuration/bluetooth.md)
|
||||
|
||||
`coreboot`
|
||||
- [install coreboot on a Thinkpad x230](coreboot/x230.md)
|
||||
|
17
docs/configuration/bluetooth.md
Normal file
17
docs/configuration/bluetooth.md
Normal file
@ -0,0 +1,17 @@
|
||||
# Graphical Bluetooth configuration
|
||||
|
||||
Install the package `blueman` in the template of your `sys-usb` qube.
|
||||
|
||||
```
|
||||
sudo dnf install -y blueman
|
||||
```
|
||||
|
||||
Then restart the qube. From now on you should have a tray icon and be ready to connect to bluetooth devices graphically, like so:
|
||||
|
||||

|
||||
|
||||
In the picture above I had a sys-net combined to use USB devices too. The procedure stays the same.
|
||||
|
||||
## AudioVM
|
||||
|
||||
For the most secure scenario, one should be running an AudioVM rather than rely on having PulseAudio in dom0. The creation of such a VM is beyond the scope of this guide.
|
Loading…
x
Reference in New Issue
Block a user