Description of problem: If wireless is on, a connection to a bluetooth mouse isn't possible. If wireless is turned off, a connection to a bluetooth mouse is possible. So I have to disable wireless, then connect to the mouse, then enable wireless. And the neither the GUI nor journal make it at all obvious there is a relationship between wireless and bluetooth I just guessed this on my own by poking this thing with a stick until I stumbled on it. Version-Release number of selected component (if applicable): bluez-5.39-1.fc24.x86_64 kernel-4.6.0-1.fc25.x86_64 kernel-4.5.5-300.fc24.x86_64 (happens with either kernel, and much older kernels as well) How reproducible: Always Steps to Reproduce: 1. Settings > Bluetooth > Mouses (click) > set Connection from Off to On. 2. 3. Actual results: A few seconds go by, then the UI switch flips from On to Off by itself, no error message of any kind in the GUI. And the mouse does not work. Expected results: I expect the connection to remain on, and for the bluetooth mouse to work. Additional info: In the journal I get this when it fails to connect: May 28 21:29:59 f24m bluetoothd[825]: Can't get HIDP connection info May 28 21:30:04 f24m bluetoothd[825]: connect error: Host is down (112) If I try to connect with bluetoothctl I see this [bluetooth]# connect 58:1F:AA:EB:B4:6A Attempting to connect to 58:1F:AA:EB:B4:6A Failed to connect: org.bluez.Error.Failed [bluetooth]# There's no related kernel messages, but for whatever reason wlp3s0b1 (wireless) floods kernel messages with [17737.763308] wlp3s0b1: authenticate with b4:c7:99:ed:d6:c8 [17737.774424] wlp3s0b1: send auth to b4:c7:99:ed:d6:c8 (try 1/3) [17737.776605] wlp3s0b1: authenticated [17737.777140] wlp3s0b1: associate with b4:c7:99:ed:d6:c8 (try 1/3) [17737.834883] wlp3s0b1: RX AssocResp from b4:c7:99:ed:d6:c8 (capab=0x401 status=0 aid=2) [17737.835055] wlp3s0b1: associated [17857.760316] wlp3s0b1: authenticate with b4:c7:99:ee:3a:f0 [17857.771494] wlp3s0b1: send auth to b4:c7:99:ee:3a:f0 (try 1/3) [17857.774262] wlp3s0b1: authenticated [17857.775192] wlp3s0b1: associate with b4:c7:99:ee:3a:f0 (try 1/3) [17857.789615] wlp3s0b1: RX AssocResp from b4:c7:99:ee:3a:f0 (capab=0x401 status=0 aid=1) [17857.789832] wlp3s0b1: associated Seems unrelated and also wholly unnecessary. If I turn wifi off first, then try to connect I get this in the journal: 8 21:36:48 f24m bluetoothd[825]: Can't get HIDP connection info May 28 21:36:58 f24m kernel: magicmouse 0005:05AC:030D.0009: unknown main item tag 0x0 May 28 21:36:58 f24m kernel: input: mouses as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/bluetooth/hci0/hci0:12/0005:05AC:030D.0009/input/input18 May 28 21:36:58 f24m kernel: magicmouse 0005:05AC:030D.0009: input,hidraw3: BLUETOOTH HID v3.06 Mouse [mouses] on e0:f8:47:39:5d:df May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) config/udev: Adding input device mouses (/dev/input/mouse0) May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) No input driver specified, ignoring this device. May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) This device may have been added with another device file. May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) config/udev: Adding input device mouses (/dev/input/event7) May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: Applying InputClass "evdev pointer catchall" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: Applying InputClass "libinput pointer catchall" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 36 paused 0 May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) Using input driver 'libinput' for 'mouses' May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: always reports core events May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) Option "Device" "/dev/input/event7" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) Option "_source" "server/udev" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) input device 'mouses', /dev/input/event7 is tagged by udev as: Mouse May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) input device 'mouses', /dev/input/event7 is a pointer caps May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/bluetooth/hci0/hci0:12/0005:05AC:030D.0009/input/input18/event7" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) XINPUT: Adding extended input device "mouses" (type: MOUSE, id 15) May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) Option "AccelerationScheme" "none" May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: (accel) selected scheme none/0 May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: (accel) acceleration factor: 2.000 May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (**) mouses: (accel) acceleration threshold: 4 May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) input device 'mouses', /dev/input/event7 is tagged by udev as: Mouse May 28 21:36:58 f24m /usr/libexec/gdm-x-session[1693]: (II) input device 'mouses', /dev/input/event7 is a pointer caps
Created attachment 1162601 [details] journal.log journal for this boot
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.