Slackware current x86_64
blueman 1.22

I have two bluetooth dongles. Blueman sees them, and I can use either of them to pair with my phones, both Samsung t249, just fine.

It will not, however, mount it. I get this:

Run (/usr/lib64/python2.6/site-packages/blueman/main/PluginManager.py:216)
Function on_request_menu_items on Services Failed
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/blueman/main/PluginManager.py", line 220, in Run
ret = getattr(inst, function)(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/blueman/plugins/manager/Services.py", line 48, in on_request_menu_items
ports_list = rfcomm_list()
File "_blueman.pyx", line 174, in _blueman.rfcomm_list
Exception: ERR_SOCKET_FAILED


I really don't know what it is trying to tell me. Any ideas what this means, and how I can get it to mount these ?

I have an almost default Slackware32 13.37 installation here, and I cannot reproduce your situation. I recommend looking in Gentoo and Arch Wikis for hints. As you are running -current, I assume that you are an advanced user.

To start with, do you have all the obex* packages?

I've been living with -current for quite a while now. Yeah, it's a bit on the edge and a touch risky, but it's never let me down (yet). A lot of my work is done on remote systems or in virtual machines, so the risk of being bit is slightly less. So long as VirtualBox and citric clients work, I'm happy. And if worse comes to worse I can reload a default 13.37 install in about a half hour (beats the heck out of taking half a day or more to reinstall Windows, find the missing install disk for office, where is that dang driver, etc., etc. but that is another story.....).

I have all three of those obex packages:

root@ook:~# ls -l /var/log/packages/obex*
-rw-r--r-- 1 root root 1258 Apr 11 11:46 /var/log/packages/obex-data-server-0.4.6-x86_64-1
-rw-r--r-- 1 root root 895 Apr 11 11:46 /var/log/packages/obexfs-0.12-x86_64-1
-rw-r--r-- 1 root root 2470 Apr 11 11:46 /var/log/packages/obexftp-0.23-x86_64-6

If I get a chance I might put a stock 13.37 install onto a spare partition and see if it works - it is very possible something in -current is broken.

Just to ensure that I am not misleading you; I do not own a Samsung t249, my smartphone is an Android HTC Explorer so I cannot be sure if it is due to your Linux System or your device.

Before reverting to -stable, maybe you should look here: http://www.gentoo.org/doc/en/bluetooth-guide.xml as there are many tests you can try.

I assume you are sure the t249 has full Bluetooth FTP support, and not just OBEX PUSH?

FWIW, I reverted back to 13.37, and now bluetooth works as expected. I don't think it's the kernel, as I'm currently using 3.3.7 and have used others, and bluetooth still works fine. My guess is that something in the -current code base is not compatible with ... something ... somewhere ... and this is keeping bluetooth from working. I can't really test further until ATI comes out with video drivers that work with the -current x server, because as I understand it recent changes are not compatible with current ATI drivers.. (a new shiny nVidia card is looking better and better)....ATI just released a new driver set but their release notes is nothing more then a generic installation guide...but I digress...

13.37: bluetooth works fine

-current: I've not been able to get bluetooth to work for the last six months of so of -current

Are you using KDE?
If so, try disabling Bluedevil.

What's with the "python2.6" in the mentioned debugging output, and where did you get "blueman 1.22"?