Description of problem: Friendly name (defaults to "Broadcom BCM2035") is not saved when changed to something else. Version-Release number of selected component (if applicable): gnome-bluetooth-2.28.6-1.fc12.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Edit the friendly name. Close the applet via close button and reopen it, everything is fine. 2. Reboot the system, the friendly name has changed back to "Broadcom BCM2035". 3. Actual results: Expected results: Additional info:
Please check for bluetoothd-related and "Bluetooth" errors (check for hci) in /var/log/messages
[root@orilla ~]# grep -i blue /var/log/messages Jan 10 19:27:55 orilla kernel: usb 3-2.1: Product: Wireless Radio for Bluetooth 2.0 Jan 10 19:27:55 orilla kernel: Bluetooth: Core ver 2.15 Jan 10 19:27:55 orilla kernel: Bluetooth: HCI device and connection manager initialized Jan 10 19:27:55 orilla kernel: Bluetooth: HCI socket layer initialized Jan 10 19:27:55 orilla kernel: Bluetooth: Generic Bluetooth USB driver ver 0.6 Jan 10 19:27:55 orilla bluetoothd[2497]: Bluetooth daemon 4.58 Jan 10 19:27:55 orilla bluetoothd[2500]: Starting SDP server Jan 10 19:27:55 orilla kernel: Bluetooth: L2CAP ver 2.13 Jan 10 19:27:55 orilla kernel: Bluetooth: L2CAP socket layer initialized Jan 10 19:27:55 orilla bluetoothd[2500]: Parsing /etc/bluetooth/network.conf failed: No such file or directory Jan 10 19:27:55 orilla kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Jan 10 19:27:55 orilla kernel: Bluetooth: BNEP filters: protocol multicast Jan 10 19:27:55 orilla bluetoothd[2500]: bridge pan0 created Jan 10 19:27:55 orilla bluetoothd[2500]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Jan 10 19:27:55 orilla bluetoothd[2500]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Jan 10 19:27:55 orilla bluetoothd[2500]: HCI dev 0 registered Jan 10 19:27:55 orilla kernel: Bluetooth: SCO (Voice Link) ver 0.6 Jan 10 19:27:55 orilla kernel: Bluetooth: SCO socket layer initialized Jan 10 19:27:55 orilla bluetoothd[2500]: HCI dev 0 up Jan 10 19:27:55 orilla bluetoothd[2500]: Starting security manager 0 Jan 10 19:27:56 orilla bluetoothd[2500]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Jan 10 19:27:56 orilla kernel: Bluetooth: RFCOMM TTY layer initialized Jan 10 19:27:56 orilla kernel: Bluetooth: RFCOMM socket layer initialized Jan 10 19:27:56 orilla kernel: Bluetooth: RFCOMM ver 1.11 Jan 10 19:27:56 orilla bluetoothd[2500]: Adapter /org/bluez/2497/hci0 has been enabled Jan 10 19:27:56 orilla kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [root@orilla ~]# [root@orilla ~]# grep -i hci /var/log/messages Jan 10 19:22:57 orilla kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: PCI INT B -> Link[APCL] -> GSI 23 (level, low) -> IRQ 23 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: EHCI Host Controller Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: debug port 1 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: irq 23, io mem 0xfc106000 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00 Jan 10 19:22:57 orilla kernel: usb usb1: Product: EHCI Host Controller Jan 10 19:22:57 orilla kernel: usb usb1: Manufacturer: Linux 2.6.31.9-174.fc12.x86_64 ehci_hcd Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:01:07.2: PCI INT C -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:01:07.2: EHCI Host Controller Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:01:07.2: new USB bus registered, assigned bus number 2 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:01:07.2: irq 17, io mem 0xfc005000 Jan 10 19:22:57 orilla kernel: ehci_hcd 0000:01:07.2: USB 2.0 started, EHCI 1.00 Jan 10 19:22:57 orilla kernel: usb usb2: Product: EHCI Host Controller Jan 10 19:22:57 orilla kernel: usb usb2: Manufacturer: Linux 2.6.31.9-174.fc12.x86_64 ehci_hcd Jan 10 19:22:57 orilla kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 10 19:22:57 orilla kernel: ohci_hcd 0000:00:02.0: PCI INT A -> Link[APCF] -> GSI 22 (level, low) -> IRQ 22 Jan 10 19:22:57 orilla kernel: ohci_hcd 0000:00:02.0: OHCI Host Controller Jan 10 19:22:57 orilla kernel: ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3 Jan 10 19:22:57 orilla kernel: ohci_hcd 0000:00:02.0: irq 22, io mem 0xfc105000 Jan 10 19:22:57 orilla kernel: usb usb3: Product: OHCI Host Controller Jan 10 19:22:57 orilla kernel: usb usb3: Manufacturer: Linux 2.6.31.9-174.fc12.x86_64 ohci_hcd Jan 10 19:22:57 orilla kernel: uhci_hcd: USB Universal Host Controller Interface driver Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.0: PCI INT A -> Link[APC4] -> GSI 19 (level, low) -> IRQ 19 Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.0: UHCI Host Controller Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.0: new USB bus registered, assigned bus number 4 Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.0: irq 19, io base 0x00008000 Jan 10 19:22:57 orilla kernel: usb usb4: Product: UHCI Host Controller Jan 10 19:22:57 orilla kernel: usb usb4: Manufacturer: Linux 2.6.31.9-174.fc12.x86_64 uhci_hcd Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.1: PCI INT B -> Link[APC1] -> GSI 16 (level, low) -> IRQ 16 Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.1: UHCI Host Controller Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.1: new USB bus registered, assigned bus number 5 Jan 10 19:22:57 orilla kernel: uhci_hcd 0000:01:07.1: irq 16, io base 0x00008400 Jan 10 19:22:57 orilla kernel: usb usb5: Product: UHCI Host Controller Jan 10 19:22:57 orilla kernel: usb usb5: Manufacturer: Linux 2.6.31.9-174.fc12.x86_64 uhci_hcd Jan 10 19:22:57 orilla kernel: usb 1-4: new high speed USB device using ehci_hcd and address 2 Jan 10 19:22:57 orilla kernel: usb 1-8: new high speed USB device using ehci_hcd and address 3 Jan 10 19:22:57 orilla kernel: usb 3-9: new low speed USB device using ohci_hcd and address 2 Jan 10 19:22:57 orilla kernel: usb 5-2: new low speed USB device using uhci_hcd and address 2 Jan 10 19:22:57 orilla kernel: firewire_ohci 0000:01:0a.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18 Jan 10 19:22:57 orilla kernel: firewire_ohci: Added fw-ohci device 0000:01:0a.0, OHCI version 1.10 Jan 10 19:27:54 orilla kernel: usb 3-2: new full speed USB device using ohci_hcd and address 3 Jan 10 19:27:55 orilla kernel: usb 3-2.1: new full speed USB device using ohci_hcd and address 4 Jan 10 19:27:55 orilla kernel: usb 3-2.2: new full speed USB device using ohci_hcd and address 5 Jan 10 19:27:55 orilla kernel: Bluetooth: HCI device and connection manager initialized Jan 10 19:27:55 orilla kernel: Bluetooth: HCI socket layer initialized Jan 10 19:27:55 orilla kernel: usb 3-2.3: new full speed USB device using ohci_hcd and address 6 Jan 10 19:27:55 orilla bluetoothd[2500]: HCI dev 0 registered Jan 10 19:27:55 orilla bluetoothd[2500]: HCI dev 0 up Jan 10 19:27:56 orilla bluetoothd[2500]: Adapter /org/bluez/2497/hci0 has been enabled Jan 10 19:28:00 orilla kernel: usb 3-2.3: new full speed USB device using ohci_hcd and address 7 Jan 10 19:28:27 orilla kernel: hci_cmd_task: hci0 command tx timeout [root@orilla ~]# The only error I can find is orilla kernel: hci_cmd_task: hci0 command tx timeout. If I run bluetooth-applet -d I get lot of these, but nothing usefull: [root@orilla ~]# bluetooth-applet -d ** Message: adding killswitch idx 0 state 1 ** Message: killswitch 0 is 1 ** Message: killswitches state 1 ** Message: killswitch 0 is 1 ** Message: killswitches state 1 ** Message: RFKILL event: idx 0 type 2 op 2 soft 1 hard 0 ** Message: updating killswitch status 0 ** Message: killswitch 0 is 0 ** Message: killswitches state 0 ** Message: killswitch 0 is 0 ** Message: killswitches state 0 ** Message: adding killswitch idx 0 state 0 ** Message: killswitch 0 is 0 ** Message: killswitches state 0 ** Message: RFKILL event: idx 0 type 2 op 2 soft 0 hard 0 If I disable the bluetooth via the applet, the changed name is (greyed out as the whole dialog) still visible. The moment I reenable the bluetooth, the name changes back to the default (broadcom ....).
Either your bluetooth dongle, or the kernel has problems: Jan 10 19:28:27 orilla kernel: hci_cmd_task: hci0 command tx timeout
I can confirm this. Also happens with blueman. It worked fien in fedora 11, so unlikely to be a problem with the dongle..
I have this issue on several different machines with many different bluetooth dongles. I can confirm this is still a bug in Fedora 13 and 14 Alpha builds, same as above descriptions.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.