[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Invalid Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.50-0ubuntu0ppa1 amd64bluez obex da
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Tried the bluez PPA before, but it didn't help. Since I don't own this notebook anymore, this issue is resolved for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Incomplete Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.50-0u
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Next, please report the bug to the BlueZ developers here: https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers&component=Bluetooth and then tell us what the new bug ID is. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Incomplete Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
You may also wish to test version 5.50 in case it solves the problem: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: Incomplete Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Bluetooth "crashes" in the sense that I can't establish any Bluetooth connection anymore, even from a device that was not paired or connected at the moment the "crash" happened. Only a "sudo service bluetooth restart" helps. Therefore my /var/crash/ folder is empty. I thought that this is the right place to handle such bugs. Who would have the expertise to help me on that subject then? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
If something is "crashing" then please follow the instructions for reporting crashes: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted b
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Sorry, I don't have any more expertise on the matter. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macOS. It also worked well with another notebook (Toshiba Satellite Pro C850-1HL) from 17.04 to 18.04, which I don't own anymore. I've updated my BlueZ stack with ppa:bluetooth/bluez, but reverted back by purging it, because it didn't help. I also have some debug info FROM LAST WEEK. This was collected after a system restart and while the keyboard tried to reestablish the connection. At this time my BlueZ packages were from the PPA mentioned above: $ dpkg -l | grep blue ii bluez 5.50-0ubuntu0ppa1 amd64Bluetooth tools and daemons ii bluez-cups 5.50-0ubuntu0ppa1 amd64Bluetooth printer driver for CUPS ii bluez-obexd5.50-0ubuntu0ppa1 amd64bluez obex daemon ii gir1.2
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
Your suggestion didn't help. Bluetooth is still crashing when the keyboard is connecting, either from the keyboard itself or through bluetoothctl. To be on the safe side, I paired the keyboard again and restarted Ubuntu, but it still won't connect again after a connection loss: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed It seems that my mouse is now nearly instantly connecting though, but no guarantees on that. I really can't explain why this is happening :( Repairing the keyboard after each lost connection isn't an option, especially because I always have to type the confirmation code on the keyboard, while pairing. Didn't you spot something unusual in my debug info? From my layman's view, there seem to be a lot of error messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also on a MacBook Pro with macO
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
This is surprising. It sounds like reconnecting is disabled by default unless you specify exactly which devices to reconnect in /etc/bluetooth/main.conf: # The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb So maybe try editing /etc/bluetooth/main.conf and change: #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb to: ReconnectUUIDs=1124--1000-8000-00805f9b34fb, 1812--1000-8000-00805f9b34fb in an attempt to auto-reconnect your Human Interface Devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also
