Bug 1048420

Summary: Regression: Bluetooth DUN fails.
Product: [Fedora] Fedora Reporter: Björn Persson <bjorn>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-25 21:55:55 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 Flags
log none

Description Björn Persson 2014-01-04 05:34:17 UTC 
Created attachment 845204 [details]
log

Description of problem:
kernel-3.12.6-200.fc19 fails to bring up a Bluetooth DUN connection. kernel-3.11.9-200.fc19 can bring up the connection (but has bug 1008112).

Version-Release number of selected component (if applicable):
3.12.6-200.fc19.x86_64

How reproducible:
It seems perfectly reproducible to me.

Steps to Reproduce:
1. Enable Bluetooth in the phone.
2. Enable Bluetooth in the laptop.
3. Try to bring up a DUN connection that has been configured earlier.

Actual results:
Network Manager begins configuring the connection, pauses, and then reports that the network has been disconnected. In the log the error seems to be "modem-not-found".

Expected results:
A network connection.

Additional info:
This prevents me from checking if bug 1008112 is still there.
Comment 1 Justin M. Forbes 2014-03-10 14:52:15 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.13.5-100.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.
Comment 2 Björn Persson 2014-03-10 15:36:25 UTC 
No improvement in 3.13.5-103.fc19.x86_64.
Comment 3 Justin M. Forbes 2014-05-21 19:31:31 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.14.4-100.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 4 Björn Persson 2014-05-25 21:55:55 UTC 
With 3.14.4-100.fc19.x86_64 I don't have this problem.