Bluetooth 5.4 USB stick connected on a desktop computer with OpenSUSE 15.5 with KDE not working

English Hardware
1

I’m trying to use a Bluetooth 5.4 USB stick connected to my desktop computer that has OpenSUSE 15.5 with KDE.
Unfortunately I am not able to diagnose the problem due to lack of knowledge, but I have run several commands found on the Internet to find information on the state of the system and I am sharing them with you in the hope of being able to resolve it.

The device is visible with lsusb.

~> lsusb
Bus 004 Device 002: ID 33fa:0010  USB2.0-BT

and it appears to be successfully interrogated

~> lsusb -v -d 33fa:0010

Bus 004 Device 002: ID 33fa:0010  USB2.0-BT
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x33fa 
  idProduct          0x0010 
  bcdDevice           88.91
  iManufacturer           0 
  iProduct                2 USB2.0-BT
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x00b1
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0000  1x 0 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0000  1x 0 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0009  1x 9 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0009  1x 9 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       2
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0011  1x 17 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0011  1x 17 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       3
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0019  1x 25 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0019  1x 25 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       4
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0021  1x 33 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0021  1x 33 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       5
      bNumEndpoints           2
      bInterfaceClass       224 Wireless
      bInterfaceSubClass      1 Radio Frequency
      bInterfaceProtocol      1 Bluetooth
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0031  1x 49 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0031  1x 49 bytes
        bInterval               1

This result if I query the hardware

~> sudo hwinfo --bluetooth
[sudo] password di root: 
03: USB 00.1: 11500 Bluetooth Device                            
  [Created at usb.122]
  Unique ID: sjcF.vycpFRHqAB1
  Parent ID: zPk0.lC9gMZu39RD
  SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:05:05.1/usb4/4-1/4-1:1.1
  SysFS BusID: 4-1:1.1
  Hardware Class: bluetooth
  Model: "USB2.0-BT"
  Hotplug: USB
  Vendor: usb 0x33fa 
  Device: usb 0x0010 "USB2.0-BT"
  Revision: "88.91"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v33FAp0010d8891dcE0dsc01dp01icE0isc01ip01in01"
  Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #11 (Hub)

The device does not appear to have active software or hardware locks

~> sudo rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked

a bluetooth module is loaded, but I have no idea if it’s the correct one

~> lsmod | grep bluetooth
bluetooth             901120  15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
crc16                  16384  2 bluetooth,ext4
rfkill                 28672  8 bluetooth,cfg80211

I see the Bluetooth service active, but there seems to be two warnings, I don’t know if these can hinder correct functioning

~> sudo systemctl status bluetooth.service
[sudo] password di root: 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2024-04-06 07:07:09 CEST; 3h 23min ago
       Docs: man:bluetoothd(8)
   Main PID: 958 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
     CGroup: /system.slice/bluetooth.service
             └─ 958 /usr/lib/bluetooth/bluetoothd

apr 06 07:07:05 rene-alien systemd[1]: Starting Bluetooth service...
apr 06 07:07:05 rene-alien (uetoothd)[958]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
apr 06 07:07:06 rene-alien bluetoothd[958]: Bluetooth daemon 5.65
apr 06 07:07:09 rene-alien systemd[1]: Started Bluetooth service.
apr 06 07:07:09 rene-alien bluetoothd[958]: Starting SDP server
apr 06 07:07:09 rene-alien bluetoothd[958]: Bluetooth management interface 1.22 initialized
apr 06 07:08:33 rene-alien bluetoothd[958]: src/profile.c:register_profile() :1.70 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

I tried to stop (stop) and restart (start) the service, as well as restart it (restart), but no change in state occurred.
Querying the system logs I realized that they are exactly the part that is attached to the result of the systemctl command.

~> journalctl -u bluetooth.service
apr 06 07:07:05 rene-alien systemd[1]: Starting Bluetooth service...
apr 06 07:07:05 rene-alien (uetoothd)[958]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
apr 06 07:07:06 rene-alien bluetoothd[958]: Bluetooth daemon 5.65
apr 06 07:07:09 rene-alien systemd[1]: Started Bluetooth service.
apr 06 07:07:09 rene-alien bluetoothd[958]: Starting SDP server
apr 06 07:07:09 rene-alien bluetoothd[958]: Bluetooth management interface 1.22 initialized
apr 06 07:08:33 rene-alien bluetoothd[958]: src/profile.c:register_profile() :1.70 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

The bluetoothctl system does not seem to see the device.

~> bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available
[bluetooth]#

In the graphical control panel of the “System settings” on the Bluetooth page, the page appears to me with a central message that says “Bluetooth is deactivated” and immediately below there is an “Activate” button, this button, if pressed, appears do absolutely nothing, everything remains as it is.
In the system tray if I click on the Bluetooth icon the curtain that comes out tells me “No devices found”, but I imagine that it should be activated first and that the “devices” it means should be the peripherals to which you can connect.
Obviously, not knowing the way to resolve it, I don’t know if among this information there is precisely the information that explains the malfunction, unfortunately I am not able to understand.
This is all, for now, I have managed to find to query to try to understand what is not working, but I still have not been able to understand what is not working.
I hope some of you can help me solve it.
Thanks in advance

2

I am continuing to experiment and look for information.
I found this command in a forum, which should be used to activate the device manually.
sudo hciconfig hci0 up
but when I used it a file not found error came back to me

~> sudo hciconfig hci0 up
[sudo] password di root: 
sudo: hciconfig: comando non trovato

I tried searching for this command

~> whereis hciconfig
hciconfig:

but nothing was found.

So I tried to better understand what it was and it seems to be a script, but it also seems to be present in my system

~> ls -l /usr/share/bash-completion/completions/hci*
lrwxrwxrwx 1 root root    7 15 dic  2022 /usr/share/bash-completion/completions/hciattach -> hcitool
lrwxrwxrwx 1 root root    7 15 dic  2022 /usr/share/bash-completion/completions/hciconfig -> hcitool
-rw-r--r-- 1 root root 9756 15 dic  2022 /usr/share/bash-completion/completions/hcitool

I thought, seeing as I know little about it, that if it exists in my system but isn’t found, there must certainly be a reason.
I then tried to search if there was any package that Yast could install that contained it and I found the bluez-deprecated package that contains it but, as the name says, it seems no longer used and replaced by something in the bluez package, if I understood correctly .
I installed it anyway and tried the command again which, this time, worked but generated an error.

~> sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

For now that’s all I’ve further investigated.
Since I don’t understand anything about it, I don’t know if anything has changed, I don’t think that package installed was needed, and I hope it doesn’t cause any problems having it installed, but I hope it will simply be ignored.
I haven’t rebooted yet, you never know, maybe even if it’s obsolete if found at startup it could do something, possibly if something changes I’ll update the information here.
That’s all for now, I’ll keep experimenting.

3

Could you try reinstalling bluetooth stack:

sudo zypper in --force bluez bluez-auto-enable-devices
systemctl reboot
bluetoothctl list
bluetoothctl devices
bluetoothctl show
4

@renedrive what about (as root user);

bluetoothctl power on
bluetoothctl discoverable on
5

I believe I forced the reinstallation using Yast Software and using the “Update Unconditional” feature.
I did it because, reading advice in forums and online guides, there was talk of modifying the Bluetooth system configuration file by modifying the file
/etc/bluetooth/main.conf
but when I looked for it the file didn’t exist.
It seemed strange to me that the file didn’t exist, it seemed like a necessary file.
I had created it and inserted only the 3 lines that were recommended to be modified but it didn’t work because the file seems organized in well-defined sections that must exist, and therefore generated an error from the Bluetooth system.
I then thought that attempting a force reinstallation might fix it and create the correct file.
Even after forcing the “Update unconditionally” command, done with Yast, the file was not there.
So I proceeded to search for a similar file on the Internet, found it, I replaced it in place of my file with only 3 lines, and at this point the Bluetooth system started working again without those errors, and as I reported.
Obviously in this case I wasn’t sure that the file I was looking for was perfectly compatible, but it seemed to work.

Now I tried the zypper command you recommended.
I immediately noticed several things during the update.

  1. it asked me to install a newer version of
    bluez-obexd-5.71 (from vendor obs://build.opensuse.org/home:plater)
    instead of the existing one
    bluez-obexd-5.65 (from vendor SUSE LLC https://www.suse.com/)
  2. obviously also installed other updates from the same repository
  bluez                      SUSE LLC <https://www.suse.com/> -> obs://build.opensuse.org/home:plater
  bluez-auto-enable-devices  SUSE LLC <https://www.suse.com/> -> obs://build.opensuse.org/home:plater
  bluez-obexd                SUSE LLC <https://www.suse.com/> -> obs://build.opensuse.org/home:plater
  1. it reported a conflict to me and I let it continue
File /usr/bin/btmgmt
  from install of
     bluez-5.71-lp155.3.3.x86_64 (home:plater)
  conflicts with file from package
     bluez-test-5.65-150500.3.11.1.x86_64 (@System)
  1. but above all, during the update, I noticed the file writing message
(1/4) Installazione di: libreadline8-8.2.10-lp155.9.1.x86_64 ..................................................[fine]
warning: /etc/bluetooth/main.conf created as /etc/bluetooth/main.conf.rpmnew
(2/4) Installazione di: bluez-auto-enable-devices-5.71-lp155.3.3.noarch .......................................[fine]
(3/4) Installazione di: bluez-5.71-lp155.3.3.x86_64 ...........................................................[fine]
(4/4) Installazione di: bluez-obexd-5.71-lp155.3.3.x86_64 .....................................................[fine]
Running post-transaction scripts ..............................................................................[fine]

where he noticed that the file /etc/bluetooth/main.conf and in order not to replace it, I think, he wrote the file /etc/bluetooth/main.conf.rpmnew.
Since the previous file was the one I had “invented” myself, I replaced it with the new one created by the update.

This gave me hope.
I proceeded to reboot, as you suggested
systemctl reboot
but unfortunately the result…

~> bluetoothctl list
~> bluetoothctl devices
No default controller available
~> bluetoothctl show
No default controller available

Thank you very much anyway because the situation could certainly be improved compared to before, talking about the software and coherence.

6

I hadn’t thought about doing the test you recommend with the root user.
Unfortunately, however, the result is…

~> su
Password: 
# bluetoothctl power on
No default controller available
# bluetoothctl discoverable on
No default controller available
7

Now, after reinstalling the bluez system I noticed this…

~> sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2024-04-09 10:27:49 CEST; 19min ago
       Docs: man:bluetoothd(8)
   Main PID: 1023 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
     CGroup: /system.slice/bluetooth.service
             └─ 1023 /usr/lib/bluetooth/bluetoothd

apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support csip plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support micp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support vcp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support mcp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support bass plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support bap plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support admin plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: Bluetooth management interface 1.22 initialized
apr 09 10:29:11 rene-alien bluetoothd[1023]: src/profile.c:register_profile() :1.69 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

and, of course, this …

~> journalctl -u bluetooth.service
apr 09 10:27:46 rene-alien systemd[1]: Starting Bluetooth service...
apr 09 10:27:46 rene-alien (uetoothd)[1023]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
apr 09 10:27:47 rene-alien bluetoothd[1023]: Bluetooth daemon 5.71
apr 09 10:27:49 rene-alien systemd[1]: Started Bluetooth service.
apr 09 10:27:49 rene-alien bluetoothd[1023]: Starting SDP server
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support csip plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support micp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support vcp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support mcp plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support bass plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support bap plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: src/plugin.c:plugin_init() System does not support admin plugin
apr 09 10:27:49 rene-alien bluetoothd[1023]: Bluetooth management interface 1.22 initialized
apr 09 10:29:11 rene-alien bluetoothd[1023]: src/profile.c:register_profile() :1.69 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

I will now try to investigate these reports.
Then I’ll let you know if I discovered anything.

I also noticed that the new conf file has everything commented out, no active options, nothing.
I have now tried to uncomment and modify the 3 specific entries as recommended on the Internet.

AutoEnable=true
ReconnectAttempts = 7
FastConnectable=true

So I restarted the system, but nothing changed, still the same situation as response to commands.

I don’t know, I’ll keep investigating, and I’ll let you know.
Thanks for your help so far, I’m learning something.

8

I already have an update.
I’ve read that some of the warnings when starting the Bluetooth service are normal.
It seems that they are inactive options of the Bluetooth system because they are not yet stable but which can be activated by activating the “experimental” system, deactivated by default, precisely because the software parts could be unstable.
Since I tried everything I also tried activating the “experimental” option.
Indeed, as one would expect, the warnings disappeared.
Now the situation has returned…

~> sudo systemctl status bluetooth.service
[sudo] password di root: 
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2024-04-09 11:26:36 CEST; 6min ago
       Docs: man:bluetoothd(8)
   Main PID: 4586 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4915)
     CGroup: /system.slice/bluetooth.service
             └─ 4586 /usr/lib/bluetooth/bluetoothd

apr 09 11:26:35 rene-alien systemd[1]: Starting Bluetooth service...
apr 09 11:26:35 rene-alien (uetoothd)[4586]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
apr 09 11:26:36 rene-alien bluetoothd[4586]: Bluetooth daemon 5.71
apr 09 11:26:36 rene-alien bluetoothd[4586]: Starting SDP server
apr 09 11:26:36 rene-alien systemd[1]: Started Bluetooth service.
apr 09 11:26:36 rene-alien bluetoothd[4586]: Bluetooth management interface 1.22 initialized
apr 09 11:26:36 rene-alien bluetoothd[4586]: src/profile.c:register_profile() :1.49 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

and…

~> journalctl -u bluetooth.service
apr 09 11:26:35 rene-alien bluetoothd[1034]: Terminating
apr 09 11:26:35 rene-alien systemd[1]: Stopping Bluetooth service...
apr 09 11:26:35 rene-alien bluetoothd[1034]: Stopping SDP server
apr 09 11:26:35 rene-alien bluetoothd[1034]: Exit
apr 09 11:26:35 rene-alien systemd[1]: bluetooth.service: Deactivated successfully.
apr 09 11:26:35 rene-alien systemd[1]: Stopped Bluetooth service.
apr 09 11:26:35 rene-alien systemd[1]: Starting Bluetooth service...
apr 09 11:26:35 rene-alien (uetoothd)[4586]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
apr 09 11:26:36 rene-alien bluetoothd[4586]: Bluetooth daemon 5.71
apr 09 11:26:36 rene-alien bluetoothd[4586]: Starting SDP server
apr 09 11:26:36 rene-alien systemd[1]: Started Bluetooth service.
apr 09 11:26:36 rene-alien bluetoothd[4586]: Bluetooth management interface 1.22 initialized
apr 09 11:26:36 rene-alien bluetoothd[4586]: src/profile.c:register_profile() :1.49 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered

So +/- the situation is unchanged, it still doesn’t work.
I will continue to study the situation.

What I can’t understand is whether we can know if perhaps the problem is incompatibility.
How can I know if the specific flash drive is compatible?
Or are they all compatible anyway?
I don’t see any messages suggesting incompatibility.
And obviously the stick works, for example if I try it in a Windows environment.
It’s bad not being able to understand what’s wrong, my ignorance on the subject annoys me, it would be nice to understand better, but I’ll try!! :wink:
Until next time … …

9

Quite concerning that the packages are being installed from OBS home repo, makes sense that would cause the conflict you experienced later.
Could you provide the output of:

zypper lr -dP

Some repo cleanup may be in order :microscope:

10

It sounds like a hardware issue with either BT dongle or USB port. Try different USB port. If it still does not work - reboot with the dongle connected and provide full output of

journalctl -b --no-pager --full

upload to the https://paste.opensuse.org/

11

I actually noticed that during the forced update with zypper it asked me to change supplier.
Since I doubted that the hardware is very recent and that the software might be “not yet” compatible, I let it go because it installed a more up-to-date version.
It should be noted, however, that the version installed before was from the OpenSUSE server and therefore not OBS, and that was the version on which I made all my reports and requests for help.
That is to say that it was the version from the OpenSUSE repository that didn’t work, but now, with the OBS version it behaves exactly the same way.
I therefore don’t believe that with the same behavior, i.e. not working, the source from which it was installed changes anything.

I have to say that I purposely do everything from Yast, precisely because I noticed that zypper seems to ignore the priority and automatic update settings for the repositories.
I’ll explain better.
My installation is highly multimedia, this is because I deal with, both for work and for passion, the creation, modification and processing of multimedia files, audio, music, video, photos and more (ah, anyway, also some WEB stuff and some games… obviously).
For this reason I have installed a lot of software and much of this does not exist in the official repositories, so I have to use many different repositories, more or less reliable.
This often created problems for me in the past.
Not knowing either the priority system or the auto update option for the repositories, I often found myself with unstable updates that ruined the balance of the system.
However, I have studied a little the repository priority system and the option to disable automatic repository updating.
In this way I always have control over what is installed and the automatic updates come to me only and exclusively from official repositories.
In fact, I use a priority lower than 99, more precisely 97, for all the trusted repositories, and I raise all the others to 101 or 104, in this way updates hardly reach me from unofficial repositories, but since sometimes it wasn’t enough over time I also disabled the automatic update option for all repositories with priority higher than 99, in fact it is also disabled for some with priority 97.
In this way, from Yast I can have an easy view of what I am installing and from where, and the automatic updates come to me only and only from the few repositories that have priority 97 and automatic update flag active.
Since I adopted this strategy, for a few years now, I have never had a system crash due to anomalous automatic updates arriving without my realizing it.
The system seems to work well, it is under control.
Every now and then I happen to install applications with the “one-click-install” system and in this case, either I ask NOT to maintain the repositories or if I also need to maintain them they will add, as you know, to priority 99 and therefore my system, which It has no priority 99 repository, it allows me to be able to identify each addition very quickly and very well and configure them as best as possible by lowering their priority and deactivating the automatic update flag.
As I was saying, a system that seems to work and allows me a certain degree of control.
However, I noticed, as mentioned, that zypper does not seem to consider either the priority system or the automatic update flag, which is why I typically try to avoid using zypper, except in particular cases.

Having said that, here is the result of the repository list command.
You can see that actually the repository from which zypper installed the update has the automatic update flag disabled and the very low priority, highest number.
But, I repeat, I let it happen because the one from the OpenSUSE repository already didn’t work.

zypper lr -dP
#  | Alias                                        | Name                                                                 | Enabled | GPG Check | Refresh | Priority | Type     | URI                                                                                       | Service
---+----------------------------------------------+----------------------------------------------------------------------+---------+-----------+---------+----------+----------+-------------------------------------------------------------------------------------------+--------
 3 | Mozilla                                      | Mozilla                                                              | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.5/                    | 
 6 | VLC                                          | VLC                                                                  | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | https://download.videolan.org/pub/vlc/SuSE/15.5/                                          | 
 8 | download.nvidia.com-$releasever              | nVidia Graphics Drivers                                              | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | https://download.nvidia.com/opensuse/leap/15.5                                            | 
 9 | ftp.gwdg.de-openSUSE_Leap_$releasever        | Packman Repository                                                   | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.5/                        | 
32 | opensuse-guide.org-openSUSE_Leap_$releasever | Libdvdcss Repository                                                 | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://opensuse-guide.org/repo/openSUSE_Leap_15.5/                                        | 
33 | packman                                      | packman                                                              | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.5/                       | 
34 | repo-backports-debug-update                  | Update repository of openSUSE Backports (Debug)                      | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/update/leap/15.5/backports_debug/                            | 
35 | repo-backports-update                        | Update repository of openSUSE Backports                              | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/update/leap/15.5/backports/                                  | 
36 | repo-debug                                   | Debug Repository                                                     | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/debug/distribution/leap/15.5/repo/oss/                       | 
37 | repo-debug-non-oss                           | Debug Repository (Non-OSS)                                           | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/debug/distribution/leap/15.5/repo/non-oss/                   | 
38 | repo-debug-update                            | Update Repository (Debug)                                            | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/debug/update/leap/15.5/oss/                                  | 
39 | repo-debug-update-non-oss                    | Update Repository (Debug, Non-OSS)                                   | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/debug/update/leap/15.5/non-oss/                              | 
40 | repo-non-oss                                 | Repository Non-OSS                                                   | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/distribution/leap/15.5/repo/non-oss/                         | 
41 | repo-openh264                                | Open H.264 Codec (openSUSE Leap)                                     | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://codecs.opensuse.org/openh264/openSUSE_Leap/                                        | 
42 | repo-oss                                     | Repository principale                                                | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/distribution/leap/15.5/repo/oss/                             | 
43 | repo-sle-debug-update                        | Update repository with updates from SUSE Linux Enterprise 15 (Debug) | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/debug/update/leap/15.5/sle/                                  | 
44 | repo-sle-update                              | Update repository with updates from SUSE Linux Enterprise 15         | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/update/leap/15.5/sle/                                        | 
45 | repo-source                                  | Source Repository                                                    | No      | ----      | ----    |   97     | N/A      | http://download.opensuse.org/source/distribution/leap/15.5/repo/oss/                      | 
46 | repo-update                                  | Repository principale degli aggiornamenti                            | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/update/leap/15.5/oss                                         | 
47 | repo-update-non-oss                          | Repository degli aggiornamenti (Non-Oss)                             | Sì      | (r ) Sì   | Sì      |   97     | rpm-md   | http://download.opensuse.org/update/leap/15.5/non-oss/                                    | 
 5 | Scrivania                                    | Scrivania                                                            | Sì      | ( p) Sì   | No      |  100     | plaindir | dir:/home/renedrive/Scrivania                                                             | 
31 | openSUSE-Leap-15.5-1                         | openSUSE-Leap-15.5-1                                                 | No      | ----      | ----    |  100     | rpm-md   | hd:/?device=/dev/disk/by-id/dm-name-ventoy                                                | 
 1 | Game                                         | Game                                                                 | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/games/15.5/                                    | 
 2 | GamesTools                                   | GamesTools                                                           | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/games:/tools/15.5/                             | 
 4 | PlexRepo                                     | PlexRepo                                                             | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://downloads.plex.tv/repo/rpm/x86_64/                                                | 
 7 | Wine                                         | Wine                                                                 | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/Emulators:/Wine/15.5/                          | 
10 | hardware                                     | hardware                                                             | Sì      | (r ) Sì   | Sì      |  101     | rpm-md   | https://download.opensuse.org/repositories/hardware/15.5/                                 | 
17 | https-download.opensuse.org-23aaaa01         | multimedia:proaudio                                                  | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/multimedia:/proaudio/15.5/                     | 
19 | https-download.opensuse.org-43698cd4         | windows:mingw:win32                                                  | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_15.5/      | 
22 | https-download.opensuse.org-8c639583         | windows:mingw:win64                                                  | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/windows:/mingw:/win64/openSUSE_Leap_15.5/      | 
23 | https-download.opensuse.org-a4841028         | devel:tools:building                                                 | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/devel:/tools:/building/15.5/                   | 
24 | https-download.opensuse.org-a7b04f5c         | SUSE:SLE-15:Update                                                   | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/distribution/leap/15.5/repo/oss/                            | 
25 | https-download.opensuse.org-cbc705b0         | openSUSE:Leap:15.5:Update                                            | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/update/leap/15.5/oss/                                       | 
26 | https-download.opensuse.org-d3d3b458         | openSUSE:Leap:15.5                                                   | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/openSUSE:/Leap:/15.5/standard/                 | 
27 | https-download.opensuse.org-e6b18b91         | openSUSE:Backports:SLE-15-SP5                                        | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP5/standard/      | 
28 | multimedia:apps                              | multimedia:apps                                                      | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/multimedia:apps/15.5/                          | 
29 | multimedia:libs                              | multimedia:libs                                                      | Sì      | (r ) Sì   | No      |  101     | rpm-md   | https://download.opensuse.org/repositories/multimedia:libs/15.5/                          | 
30 | network                                      | network                                                              | Sì      | (r ) Sì   | Sì      |  101     | rpm-md   | https://download.opensuse.org/repositories/network/15.5/                                  | 
11 | home:AndnoVember:LXQt                        | home:AndnoVember:LXQt                                                | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:AndnoVember:LXQt/15.5/                    | 
12 | home:_Sauerland                              | home: Sauerland                                                      | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_15.5/  | 
13 | home:ecsos                                   | home:ecsos                                                           | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:ecsos/15.5/                               | 
14 | home:malkav                                  | home:malkav                                                          | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:malkavi/15.5/                             | 
15 | home:mpoleur:KDE:Extra                       | home:mpoleur:KDE:Extra                                               | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:mpoleur:KDE:Extra/15.5/                   | 
16 | home:plater                                  | home:plater                                                          | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:plater/15.5/                              | 
18 | https-download.opensuse.org-28daa22f         | home:kimi:zoom                                                       | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:/kimi:/zoom/15.5/                         | 
20 | https-download.opensuse.org-67679826         | home:rncbc:qt6.6-static                                              | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:/rncbc:/qt6.6-static/openSUSE_Leap_15.5/  | 
21 | https-download.opensuse.org-7a5c1b29         | home:ahmedmoselhi2:branches:Emulators                                | Sì      | (r ) Sì   | No      |  104     | rpm-md   | https://download.opensuse.org/repositories/home:/ahmedmoselhi2:/branches:/Emulators/15.5/ |

Given that often, when requesting help, I am asked to “clean up” the repository list, I am convinced that this cleaning makes no difference given the attention I pay when I manually install or update some applications (as explained above).
Of course, I agree that a “cleaner” repository list is less risky than one like mine, but I can assure you that I have to get heavily distracted in order to make mistakes and install “unsuitable” software on my system, this is because I was left “burned” " many times and therefore I always pay close attention, and, certainly, a distraction can happen, and there have been some, but they are very rare thanks to this organization of mine and those rare times that it happens to recover by installing the correct versions again is an easy game even thanks to the configuration I use.

However, if you believe that the current version not working may be different from the previous version not working, taken from the official repositories, there is no problem, going back to the other version is easy.

12

Very interesting.
Can I ask you what the log that generates the command shows?
Is this the normal system log or do the added switches do anything special?
I see a lot of warnings and some errors.
Also another question.
What is that system you linked to?
What is it for?
To share large files?
I see it has a “Private” option that is turned on.
How to use?
Sorry but it’s something I’ve never seen or used.

Ok, maybe I figured it out myself.
I was trying to insert the result of the command here and it tells me that the limit is 32000 characters, I think, and that I was trying to insert 300000.
So that’s what that link is for?

So I guess I have to post the link that system provided me!?!?
https://paste.opensuse.org/pastes/3cb8eb4d82f5

13 
apr 09 16:17:23 rene-alien kernel: Bluetooth: hci0: Opcode 0x1005 failed: -110
apr 09 16:17:23 rene-alien kernel: Bluetooth: hci0: command 0x1005 tx timeout

As I said - it is most likely hardware issue, may be missing firmware.

14

Does it help, if you unload and load bluetooth as root:

rmmod btusb
modprobe btusb

or
systemctl restart bluetooth

15

If you mean hardware problem as hardware failure, I really don’t think so, in Windows 10 the stick is recognized, the automatically loaded driver doesn’t work, but by downloading the correct driver from the manufacturer it works correctly.
However, I too am convinced that the problem could be Linux with this specific hardware, which perhaps contains a chip that is not yet fully supported or that requires some “particular” procedure or configuration, or driver.

I’m trying to find and understand what exactly the problem is by looking for error -110, the one you see in the line
Apr 09 16:17:23 rene-alien kernel: Bluetooth: hci0: Opcode 0x1005 failed: -110
but it’s not easy to find.
I imagine it’s something like missing device, or not recognized or not supported, but I’m not sure, I can’t find a real explanation.

However, I have found several threads talking about this exact Bluetooth dongle, same make and model, and many have problems.
Some say they solved it by moving from kernel 5.4 to 5.13, but I have 5.14, I expect that if it is more recent it still contains the above, although I’m not sure.
But it’s also true that we’re talking about different Linux distributions, maybe the kernels are different, I don’t know.
Most seem not to have resolved, perhaps, as I assumed, this hardware is not yet supported.

I don’t know what to think, maybe I should just wait for a new kernel version!?!?
Since this flash drive is quite recent but has been on sale for a few months, I was hoping there were already solutions to make it compatible.

16

OK, it is something between the kernel driver and the dongle. No amount of fiddling with user space is going to help until kernel is capable to talk to the device.

That’s possible.

Try kernel from /repositories/Kernel:/stable:/Backport/standard - openSUSE Download

17

I tried the first two commands you recommended, as root.
Checking that they worked as expected.

# rmmod btusb
# lsmod | grep bluetooth
bluetooth             901120  13 btrtl,btmtk,btintel,btbcm,bnep
ecdh_generic           16384  1 bluetooth
rfkill                 28672  8 bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4
# modprobe btusb
# lsmod | grep bluetooth
bluetooth             901120  15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 28672  8 bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4

But after these the result did not change.

# bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# list
[bluetooth]# devices
No default controller available

However, I also tried the command

systemctl restart bluetooth

But nothing has changed

# bluetoothctl devices
No default controller available
18

I know, it’s written in the repository name, but I want to be sure.
Do you consider this repository that you recommend reliable and stable?
Sorry to ask, but I try to be very careful about the repositories I add.
Maybe I add it with a low priority and disabling automatic updates, then I try upgrading the kernel only, always with the possibility of returning to the standard one.
Do you think it could cause malfunctions to other peripherals?
I don’t know, I’m just being cautious!?!? :slight_smile:

19

All your installed kmps will not work anymore, they are build against kernel 5.14 from Leap.
So you have to add other Repos to get them working with kernel:stable:backports.

PS:
I used kernel:stable:backports for years without problems.

20

Thank you very much for the information about your personal experience with this kernel and its stability.

I apologize for this but I don’t think I’m able to fully understand your statement about kmps.
I’m not sure what kmps means.
I don’t really understand what might no longer work after the update.
You tell me that I should therefore add other repositories, but I guess I should know which ones they are based on “what I need to work”, but I don’t know how I would know what I need?!?
Is there a way to know what I need and therefore find the right repositories or do I have to check everything again after the update and then search for the most suitable repositories?

Sorry for these questions but I’m a little too inexperienced to know enough about this topic.