Bug 1329800 - NetworkManager Bluetooth update breaks Bluetooth and shows "Visible as "Bastien's computer"
Summary: NetworkManager Bluetooth update breaks Bluetooth and shows "Visible as "Basti...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-23 08:18 UTC by mikey
Modified: 2016-12-20 20:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:06:29 UTC
Type: Bug


Attachments (Terms of Use)

Description mikey 2016-04-23 08:18:07 UTC
Description of problem:

There are 2 issues here but they appear together and relate to the same update on the same component so I will report them together.

Firstly after the update to NetworkManager-1:1.0.12-2.fc23.x86_64 bluetooth stopped working. The devices in the gnome Bluetooth settings window were now empty. 

Also where before the Bluetooth settings window showed the message:

    Visible as "MY_PC" and available for Bluetooth file transfers. Transferred files are placed in the Downloads folder.

It was now showing::

        Visible as "Bastien's computer" and available for Bluetooth file transfers. Transferred files are placed in the Downloads folder.

Who is this Bastien?

Anyway I can see a Debian bug report for a similar issue with Bluetooth settings showing "Bastien's computuer":

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803719

Downgrading network manager to NetworkManager-1:1.0.6-6.fc23.x86_64 has restored Bluetooth function.

I have separate usb wifi and bluetooth dongles:

~ lsusb | grep -i "\(bluetooth\|WLAN\)"
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter

I am using the following wifi drivers as my previous wifi drivers also broke with the upgrade to NetworkManager:

https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git 

See:

https://github.com/gnab/rtl8812au/issues/80

Comment 1 Fedora End Of Life 2016-11-25 07:27:01 UTC
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 2 Fedora End Of Life 2016-12-20 20:06:29 UTC
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
bug.

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.