VLC was complaining about Pulseaudio, so I figured I'd try to fix it by uninstalling and reninstalling it (via yum). VLC now works, but Bluetooth does not. Oops.

I haven't found any useful error messages, but commands that used to work, like bluetooth-wizard and hcitool don't exist anymore.

Also, while the bluetooth menu in gnome-control-center still exists, it says "No Bluetooth adapters found", something that I hadn't seen before this broke.

My best guess is that while uninstalling Pulseaudio dependencies, something important to Bluetooth was included in there, and that wasn't put back when I reinstalled Pulseaudio.

I don't know what exactly I removed, how I would find that out, or how I would reinstall it. I've tried simple things like "yum install bluetooth" to no avail.

I'm using Fedora 17 on a Thinkpad X220 Tablet

Hi,
you should be able to see what was uninstalled by checking the yum log file. Eg as root
Evo2.

1 members found this post helpful.

Here's the log:

Jul 26 14:26:02 Erased: kde-settings-pulseaudio-4.8-25.fc17.noarch
Jul 26 14:26:02 Erased: bluedevil-1.3-1.fc17.x86_64
Jul 26 14:26:05 Erased: libbluedevil-1.9.2-1.fc17.x86_64
Jul 26 14:26:05 Erased: pulseaudio-module-x11-1.1-9.fc17.x86_64
Jul 26 14:26:06 Erased: alsa-plugins-pulseaudio-1.0.26-1.fc17.x86_64
Jul 26 14:26:08 Erased: gnome-shell-3.4.1-6.fc17.x86_64
Jul 26 14:26:09 Erased: bluez-4.99-2.fc17.x86_64
Jul 26 14:26:10 Erased: 1:gnome-bluetooth-3.4.2-2.fc17.x86_64
Jul 26 14:26:12 Erased: pulseaudio-module-bluetooth-1.1-9.fc17.x86_64
Jul 26 14:26:12 Erased: pulseaudio-1.1-9.fc17.x86_64
Jul 26 19:10:52 Installed: pulseaudio-1.1-9.fc17.x86_64

I reinstalled everything on that list; it doesn't work again yet.

hcitool, bluetooth-wizard, etc. are recognized as commands. However, running "hcitool scan" shows , the bluetooth menu in gnome-control-center still says "No Bluetooth adapters found" and running bluetooth-applet shows The bluetooth-wizard does not find any devices (and I'm pretty sure there are some in the room).

Hi,

the device may have been blocked either through software or a hardware switch. You can try to check using rfkill. Eg
Evo2.

I'm pretty sure you need bluez to communicate with the bluetooth device. Start by installing that again. You should be able to see your hci device using hcitool after that.

Hi,
Post #3 indicates that bluez was reinstalled along with the other listed packages.

Evo2.

My mistake. Sorry about that.

How might I find out what's blocking it?

Edit:

I flipped the hardware switch off and on again. Now it's:

It might be working now. I'll test it.

I turned my computer off and on again, and after some poking around (trying to disconnect and reconnect a few times), it works.

I did see a message "a problem in the bluez-4.99-2.fc17 package has been detected" or something like that, but it works anyway.