Bluez daemon not running, unable to use bluetooth dongle!

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

Bluez daemon not running, unable to use bluetooth dongle!

Postby eor2004 » Mon Jan 06, 2014 22:23

Hi guys, I'm trying to use my usb bluetooth dongle using Blueman or Mate bluetooth, but everytime I get an error message telling me that "Connection to BlueZ failed, Bluez daemon is not running, blueman-manager cannot continue.
This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.
"

If I do an lsusb command, the bluetooth dongle shows up, so it is beign recognized by the kernel.
If I plug my usb bluetooth dongle, the bluetooth icon shows up in the task bar, but can't turn on the bluetooth adapter.

I'm using Sabayon MATE 64bit fully updated, kernel 3.10
Anyone knows how can I enable or make the Bluez daemon run???

Because an image or video is worth more than a thousand words, here's a link to download a video about the issue or bug, made using "recordmydesktop":
https://www.dropbox.com/s/htdi469mlfi7y ... daemon.mkv
Sabayon Linux MATE 64-bit
Gigabyte G41M-ES2L-->2gb ram
Intel Pentium Dual Core 2.60ghz-->E5300
WD-6400AAKS-Caviar-SE16-640gb-->XFS filesystem
User avatar
eor2004
Simple Hen
 
Posts: 85
Joined: Thu Jul 12, 2012 15:46
Location: Puerto Rico

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby linuxfluesterer » Tue Jan 07, 2014 9:29

Hallo.
As I have reported earlier in this forum, see here:
https://forum.sabayon.org/viewtopic.php?f=56&t=31072&p=168259&hilit=bluetooth+not#p168259
I've had the same problem in KDE 4.11.3 and now in KDE 4.12. It seems not to be a topic of Sabayon (at least of KDE).
Anyway, I can (exactly, I must) activate my bluetooth with a command in root console:
Code: Select all
hcitool hci0 up
then I can scan my environment by a command also:
Code: Select all
[email protected]:hcitool scan
Scanning ...
        00:01:E3:B6:53:DE       S68H
        C8:12:79:D3:96:B1       Galaxy Note 3
        F0:08:F1:F7:D8:92       Wave II
        00:1E:10:87:73:E2       Mama Handy .M

Then I receive bluetooth devices in my environment. But in KDE there is still a message in bluetooth adapters window:
"No Bluetooth adapters have been found. No adapters found. Please connect one."
The problem seems to be bluez5, which is assumed by Fabio (lxnay) in my thread.
We have no choice. We must wait, until this bluez5 is finished to work. And it seems, not only KDE is affected, other DEs, so yours (Mate?) also.
Do we have a free wish for 2014? Hope so, lol.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 703
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby Cb7 » Tue Jan 07, 2014 9:46

Are you familiar with managing services using systemd (I assume that you're using it)?
If not, there's wiki article about it: HOWTO: systemd
In your case it would be:
Code: Select all
systemctl enable bluetooth && systemctl start bluetooth
Why, and how to add "[Solved]" to your post. Please read. ← credits to Fitzcarraldo

Kind regards
~Zetok Zalbavar
Cb7
Growing Hen
 
Posts: 104
Joined: Sun Apr 07, 2013 7:13

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby linuxfluesterer » Tue Jan 07, 2014 10:17

Thank you for give the hint. As you can see here:
Code: Select all
[email protected]:systemctl --show|grep blue
sys-devi...ooth-hci0.device loaded active plugged   /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0/bluetooth/hci0
sys-subs...ices-hci0.device loaded active plugged   /sys/subsystem/bluetooth/devices/hci0
bluetooth.target            loaded active active    Bluetooth

bluetooth seems to be active. Anyway, I've activated again with:
Code: Select all
systemctl start bluetooth

So, now I can see my adapter. I can find my device (Galaxy Note 3) I have connected with, confirming the pin number.
But I can still NOT send any file from my phone to my notebook neither from notebook to my phone. My telephone says:
"File not sent". I can repeat this several times, no success.
This is my dmesg output start from starting Bluetooth to last action:
Code: Select all
[    3.990328] Bluetooth: Core ver 2.16                                                                                               
[    3.990341] NET: Registered protocol family 31                                                                                     
[    3.990343] Bluetooth: HCI device and connection manager initialized                                                               
[    3.990350] Bluetooth: HCI socket layer initialized                                                                               
[    3.990353] Bluetooth: L2CAP socket layer initialized                                                                             
[    3.990358] Bluetooth: SCO socket layer initialized                                                                               
[    3.993131] usbcore: registered new interface driver btusb                                                                         
[    3.993589] uvcvideo: Found UVC 1.00 device HD WebCam (04f2:b374)                                                                 
[    4.002955] input: HD WebCam as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0/input/input13                           
[    4.003183] usbcore: registered new interface driver uvcvideo                                                                     
[    4.003199] USB Video Class driver (1.1.1)                                                                                         
[    4.005513] acer_wmi: Acer Laptop ACPI-WMI Extras                                                                                 
[    4.005526] acer_wmi: Function bitmap for Communication Button: 0x801                                                             
[    4.005627] acer_wmi: Brightness must be controlled by acpi video driver                                                           
[    4.006456] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x12                                                                   
[    4.007507] iTCO_vendor_support: vendor-support=0                                                                                 
[    4.013309] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10                                                                       
[    4.013340] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460)                                                 
[    4.013434] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)                                                                   
[    4.014908] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x12                                                                   
[    4.021130] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x12                                                                   
[    4.021195] acer_wmi: Enabling Launch Manager failed: 0xe2 - 0x0                                                                   
[    4.021317] input: Acer WMI hotkeys as /devices/virtual/input/input14                                                             
[    4.021608] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba                                   
[    4.022200] input: Acer BMA150 accelerometer as /devices/virtual/input/input15                                                     
[    4.039840] cfg80211: World regulatory domain updated:                                                                             
[    4.039843] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)                                         
[    4.039844] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                               
[    4.039846] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                               
[    4.039847] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)                                               
[    4.039848] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                               
[    4.039849] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)                                               
[    4.047931] usbcore: registered new interface driver ath3k                                                                         
[    4.119832] usb 3-1.1: USB disconnect, device number 3                                                                             
[    4.276976] fbcon: inteldrmfb (fb0) is primary device                                                                             
[    4.277001] Console: switching to colour frame buffer device 170x48
[    4.277008] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    4.277010] i915 0000:00:02.0: registered panic notifier
[    4.296634] usb 3-1.1: new full-speed USB device number 5 using ehci-pci
[    4.384031] usb 3-1.1: string descriptor 0 read error: -22
[    4.384043] usb 3-1.1: New USB device found, idVendor=0489, idProduct=e04e
[    4.384047] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.577982] acpi device:3e: registered as cooling_device5
[    4.578223] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    4.578290] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input16
[    4.578414] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[    4.619234] systemd[1]: lm_sensors.service failed to run 'start' task: No such file or directory
[    4.619318] systemd[1]: Unit lm_sensors.service entered failed state.
[    5.239282] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x550f01)
[    5.263410] psmouse serio1: elantech: Synaptics capabilities query result 0x79, 0x18, 0x0b.
[    5.394690] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input9
[    5.446781] tg3 0000:02:00.0: irq 45 for MSI/MSI-X
[    5.446789] tg3 0000:02:00.0: irq 46 for MSI/MSI-X
[    5.446795] tg3 0000:02:00.0: irq 47 for MSI/MSI-X
[    5.446800] tg3 0000:02:00.0: irq 48 for MSI/MSI-X
[    5.446805] tg3 0000:02:00.0: irq 49 for MSI/MSI-X
[    5.730643] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[    6.013164] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.022629] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   25.547655] wlan0: authenticate with 00:04:0e:ea:0e:e7
[   25.559627] wlan0: send auth to 00:04:0e:ea:0e:e7 (try 1/3)
[   25.561847] wlan0: authenticated
[   25.562846] wlan0: associate with 00:04:0e:ea:0e:e7 (try 1/3)
[   25.570606] wlan0: RX AssocResp from 00:04:0e:ea:0e:e7 (capab=0x411 status=0 aid=1)
[   25.570836] wlan0: associated
[   25.570868] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 2953.881654] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2953.881658] Bluetooth: BNEP filters: protocol multicast
[ 2953.881667] Bluetooth: BNEP socket layer initialized

There is still something not working properly as I'm doing before with KDE 4.11.2.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 703
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby Cb7 » Tue Jan 07, 2014 10:27

Um, I've written my post just before your linuxfluesterer, and send it after you've send yours, so it was rather addressed to eor2004, since he mentioned that bluez daemon doesn't work. What I wrote doesn't address issues that may be present because of API breakage in bluez 5.
Last edited by Cb7 on Tue Jan 07, 2014 14:07, edited 1 time in total.
Why, and how to add "[Solved]" to your post. Please read. ← credits to Fitzcarraldo

Kind regards
~Zetok Zalbavar
Cb7
Growing Hen
 
Posts: 104
Joined: Sun Apr 07, 2013 7:13

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby linuxfluesterer » Tue Jan 07, 2014 11:38

Oh, sorry, I've misunderstood...
Anyway... do you have a bluetooth run with your DE (KDE or else)? I am rather interested in.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 703
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby Cb7 » Tue Jan 07, 2014 14:14

I don't have currently anything to check bluetooth on, but if bluez's API was broken, then until things get updated to work with newer version, they won't work. From what I know, bluez had to be bumped because of Gnome 3.10, which with bluez 5 works (or rather it should). DE that don't work with it correctly simply are lagging behind, and you can't do much with it except waiting.

I can write about workaround (if you want) for sending files, which would at least solve some of your problems, linuxfluesterer, and workaround would be safer for sending files (encryption; yea bluetooth has some of it, but I personally don't believe that it works as it should).

You could use sftp, in both directions, though accessing android device from computer would be much harder to do… Only problem with that would be permissions (in some cases), but if it's only for backups, then it's not a problem at all.
Why, and how to add "[Solved]" to your post. Please read. ← credits to Fitzcarraldo

Kind regards
~Zetok Zalbavar
Cb7
Growing Hen
 
Posts: 104
Joined: Sun Apr 07, 2013 7:13

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby linuxfluesterer » Wed Jan 08, 2014 9:24

Thank you very much indeed for your offer, cb7.
Exactly, I am most interested in understanding the procedures, assuming, the procedure is working normally and without bugs or errors. Until KDE 4.11.2 (or better, bluez4), I was able by myself to activate bluetooth running and connecting with my devices.
But with bluez5 everything has changed and my problem is, I do not understand, what exactly is the problem.
I don't know, where to find a bluetooth log file, which I can read.
I don't know, is there someone, who can really work with bluetooth without any workaround. If so, what must be done to achieve it? And, to be honest, I see no reason, why bluez5 must have come with all that problems though bluez4 has been working fine with KDE and others.
But I appreciate your offer, though this is not, what I'm looking for. I need an answer, why the normal way to use bluetooth known from KDE 4.11.2 is not working here since KDE 4.11.3 (KDE 4.12 also).
I'm willing to learn about solutions, but I prefer the general solution to handle a problem for Sabayon KDE. I may change a file, ok, initialize a routine for a single time (as there is, e.g. systemctl enable bluetooth) but this is a standard way.
In my Google searches I didn't really find an answer to my questions, but I'm rather sure, that bluez5 (or is it bluedevil?) is still the problem.
Btw. I just want to use bluetooth connection to transfer photos from my phone or my girlfriend's phone to my notebook, because we do not always have a cable. And I love, when the hardware deals work fine with my Linux, here Sabayon.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 703
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby Cb7 » Wed Jan 08, 2014 14:37

As I said before, and also Fabio did, but in simpler words:
Things that are compatible with bluez 4 aren't compatible with bluez 5. That is because of changes that were made in bluez. I don't know why they were made, but usually that kind of serious changes aren't made without a really good reason. So there was a reason, to break compatibility with applications that don't support newer version of bluez. And projects, that are dependent on bluez for something should have updated things for bluez 5.
Many projects (including KDE) haven't released compatible with bluez 5 software, and thus it doesn't want to work with it.

So why there was a need to switch to bluez 5 on Sabayon, when many applications are not prepared for it yet?

1st thing is that it had to be done, since Gnome 3.10 required bluez 5 to work.
2nd thing is that it had to be done someday, and applications would be broken anyway, but perhaps their number would be lesser. And further in time without updating bluez, more applications wouldn't be compatible with bluez 4, and would be compatible with bluez 5, which also wouldn't be a good thing.

Until software won't be updated to version that works with bluez 5, it won't work.

So what, as a user you could do?
… not much. At least as a KDE user. You can wait for fix in updates.
(I don't advise that: you could bug about it devs of projects that don't work with bluez 5)

That's unfortunately one of bad sides of rolling distro, when you have something updated to work with one thing, and stop working with others (until some next update).

Bluez 5 should work with DEs that were updated to make it compatible with it. I guess that Gnome should work with bluez 5, since it itself was a reason to pull in bluez 5.
Why, and how to add "[Solved]" to your post. Please read. ← credits to Fitzcarraldo

Kind regards
~Zetok Zalbavar
Cb7
Growing Hen
 
Posts: 104
Joined: Sun Apr 07, 2013 7:13

Re: Bluez daemon not running, unable to use bluetooth dongle

Postby patkoscsaba » Tue Jan 21, 2014 17:03

My bluetooth daemon behaves strange also. Most of the time it segfaults after a device connects, but at least the connection remains active for that device.

I wrote some workarounds I managed to figure out, see the link below to my blog. I prefer to just link it here to avoid copy/pasting long stories. Also see the link in my post to the pairing workaround.

http://patkoscsaba.blogspot.ro/2013/12/programmers-diary-bluetooth-hell.html

These ideas are far from a solution and may not apply to your exact problem, but they work for my until an official update fixes the problem.
patkoscsaba
Baby Hen
 
Posts: 4
Joined: Fri Jan 20, 2012 14:07
Location: Romania


Return to Hardware

Who is online

Users browsing this forum: No registered users and 2 guests