Now the strange things:
blueman-applet sometimes reports "bluetooth is deactiveted", sometimes "bluetooth is activated".
sometimes i can find other bt devices using hcitool scan, sometimes not

just an hour ago I sent 1 file from my phone via opp to my home directory; it worked. afterwards i was not able to find my pc from my phone or vice versa; sending worked neither. After rebooting, i wasn't able to send 1 file again; that mostly helped in the past.

here is a tail of my syslog and in vain trying to connect after reboot.:

to be more precise, IF rebooting helps, I can perform one bluetooth file transfer action - i.e. sending one file or three files in a row (using a bluetooth file transfer manaager).

However it is not possible to send file 1, then wait until it is successfully sent and then select the next file. Only the first "action" is performed, regardless of how many files (or like) there are.

Although i can no longer send files via obex, hcitool scan still works for a while.

Hello,
it can be usefull to know on which computer you work and the exact trademark and port/chipset of the Bluetooth device. I ask for that because I have and Acer Aspire X1470 desktop who was freezing completely with some Bluetooth USB dongle, like Iogear and Cambridge.

I had to use an Asus/Atheros BT211 Bluetooth USB who use the ath3k module and linux-firmware binary to make it work properly on Linux. All my Linux system (ArchLinux/Debian/Funtoo) are stable, but with some Bluetooth devices, from the moment it try to pair with my cellular and do files transfert, I have a kernel panic.

It would be more occurate to use only one interface, I say obexftp or Blueman for test, but not both. I use a pincodes file in /var/lib/bluetooth/xx:xx:xx:xx:xx:xx/ for pairing.

As a side note, I can pull files from my Android cellular using obexftp with my Linux desktop, but I can not push files from my cellular to my desktop, because Android say the Obex Object Push profile is not available on my desktop. The sdptool say the profile is supported on my desktop. So Bluetooth is not an easy protocol to handle._________________Paul

Last edited by Logicien on Sun Jan 27, 2013 10:25 pm; edited 1 time in total

But you're right: The more people with that problem, the more likely it will be fixed^^

eminenz ... but the fix will more likely be more of the same ... broken by design. I call it broken to have a protocol stack (bluez) depend on an IPC (dbus) ...

Its furrydesktop at its very worst, entirely opaque automagic ... and when it fails there is no possibility of reaching into the lower level protocol to debug the process, thats a closed world, its enirely in the hands of redmondhat, furrydesktop, et al.

I tried re-merging the above-mentioned packages, as well as a world update, but those still didn't solve the problem, although sometimes if I re-merge obexftp then Bluetooth works for a while after I reboot.

However, it seems that, if I restart the initscript, Bluetooth works (I'm not sure yet if this works every time I restart the initscript):

Code:

/etc/init.d/bluetooth restart

EDIT (Oct. 2, 2012): I was too hasty writing that, as this morning I find that restarting the initscript does not get Bluetooth working.

Did another world update last night to pull in KDE 4.9.2 and a few other packages, but still the same problem with Bluetooth. I even re-merged PulseAudio with USE="-bluetooth" in case that was causing it, but it made no difference.

/var/log/messages contains the following every time I start-up my laptop:

Thanks for the tip, feystorm but, at least in my case, it makes no difference.

Well, a couple of days after posting that, and a few reboots later (without having updated any packages and without having installed any new packages), the Bluetooth icon in KDE became responsive to me turning Bluetooth off/on, so I tried to upload a file from my phone to my laptop just to check if Bluetooth was indeed working again. It was. Since then I have left Discoverable ticked and Bluetooth turned on in the System Tray, and, after several more reboots, it remains working. So it could be that the edit you suggested, feystorm, did work after all, albeit only after several reboots for some reason. It could be coincidence, of course, but I doubt that. I've still got my fingers crossed, as it's early days, but I just wanted to let you know that Bluetooth on my machine is now working consistently again. Thanks!_________________Clevo W230SS: amd64, OpenRC, nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64, OpenRC, xf86-video-ati, dual booting with Win 7 Pro 64-bit.
KDE on both laptops.Fitzcarraldo's blog