Description of problem: Paired device stopped working after a while Version-Release number of selected component (if applicable): bluez.x86_64 5.54-1.fc32 @fedora How reproducible: working a while with the bt-device Additional info: before: [General] Name=M585/M590 Appearance=0x03c2 AddressType=static SupportedTechnologies=LE; Trusted=true Blocked=false Services=00001800-0000-1000-8000-00805f9b34fb;00001801-0000-1000-8000-00805f9b34fb;0000180a-0000-1000-8000-00805f9b34fb;0000180f-0000-1000-8000-00805f9b34fb;00001812-0000-1000-8000-00805f9b34fb;00010000-0000-1000-8000-011f2000046d; [ConnectionParameters] MinInterval=6 MaxInterval=9 Latency=44 Timeout=216 [IdentityResolvingKey] Key=9B1B6038AECEC8A1F6CB46B2C637FD4C [LocalSignatureKey] Key=587C30F216601ECCFB1BD0CDD2EF5888 Counter=0 Authenticated=false [LongTermKey] Key=4628B287EEB8DE6625C37F0B65C5F61D Authenticated=0 EncSize=16 EDiv=16155 Rand=3469490741712050246 [DeviceID] Source=2 Vendor=1133 Product=45083 Version=17 [ServiceChanged] CCC_LE=2` after: [General] Name=M585/M590 Appearance=0x03c2 AddressType=static SupportedTechnologies=LE; Trusted=true Blocked=false [ConnectionParameters] MinInterval=6 MaxInterval=9 Latency=44 Timeout=216 [IdentityResolvingKey] Key=9B1B6038AECEC8A1F6CB46B2C637FD4C [LocalSignatureKey] Key=587C30F216601ECCFB1BD0CDD2EF5888 Counter=0 Authenticated=false [LongTermKey] Key=4628B287EEB8DE6625C37F0B65C5F61D Authenticated=0 EncSize=16 EDiv=16155 Rand=3469490741712050246 [DeviceID] Source=2 Vendor=1133 Product=45083 Version=17 [ServiceChanged] CCC_LE=2 tagged this bug to bluez because of it's native filepath, but maybe another component is responsible for this bug ...
Oh, by manually adding the services value by a texteditor and restarting bluetooth I'm able to work with this device for a while ...
FEDORA-2020-00bf5ac290 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-00bf5ac290
FEDORA-2020-00bf5ac290 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-00bf5ac290` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-00bf5ac290 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Ok ... upgraded, now I'll try it for a while. You'll get a feedback, soon :-)
FEDORA-2020-00bf5ac290 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
OK, seems to be workin ... But the connection hangs sometimes for a second. It looks like resyncing because of LE. The configs are fine now. TNX! ... cheers speedy :-)
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.