PC config for Bluetooth - not able to d/l anything.
 

I have XFCE4 on Slackware64-Current using an AR3012 device. The other end for test purposes is my S7 Edge poser phone, which works flawlessly up to bluetooth-4.x.

On X, I have to restart rc.bluetooth, start (ugh!) pulseaudio, the bluetooth icon doesn't work, but when I try the command blueman-manager in a terminal, it goes. I have to pair again, argue with every detail (don't hide away - be visible; don't give me audio - give me a network connection, etc.) while the terminal throws hysterical python "DeprecationWarning" messages with dbus & polkit adding to the log spam.

Then it eventually tries to go, but apparently falls over transferring a file. I suspect it's lack of a PC download location, but I never saw any progress on the progress bar. How do I set up a Download location? My obstinate box will send a file ok, but not receive one.

There are issues with blueman 2.1, so the latest update reverted to 2.0.8.

Thanks. I'll make sure not to update to that. I'm using the April 2019 iso of Current, so I'm actually on blueman-2.0.8

Tried to pair with the phone today (had it paired with a previous distro revision, but unpaired it). Here's some errors When I try to pair them, I get this dialogue It's a very long winded way of saying "Nice try but no cigar." The Samsung has no difficulty pairing with other devices. The kernel of it seems to be 2 names for the 'network' (/org/bluez/hci0/dev_D8_C4_E9_64_0F_05, & org.bluez.Network1).

PC config for Bluetooth - not able to d/l anything.
 

Same phone, current too :
I've used bluetoothctl to pair. Once and no problem since.

Not in front of the computer right now but commands are quite clear. Just say if help is needed with it.

As I look at it, blueman-manager fails to pair them. Bluetoothctl lists them (surprisingly) as paired devices but doesn't have a file transfer option. Blueman-manager does have file transfer but fails (even as root) to receive anything. :-o.

Not really.

One describes a network interface (org.bluez.Network1), i.e. what methods and attributes should a network interface provide over DBus?

The other is your network interface as seen by bluez over DBus (/org/bluez/hci0/dev_D8_C4_E9_64_0F_05).

Thanks for exercising your mind on this.
Where I am now is that they are paired, the Samsung receives files, but the PC doesn't.

What does the command......return on your system?

It'll be an ugly XML blob. The really interesting bits will be in the UUIDs dict entry, but I'd like to see the entire output, if you will.

I opened a terminal and did the 'su -' bit to avoid permissions problems, so I'm not usually root, it's just that network stuff can be funny. Doing it as a user seemed to produce similar results.

Ugh, I missed that bit. There has to be something on the linux side that implements the DBus org.bluez.obex.Agent1 interface be able to send files to the server. (see https://git.kernel.org/pub/scm/bluet...-agent-api.txt) I don't know off the top of my head if anything in Slackware does so.

https://docs.ubuntu.com/core/en/stac.../sending-files indicates that nothing in Ubuntu Core does.

Since your phone has a service UUID of "00001105-0000-1000-8000-00805f9b34fb", it provides the Object Push Profile service. (see https://www.bluetooth.com/specificat...ice-discovery/) That's why you can send stuff to it without too many problems.

Indeed, that's the issue. May we ask the Slackware systems guys about this? In talking Bluetooth, how does a pc running slackware64 receive a file via bluetooth and where does it put it?

I find it very poor form if the bluetooth stack won't accept a file. My big drive(s) hang out on the pc, and it's handy/imperative to be able to update to them. I have been doing it via the all-seeing all-recording Google Drive, or the significantly slower mega.nz. Both automatically make zips, although you can d/l directories. That doesn't speed things up any.

Right-click your blueman-applet icon. Go to plugins. Look for TransferService and ensure it is enabled. Click the close button.
Right-click your blueman-applet icon (again). Go to "local services". Go to Transfer. Enable "Accept files from trusted devices". Set your incoming folder as you wish. Click "Apply" and "Close".

Any better?

To make a long story boring I finally gave up on blueman-manager but got through nevertheless. So despite the fact that this whole desperately below par, I got through.

My blueman-manager behaves differently to yours, Richard. I can configure nothing from the applet. The icon has X stuff only. I have the 'Adapter/Device/View/Help" menu and some 'Search' & 'Setup' buttons. I'm in XFCE.

I found the transfer service. It is turned on. Interestingly, PPPS support was off. When I went to enable it, it threw up a dependency issue: "Plugin NMDUNSupport conflicts with PPPSupport. Loading PPPSupport will unload NMDUNSupport. Proceed?" with a yes/no.

I didn't know what to do, but it doesn't work presently, so I tried it. It doesn't accept files that way either, failing silently. I get 'sending failed' on the Android, nothing on the PC.

And I kept getting asked ( as user) do I want to enable bluetooth. It really hasn't a breeze what's going on. I have Slackware64-Current, last updated April.

I won't lower the tone of the discussion by saying how I felt about this (!) so I got into bluetoothctl as root, typed help and started enabling this big time. I was paired with it, I unblocked it, tried to connect (which failed) I trusted it which was a change, and then the transfer to the PC succeeded. It appears there's also something called sdptool which maintains a database (somewhere) of known good devices, and that's one thing I haven't tried. It's significant that the man page lists a bug "Insufficient (Er, NO) Documentation."

Of course, blueman-manager held up the transfer until I clicked on the "Accept" dialog in X. I gather the issue was a lack of trust.