I bought Coverzone Mini v5.0 USB Bluetooth Dongle 5.0 Bluetooth. It works great on Windows. It automatically starts when i reboot Windows. But it doesn't start automatically when using zorin os. I have to take it out and put it back in once. I have to turn on this bluetooth dongle. Because I have a Logitech K380 bluetooth keyboard. I am very upset that I can't use this keyboard when I switch to Zorin OS. Does anyone have any suggestions for a solution?
You could take a Look in /etc/bluetooth/main.conf and in this File in the last Row. There stands AutoEnable= and You could check if it is set to true or false. If it is false set it to true and test it.
Another Option would be to check the ''Additional Drivers'' Tab in Software & Updates where You could look if there is a Driver for the Stick.
AutoEnable= is "true". And I checked 'Additional Drivers'' and there is no driver for it 
Did You checked the Manufacturer's Website if this Bluetooth Dongle supports Linux?
And because of Your Keyboard: Did You tried to connect it directly to Your System or doesn't You System built-in Bluetooth?
I don't have a bluettoh connection on desktop. So i need to use this dongle. After some effort, I managed to achieve something. The computer recognized the Bluetooth keyboard and it worked. The computer does not automatically recognize the dongle that is plugged in when it is turned on. However, every time I turn on the computer, I have to remove the Bluetooth dongle and plug it back in. It is not very practical to use it like this. So I completely removed the Bluetooth dongle from the system. Of course, the keyboard too...
Does the Keyboard not offer to connect with Cable? So, you could at least use it.
Now i read a comment on a forum and decided to change my bluetooth dongle. I ordered tp-link ub500.
Brave A.I. search engine via Mojeek search engine comes back with:
"#
Linux Logitech K380 Support
The Logitech K380 Bluetooth keyboard is generally supported on Linux, but it may require some troubleshooting to get it working properly. Users have reported issues with pairing and connecting the keyboard, which can often be resolved by using the bluetoothctl command-line tool to manually pair the device.
To pair the keyboard, you can use the following steps:
- Ensure your keyboard is in pairing mode by pressing and holding the Easy-Switch button until the LED starts blinking.
- Open a terminal and run
bluetoothctl. - Use the
paircommand followed by the device address to initiate pairing.
For example, if the device address is 34:88:5D:EF:19:51 , you would run:
pair 34:88:5D:EF:19:51
After pairing, you may need to trust the device with the trust command:
trust 34:88:5D:EF:19:51
Some users have also found it helpful to reboot their system after pairing to ensure the keyboard works correctly.
Additionally, there are reports that the keyboard may not work out of the box on some Linux distributions, and users have had to manually map function keys using third-party software like k380-function-keys-conf .
Despite these challenges, many users have successfully used the Logitech K380 with Linux, including Ubuntu and Manjaro."
Is the keyboard RF or Bluetooth? Did it not come with it's own dongle? I have a Logitech Solar Powered keyboard on another machine and that came with it's own dongle. Think it is RF instead of Bluetooth.
What I saw to this, this could work. If not, you could try this Dongle with a newer Kernel. Keep us up-to-date here if it will work or not.
Now i m using K380 keyboard. When I turn the computer off and on, the dongle does not work automatically. I have to take it out and put it back in. In Windows the dongle works automatically and the keyboard connects it automatically. I am sure there is a trick to this in linux. I guess I am missing something.
Did you try the potential solution I posted above?
I can use the keyboard, but I have to unplug and plug back in the Bluetooth dongle every time I turn on the computer. And this is not ther main solution for me.
There seems to be quite a lot of issues online with this particular keyboard. I would suggest you try the manual method proposed by @swarfendor437 to see if that works. If it does, we can come up with shell script to run it automatically on boot and see if that achieves the intended result.
