Bug 767335

Summary: Gnome Shell's Bluetooth menu does not update to reflect presence of new devices
Product: [Fedora] Fedora Reporter: James <james>
Component: gnome-bluetoothAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bnocera, browning48ky, marc.novel, maxamillion, otaylor, samkraju, walters
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: 2013-02-13 20:13:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Content of .xsession-errors immediately after restarting Gnome Shell, then pairing with Bluetooth headset none

Description James 2011-12-13 20:16:21 UTC
Description of problem:
Computer-initiated pairing with a new Bluetooth device does not produce a new entry for that device in the Gnome Shell Bluetooth menu.

Version-Release number of selected component (if applicable):
gnome-shell-3.2.1-2.fc16.x86_64
bluez-4.96-3.fc16.x86_64
udev-173-3.fc16.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Pair with a new device.
2. Check menu again.
  
Actual results:
Same as the menu before pairing.

Expected results:
New entry for paired device.

Additional info:
Have to restart Gnome Shell to get device entry to appear.

Comment 1 James 2011-12-13 20:21:23 UTC
Created attachment 546382 [details]
Content of .xsession-errors immediately after restarting Gnome Shell, then pairing with Bluetooth headset

Comment 2 James 2011-12-13 20:25:40 UTC
Further note: the menu does seem to update when a device is removed.

Comment 3 James 2012-01-18 15:29:35 UTC
Upstream at https://bugzilla.gnome.org/show_bug.cgi?id=666127#c5 has committed a fix --- any word on when a fix will make F16 updates-testing?

Comment 4 Fedora End Of Life 2013-01-16 16:28:47 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 20:13:04 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.