Bug 1295724 - using blueman-applet getting connect error after some time
using blueman-applet getting connect error after some time
Product: Fedora
Classification: Fedora
Component: blueman (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Pete Walter
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-05 05:55 EST by Aleksandar Kostadinov
Modified: 2016-12-20 12:37 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:37:27 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Aleksandar Kostadinov 2016-01-05 05:55:55 EST
Description of problem:
First, I use a thinkpad external bluetooth keyboard that fails to automatically connect to t530 so I use the mouse to open blueman-applet and connect it.

But after some time, when I try to connect it through applet, I see in status bar:
> Connection Failed: Connection ":1.39" is not allowed to add more match rules (increase limits in configuration file if required)

At this point, using bluetoothctl gets the thing connected.

Version-Release number of selected component (if applicable):
blueman: 2.0
BlueZ: 5.36
Desktop: XFCE

How reproducible:
After continuous use for a few days. Sometimes earlier, sometimes later.

P.S. I tried using `force_cam` to no avail, keyboard does not want to connect automatically most of the times. If you have any idea how to resolve that, would also be appreciated! Interesting observation is that if I hit many keys while trying to connect, chances to connect are higher. Not sure why.
Comment 1 Aleksandar Kostadinov 2016-01-05 06:32:48 EST
FYI upstream bug: https://github.com/blueman-project/blueman/issues/422
Comment 2 Fedora Admin XMLRPC Client 2016-06-21 12:26:49 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora End Of Life 2016-11-24 09:42:56 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.
Comment 4 Fedora End Of Life 2016-12-20 12:37:27 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

Thank you for reporting this bug and we are sorry it could not be fixed.

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