Bluetooth can be managed with systemctl
and bluetoothctl
.
https://www.makeuseof.com/manage-bluetooth-linux-with-bluetoothctl/
In my experience I find just running bluetoothctl
to enter the interactive mode easiest. You can enter commands without prepending bluetoothctl
. You can use help
at any stage. So you want to use systemctl
to make sure Bluetooth is running, then enter bluetoothctl
. Make sure the device is discoverable and pairing is set to on. Start your [headphones/whatever] in pairing mode and run devices
. When you see the device run pair <numbers/address>
. Only use the numbers. You may have to go into settings and select the device in the sound applet.
My situation doesn't require a logout timer, but if I'm walking away from the PC I just use the shortcut Super + ESC. Alternatively, there's many ways you can create a basic Bash script that when invoked times down to a systemctl suspend
command. Or possibly the hybrid-sleep option could do what you want. See systemctl -h
for possibilities.
Blanking the login screen is something that will be implemented shortly. Maybe I'll work on a script for that because it annoys me too. Fortunately I rarely use it. I'll repost if I do this.
I really don't think the two years people are saying in this thread is realistic. The hard work and core is written. What is there is stable. I think they will get this completed much sooner. They do have a hardware business to support after all.
I'm using it every day now. I have one machine installed with the 24.04 ISO and it's working fine. There's some TODO items to come which I understand will be added by Alpha2. With a little command line knowledge COSMIC is perfectly usable now and is stable.
For secure private transfer use the Warp flatpak in Linux and Worrmhole William in Android.
I've been using COSMIC for a while now without problems, and the store is great. Easy to theme and the apps are pretty good. I haven't checked it lately, but I hope the greeter improves soon.
The amount of times I've seen people request help because Pi-hole was not blocking/functioning properly, well a hosts file just ensures nothing leaves that you want blocked. Besides, you may have different machines set up to be strict or permissive depending on their use case.
Absolutely. These lists are created by server admins who collect what the firewall rejects, much like you see with the Pi-hole. They'll automatically block some ads and many threats too. Another tip if you're using Librewolf, Mullvad browser or Firefox with uBlock, enable more of the filter lists.
That's a lot of progress! Worth the read.
Pi-hole is OK, but for good measure it's easy to set up a "hosts" file that blocks all that stuff locally. You can use your findings from Pi-hole. On Linux you just pop your entries in /etc/hosts
, or other OS equivalent. Here are some curated lists.
For Mozilla telemetry - https://github.com/MrRawes/firefox-hosts/blob/firefox-hosts/hosts
Massive list for everything - https://github.com/StevenBlack/hosts
Posteo has been stable, professional and functional for many years. Tuta is another good choice.