Bluetooth RFCOMM: Transport endpoint not connected (kernel regression)

[Petr Stehlik]

Ubuntu 12.04's "Hardware Enablement Stack (HWE)" check forced me to upgrade to trusty's kernel:
* Install a newer HWE version by running:
sudo apt-get install linux-generic-lts-trusty linux-image-generic-lts-trusty

Since then bluetooth communication fails with "Transport endpoint not connected". It does work OK if I reboot back to soon-to-be unsupported kernel 3.5.0.x

This is a known kernel 3.13 regression, please see https://bugzilla.redhat.com/show_bug.cgi?id=1060457

If it is indeed fixed in kernel 3.14 please backport the fix to trusty's kernel, or perhaps get 3.14 kernel into trusty. The current 3.13 is not a good upgrade.

Thanks!
---
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3119 F.... pulseaudio
CasperVersion: 1.340build1
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140719)
MachineType: Acer Aspire V3-571G
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-4-generic N/A
 linux-backports-modules-3.16.0-4-generic N/A
 linux-firmware 1.132
Tags: utopic
Uname: Linux 3.16.0-4-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/16/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.21
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571G:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.21
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1342570

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Petr Stehlik (pstehlik)]

apport-collect failed when run over ssh on the server so I am changing the bug status to confirmed.

[penalvch (penalvch)]

Petr Stehlik, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a terminal, as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux 1342570

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[Petr Stehlik (pstehlik)]

apport information

[penalvch (penalvch)]

Petr Stehlik, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.16-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[José Serra (serrajv)]

It's solved installing kernel 3.14.15. Tested with Ubuntu 14.04.

[penalvch (penalvch)]

José Serra Mendoza, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]