You are not logged in.
Pages: 1
Hey Guys,
i installed bluez and blueman, but when i start blueman, it says that the bluez daemon didn't start.
I read the bluetooth section in the handbook, but it didn't help me.
Hcitool dev gives me a hci device. The commands bluetoothd and modprobe btusb had no positive affect on blueman...
Help! Please :-)
Offline
Try starting the following:
1. Open Sakura
2. su to root
3. modprobe bluetooth
4. bluetoothd
You can tell the above is working when the plugged in bluetooth dongle's light starts flashing. Then just start blueman-manager - you may have to be root for it to work.
Offline
Hey Trixar,
doesn't work. I started blueman-manager as root in sakura (after modprobing and bluetootding), but the terminal output says something about dbuserror i guess.
I paste the output this evening (i am at work now).
Thanks anyway so far!
Offline
And you get the same error with VLC right? The dbus key wasn't generated then.
I fixed it for myself like this:
1. In sakura as root I typed [c]dbus-uuidgen[/c]
2. Copy the number that pops up (in my example it's 50151a3ba0a5d8733a1552f200001be8)
3. Still as root, type [c]echo 50151a3ba0a5d8733a1552f200001be8 > /var/lib/dbus/machine-id[/c] with the number after echo being the number you generated.
Dbus should now work like expected 
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]