Bug 1899526 - kernel-5.9.8-100.fc32.x86_64 breaks bluetooth mouse functionality
Summary: kernel-5.9.8-100.fc32.x86_64 breaks bluetooth mouse functionality
Keywords:
Status: CLOSED DUPLICATE of bug 1897038
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-19 13:39 UTC by Reinout van Schouwen
Modified: 2020-11-19 13:48 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-19 13:48:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Reinout van Schouwen 2020-11-19 13:39:27 UTC
1. Please describe the problem:
When upgrading to kernel 5.9.8, my Logitech MX Master 2S no longer connects via bluetooth to my laptop. 

2. What is the Version-Release number of the kernel:
5.9.8-100

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes it worked before. Downgrading to the previous version, 5.8.18, fixes the problem.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

i. Boot kernel 5.9.8
ii. Pair with the bluetooth mouse from Settings > Bluetooth


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

I cannot test. If I follow the above instructions I get a warning that the GPG check failed and the kernel package is not installed.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

VirtualBox kernel modules

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Will attach this later as I currently only have the 5.8 output.

Additional info: This thread on the Arch Linux forum looks like it is about the same problem.

https://bbs.archlinux.org/viewtopic.php?id=259954&p=2

Comment 1 Justin M. Forbes 2020-11-19 13:48:34 UTC

*** This bug has been marked as a duplicate of bug 1897038 ***


Note You need to log in before you can comment on or make changes to this bug.