Bug 1147700
| Summary: | Bluetooth connections disconnect shortly after their establishment (Thinkpad T440s) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | David Jaša <djasa> | ||||||||
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lrintel> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 7.0 | CC: | danw, dcbw, jklimes, lrintel, rkhan, thaller, vbenes | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | 7.1 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | NetworkManager-0.9.9.1-46.git20140326.4dba720.el7 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
NetworkManager did not properly observe changes in status of Bluetooth connections, causing them to be terminated shortly after establishment due to erroneously assumed time-out. The updated packages correct this issue.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-03-05 13:53:19 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
David Jaša
2014-09-29 22:00:03 UTC
Hi David Can we please get one of these laptops on loan to debug the issue? Without it, it is difficult to reproduce and fix. Will need it for 1-4 weeks max. please let me know Rashid Created attachment 943363 [details]
NM debug log
Created attachment 945021 [details]
nmcli connections and details
Created attachment 945035 [details]
journal log throughout bluetooth connections
The fix works (connection is established and holds) but there are some things that do not play well:
* the connection went down after few minutes without apparent reason. After reconnecting however, the connection holds
* there are actually two connections related to the bluetooth connection:
1) actual bluetooth "GT-I8190" connection. It's MAC address is given as the connection's Device
2) USB Ethernet "Wired Connection 1" on top of "bnep0" device which actually holds IP configuration
The result is that gnome-shell shows my "GT-I8190 Network" connection as "Activating..." forever and it shows the mysterious "Wired Connection 1" as active - but the network icon is showing activating wireless connection.
The gnome-shell (and gnome-control-center) behaviour may be also buggy (in a sense it is when bridges are in use) but I frankly don't understand why two connections do some interplay on top of a single device.
Yep, seen that in your original log. I thought the "Wired Connection 1" would not activate if we took hold of the bnep0 device correctly. Will look into it. > Lubomir Rintel 2014-10-10 12:03:34 CEST
> Status: MODIFIED → ON_QA
> Fixed In Version: NetworkManager-0.9.9.1-46.git20140326.4dba720.el7
Works like charm in this build.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0311.html |