PDA

View Full Version : Bluetooth not working


atuldhawan90
26th April 2011, 08:50 PM
i have dell inspiron n4010 having widdcomm bluetooth device and i am using fedora 14. it shows bluez-daemon not working when i start kbluetooth and it shows bluetooth adapter not detected. Pls help me i am new to fedora....

bonedome
26th April 2011, 09:43 PM
Hello
first thing I'd check is the bluetooth service is running chkconfig --list bluetooth
you should see something like this bluetooth 0:off 1:off 2:off 3:off 4:off 5:off 6:offif you start fedora in the default setting (run level 5 aka graphical mode) you will want to see 5:on, usually bluetooth is enabled but sleeping and should awaken when you plug your bluetooth device in.
To enable it (you will have to be root)su -
password
chkconfig --level 5 bluetooth on
To start it manually (it's been a while but I think it's) service bluetooth start

Next thing to try is bluetooth wizard, you'll be shocked and stunned to find you need to type bluetooth-wizardand lastly when you want to check the status type bluetooth-properties
that's about my knowledge limit for bluetooth, the few times I've needed it to work it just did :D

atuldhawan90
27th April 2011, 03:12 PM

After the command chkconfig --list bluetooth
the output is
bluetooth 0:off 1:off 2:on 3:on 4:on 5:on 6:off
which is not exact as u have given

After running
chkconfig --level 5 bluetooth on
the output is nil

After running
service bluetooth start

it shows the output
Enabling Bluetooth devices:

After running
bluetooth-wizard

the output is
(bluetooth-wizard:19863): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(bluetooth-wizard:19863): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.


and after running
bluetooth-properties

it shows output
(bluetooth-properties:19936): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(bluetooth-properties:19936): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.


and if i run bluetooth manager it shows Bluez daemon is not running Bluetooth manager cannot continue

wgarider
8th May 2011, 03:39 PM
After the command chkconfig --list bluetooth
the output is
bluetooth 0:off 1:off 2:on 3:on 4:on 5:on 6:off
which is not exact as u have given

After running
chkconfig --level 5 bluetooth on
the output is nil

After running
service bluetooth start

it shows the output
Enabling Bluetooth devices:

After running
bluetooth-wizard

the output is
(bluetooth-wizard:19863): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(bluetooth-wizard:19863): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.


and after running
bluetooth-properties

it shows output
(bluetooth-properties:19936): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(bluetooth-properties:19936): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.


and if i run bluetooth manager it shows Bluez daemon is not running Bluetooth manager cannot continue

Having the exact same issue - has anyone identified a resolution?

Wahlgren
28th May 2011, 12:22 AM
Try the following and see if it helps

sudo systemctl restart bluetooth.service

gefaber
28th May 2011, 01:05 PM
"sudo systemctl restart bluetooth.service" is working for me. thanks!

but when i restart fedora i always have to type that again, not a really handy solution. any suggestions to make bluetooth working permanently? thank you in advance for your efforts!

wgarider
28th May 2011, 01:32 PM
thanks gefaber.....

this is what I get:
1014d ~]# systemctl restart bluetooth service
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused