Bug 1047864
| Summary: | can't connect to bluetooth network (provided by smartphone "sharing network" via BT) in F20 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Jaša <djasa> | ||||
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 22 | CC: | dcbw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-07-19 10:50:32 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: |
|
||||||
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |
Created attachment 844521 [details] full logs Description of problem: It's not possible to connect to a bt network created by network sharing on the smartphone. Version-Release number of selected component (if applicable): gnome-session-3.10.1-1.fc20.x86_64 NetworkManager-0.9.9.0-22.git20131003.fc20.x86_64 ModemManager-1.1.0-2.git20130913.fc20.x86_64 dbus-1.6.12-7.fc20.x86_64 bluez-5.12-1.fc20.x86_64 systemd-208-9.fc20.x86_64 dhclient-4.2.5-26.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. pair a F20 computer with a smartphone 2. enable network sharing on the smartphone 3. connect to the bluetooth network: * enable bluetooth network device(s) in gnome-shell system status menu * go to gnome-system-settings - network, enable "bluetooth" connection Actual results: connection fails almost instantly with no notification in gnome-shell. Looking into the logs, there seem to be several modes of failure: * NM thinks the device is active when it isn't so it proceeds with dhcp and IPv6 auto-configuration * the device is not recognized note that each way of connection activation produces slightly different log - I tried to capture them all in the attachment Expected results: connection is established successfully Additional info: when you click "bluetooth" network in gnome-shell system status menu, you can see up to three entries for bluetooth connection: * GT-I8190 Bluetooth Network [||| Off] * GT-I8190 Network [||| Off] * GT-I8190 Network [||| Off] First was a network connection that I renamed and subsequently deleted using 'nmcli con'. I have no idea why it still appears...