Latest Updates Broke GNOME Bluetooth Support?
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 3 of 3
  1. #1
    cdrom600 Guest

    Latest Updates Broke GNOME Bluetooth Support?

    I think that the recent updates (I noticed one for bluez; I'm not sure what else was updated) broke the GNOME Bluetooth manager. I also think that the recent dbus problems may be contributing to this.

    I've confirmed this on two different systems, a laptop and a desktop, with the same Bluetooth USB key.

    The GNOME Bluetooth manager will appear in the system tray when the device is connected and disappear when it is disconnected, but none of the settings can be changed, the friendly name is not shown, etc.

    It looks to me like the computer is communicating on some level with the Bluetooth key, but GNOME isn't.

    Has anyone else noticed this? Does anyone know how to fix it?

    Code:
    # hciconfig
    hci0:	Type: USB
    	BD Address: 00:02:72:CD:4D:59 ACL MTU: 1017:8 SCO MTU: 64:8
    	UP RUNNING PSCAN ISCAN 
    	RX bytes:785 acl:0 sco:0 events:38 errors:0
    	TX bytes:676 acl:0 sco:0 commands:38 errors:0
    Code:
    # dmesg | tail -n 15
    eth1: MII #1 reports no link. Disabling watchdog.
    ADDRCONF(NETDEV_UP): eth1: link is not ready
    eth0: no IPv6 routers present
    fuse init (API version 7.9)
    usb 3-6: new full speed USB device using ohci_hcd and address 3
    usb 3-6: configuration #1 chosen from 1 choice
    usb 3-6: New USB device found, idVendor=0a5c, idProduct=2101
    usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    usb 3-6: Product: BCM92045DG-Flash
    usb 3-6: Manufacturer: Broadcom Corp
    Bluetooth: Generic Bluetooth USB driver ver 0.3
    usbcore: registered new interface driver btusb
    Bluetooth: RFCOMM socket layer initialized
    Bluetooth: RFCOMM TTY layer initialized
    Bluetooth: RFCOMM ver 1.10
    Code:
    # cat /var/log/messages | tail -n 30
    Dec 14 19:47:06 cdz-main pulseaudio[2879]: core-util.c: setpriority(): Permission denied
    Dec 14 19:47:07 cdz-main pulseaudio[2885]: pid.c: Stale PID file, overwriting.
    Dec 14 19:47:17 cdz-main gnome-session[2606]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout
    Dec 14 19:47:17 cdz-main pulseaudio[2974]: pid.c: Daemon already running.
    Dec 14 19:48:26 cdz-main kernel: usb 3-6: new full speed USB device using ohci_hcd and address 3
    Dec 14 19:48:27 cdz-main kernel: usb 3-6: configuration #1 chosen from 1 choice
    Dec 14 19:48:27 cdz-main kernel: usb 3-6: New USB device found, idVendor=0a5c, idProduct=2101
    Dec 14 19:48:27 cdz-main kernel: usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 14 19:48:27 cdz-main kernel: usb 3-6: Product: BCM92045DG-Flash
    Dec 14 19:48:27 cdz-main kernel: usb 3-6: Manufacturer: Broadcom Corp
    Dec 14 19:48:27 cdz-main kernel: Bluetooth: Generic Bluetooth USB driver ver 0.3
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: HCI dev 0 registered
    Dec 14 19:48:27 cdz-main kernel: usbcore: registered new interface driver btusb
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: HCI dev 0 up
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.NetworkPeer on path /org/bluez/2193/hci0
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.NetworkHub on path /org/bluez/2193/hci0
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.NetworkRouter on path /org/bluez/2193/hci0
    Dec 14 19:48:27 cdz-main kernel: Bluetooth: RFCOMM socket layer initialized
    Dec 14 19:48:27 cdz-main kernel: Bluetooth: RFCOMM TTY layer initialized
    Dec 14 19:48:27 cdz-main kernel: Bluetooth: RFCOMM ver 1.10
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/2193/hci0
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Service on path /org/bluez/2193/hci0
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Serial on path /org/bluez/2193/hci0/dev_00_16_20_92_F1_B6
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Input on path /org/bluez/2193/hci0/dev_00_16_20_92_F1_B6
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: probe failed with driver input-headset for device /org/bluez/2193/hci0/dev_00_16_20_92_F1_B6
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Headset on path /org/bluez/2193/hci0/dev_00_13_17_86_9C_A4
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Serial on path /org/bluez/2193/hci0/dev_00_13_17_86_9C_A4
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Registered interface org.bluez.Input on path /org/bluez/2193/hci0/dev_00_13_17_86_9C_A4
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Adapter /org/bluez/2193/hci0 has been enabled
    Dec 14 19:48:27 cdz-main bluetoothd[2193]: Starting security manager 0
    Update:
    I checked yum.log, and I think that one of these updates was probably responsible:
    Code:
    # cat /var/log/yum.log | grep bluez
    Dec 07 20:08:49 Updated: bluez-libs-4.19-1.fc10.i386
    Dec 07 20:10:10 Updated: bluez-alsa-4.19-1.fc10.i386
    Dec 07 20:11:07 Updated: bluez-cups-4.19-1.fc10.i386
    Dec 07 20:12:44 Updated: bluez-4.19-1.fc10.i386
    The timing of these updates is consistent with when my Bluetooth functionality broke. I can't find any other bluetooth-related updates in the log.
    Last edited by cdrom600; 15th December 2008 at 02:53 AM. Reason: added yum log info

  2. #2
    cdrom600 Guest
    Good news! It appears that bluez 4.19 was the problem.

    I was able to fix it with this command:
    Code:
    # yum update bluez bluez-alsa bluez-cups bluez-libs bluez-gnome --enablerepo=updates-testing
    This will install bluez 4.22 from the testing repo and seems to have fixed my problem. I haven't tested anything thoroughly yet, so use at your own risk.
    Last edited by cdrom600; 15th December 2008 at 04:08 AM. Reason: fixed typo

  3. #3
    Join Date
    Jun 2009
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    How do I sync my bluetooth headset to my G1 without having to type the passcode every time? I was able to connect to my headset with one click on my Blackberry, but it seems I have to jump through a series of hoops to do the same on my G1. I hate having to go into settings/wireless/bluetooth/turn on bluetooth/type passcode, every single time. Is there a faster and easier way to sync? Preferably from the G1 desktop?

Similar Threads

  1. Latest set of updates [12/7/08] Broke Gnome Update.
    By bbehnam in forum Using Fedora
    Replies: 2
    Last Post: 8th December 2008, 10:27 AM
  2. Some latest updates broke networking..
    By rasjani in forum Servers & Networking
    Replies: 4
    Last Post: 28th July 2008, 02:07 PM
  3. Today Updates Apparently Broke My GNOME Desktop
    By Boricua in forum Alpha - Beta (Fedora 9 Only)
    Replies: 27
    Last Post: 26th April 2008, 01:52 PM
  4. Latest KDE updates in FC3 broke audio
    By Fairway in forum EOL (End Of Life) Versions
    Replies: 2
    Last Post: 18th August 2005, 04:20 PM
  5. Latest ISO of FC 1: Installation / Gnome broke?
    By macron in forum Installation, Upgrades and Live Media
    Replies: 3
    Last Post: 23rd March 2004, 03:43 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •