nautilus-sendto doesn't support Obex Push file transfer since intrepid

Hello,

Could give the output of « dpkg -l | grep -i bluez » to check the list of your bluez packages.
I'll try to make a nautilus-sento package with debug statement to help to track that.

This *does* occur with the 4.x version.

On 10/13/2008, Baptiste Mille-Mathias <email address hidden> wrote:
> Hello,
>
> Could give the output of « dpkg -l | grep -i bluez » to check the list of
> your bluez packages.
> I'll try to make a nautilus-sento package with debug statement to help to
> track that.
>
> --
> nautilus-sendto doesn't support Obex Push file transfer anymore
> https://bugs.launchpad.net/bugs/282325
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from my mobile device

Mario Limonciello
<email address hidden>

Mario,
I just wanted to make sure all necessary packages are there, I'm certainly wrong, but I would feel better if I'm sure the bluez packages are the one I expect :)

MouSex,
I would like to have the result of the following command run in a terminal.

dbus-send --system --print-reply --dest=org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Device.GetProperties

Where hci0 is the name of your device on you computer and XX_XX_XX_XX_XX_XX is the hardware address of the device you're trying to send files.

thanks a lot

I forgot to explain how to get the address of your remote device, you need to run "hcitool scan", the address will be XX:XX:XX:XX:XX:XX and just replace : by _ when you run the dbus-send command.

thanks

MouSeX,

Is it possible to have some feedback on my request?

thanks

Sorry, I was out for some days. The last Updates fixed this.
But here are the requested outputs (even if they rae very late :()

marius@marius-pc:~$ dpkg -l | grep -i bluez
ii bluez 4.12-0ubuntu2 Bluetooth tools and daemons
ii bluez-alsa 4.12-0ubuntu2 Bluetooth audio support
rc bluez-audio 3.36-1ubuntu2 Bluetooth audio support
ii bluez-cups 4.12-0ubuntu2 Bluetooth printer driver for CUPS
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreamer 4.12-0ubuntu2 Bluetooth gstreamer support
rc bluez-network 3.36-1ubuntu2 Bluetooth network support
rc bluez-utils 3.36-1ubuntu2 Bluetooth tools and daemons
ii libbluetooth2 3.36-1 Library to use the BlueZ Linux Bluetooth sta
ii libbluetooth3 4.12-0ubuntu2 Library to use the BlueZ Linux Bluetooth sta

All updates, still this same issue. Anyway, I am able to send files via Bluetooth Applet.

ii bluez 4.12-0ubuntu2
ii bluez-alsa 4.12-0ubuntu2
rc bluez-audio 3.36-1ubuntu2
ii bluez-cups 4.12-0ubuntu2
ii bluez-gnome 1.8-0ubuntu1
ii bluez-gstreamer 4.12-0ubuntu2
rc bluez-network 3.36-1ubuntu2
rc bluez-utils 3.36-1ubuntu2
ii libbluetooth2 3.36-1
ii libbluetooth3 4.12-0ubuntu2
ii python-bluez 0.15-1build1

It seems nautilus-sendto is too restrictive when trying to detect phone capabilities.
Perhaps we should disable this code, and see if it works better.

I'm having the same problem.

Installed 8.04.1 and never tried to use bluetooth. Updated to 8.10 2 weeks ago.

So I don't know if it worked previously but now for sure it's not :)

Is there any way I can help by providing information?

Thanks

Jonas

Yeah, making validate_destination always return true gets nautilus-sendto working. Currently it returns false because the UUIDs array for my device doesn't contain any entries.

Another issue is that nautilus-sendto will scan for and list Bluetooth devices you're not paired with, but the check in its current form can only work on paired devices. If I pick a device I'm not paired with I get "Programming error, could not find the device in the list". But with the change to validate_destination, it works properly.

With this change, if I try to send a file to a device that can't receive files, I get a progress window which produces the error "org.openobex.Error.ConnectionAttemptFailed", which I the same thing that happens if I do that from the Bluetooth applets "send files to device" option.

Ciao, I have some truble, after upgrade today I have the following packages for bluez, Dbus, and follow result of the push request.
Thanks in advance.

root@tammy:/media/cdrom0# dpkg -l | grep -i bluez
ii bluez 4.12-0ubuntu4 Bluetooth tools and daemons
ii bluez-alsa 4.12-0ubuntu4 Bluetooth audio support
ii bluez-audio 3.36-1ubuntu2 Bluetooth audio support
ii bluez-btsco 1:0.50-0ubuntu3 Bluez Bluetooth SCO tool
ii bluez-cups 4.12-0ubuntu4 Bluetooth printer driver for CUPS
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreamer 4.12-0ubuntu4 Bluetooth gstreamer support
ii bluez-input 3.36-1ubuntu2 Bluetooth input support
ii bluez-network 3.36-1ubuntu2 Bluetooth network support
ii bluez-serial 3.36-1ubuntu2 Bluetooth serial support
ii bluez-utils 4.12-0ubuntu4 Transitional package
ii libbluetooth-dev 4.12-0ubuntu4 Development files for using the BlueZ Linux
ii libbluetooth2 3.36-1 Library to use the BlueZ Linux Bluetooth sta
ii libbluetooth3 4.12-0ubuntu4 Library to use the BlueZ Linux Bluetooth sta

root@tammy:/media/cdrom0# dpkg -l | grep -i Dbus
ii dbus 1.2.4-0ubuntu1 simple interprocess messaging system
ii dbus-x11 1.2.4-0ubuntu1 simple interprocess messaging system (X11 de
ii libcryptui0 2.24.1-0ubuntu1 the UI library for DBUS functions exported b
ii libdbus-1-3 1.2.4-0ubuntu1 simple interprocess messaging system
ii libdbus-1-dev 1.2.4-0ubuntu1 simple interprocess messaging system (develo
ii libdbus-1-qt3 0.9-0ubuntu1 dbus bindings for Qt 3 (backport of the Qt 4
ii libdbus-1-qt3-dev 0.9-0ubuntu1 dbus bindings for Qt 3 (backport of the Qt 4
ii libdbus-glib-1-2 0.76-1 simple interprocess messaging system (GLib-b
ii libdbus-qt-1-1c2 0.62.git.20060814-2build1 simple interprocess messaging system (Qt-bas
ii libndesk-dbus-glib1.0-cil 0.4.1-1 ...

Any update on this issue? We can no longer use bluetooth to transfer files

I confirm this problem on Nokia 6230 and Ubuntu 8.10 with all updates installed.
On Ubuntu 8.04.1 i have no problems.

Kernel: Linux morya4ok-desktop 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux

OS: Ubuntu 8.10

 dpkg -l | grep bluez:

ii bluez 4.12-0ubuntu5 Bluetooth tools and daemons
ii bluez-alsa 4.12-0ubuntu5 Bluetooth audio support
ii bluez-cups 4.12-0ubuntu5 Bluetooth printer driver for CUPS
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreamer 4.12-0ubuntu5 Bluetooth gstreamer support
ii bluez-utils 4.12-0ubuntu5 Transitional package

I can reproduce this issue on UL 8.10 + latest updates on a Dell Laptop with Dell BT365(). I get the "Obex Push file transfer unsupported" message when I try to send a file using the Right click on file on say the Desktop--> Send To-->Send as:Bluetooth (OBEX Push)-->Send

When I try to send the file using the alternate GUI route which is:
Right Click Bluetooth icon-->Send files to device--><pick file>-->Select Device-->Connect, I get the following error message in the File Transfer window:
Eror Occurred->org.openobex.Error.ConnectionAttemptFailed

Please ignore the second paragraph of my previous comment as the file transfer from the alternate GUI route *does* in fact work. I was enlightened of a "feature" in the Blackberry, where you have to explicitly turn "Receive using Bluetooth" ON every single time, you want to do a FT.

The issue described in the first paragraph is still reproducible and valid. Can I provide any additional information such as lspci etc?

Same here. When I click "Send", it doesn't even check, if the device is available. But it works fine using Bluetooth Applet.

It worked fine on Ubuntu 8.04.

Ubuntu 8.10 with all updates.

For me same identical behaviour of Roffik: "send" doesn't check anything and says "Obex Push file transfer unsupported", while both obexftp and Bluetooth Applet work fine.

Ubuntu 8.10 updated.

leo@dharmabook:~$ dpkg -l | grep -i bluez
ii bluez 4.12-0ubuntu5 Bluetooth tools and daemons
ii bluez-alsa 4.12-0ubuntu5 Bluetooth audio support
ii bluez-audio 3.36-1ubuntu2 Bluetooth audio support
ii bluez-cups 4.12-0ubuntu5 Bluetooth printer driver for CUPS
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreamer 4.12-0ubuntu5 Bluetooth gstreamer support
ii bluez-input 3.36-1ubuntu2 Bluetooth input support
ii bluez-network 3.36-1ubuntu2 Bluetooth network support
ii bluez-serial 3.36-1ubuntu2 Bluetooth serial support
ii libbluetooth2 3.36-1 Library to use the BlueZ Linux Bluetooth sta
ii libbluetooth3 4.12-0ubuntu5 Library to use the BlueZ Linux Bluetooth sta

Hello,

to all reporters, could you install the nautilus-sendto package (only) available in my ppa (http://ppa.launchpad.net/bmillemathias/ubuntu/pool/main/n/nautilus-sendto/), kill nautilus and try again to send again a file to your remote device?

Report here if it fix your problem or not.

Thanks a lot for your help.

Nope, it doesn't work, the window closes itself (crashes?) after clicking "Send".

Should I provide more information?

Same for me: the window closes itself after clicking "Send".
My problem:
- connection to a Palm Tungsten E2 not OK in Ibex, but always OK with hardy
- see device properties in the attachment
- Sometimes I can connect to internet with ppp connection (~ once every 10 trials)
- never send to Palm with original nautilus: I get "Obex push file transfer unsupported"
- never send to Palm with bluetooth applet: I get "org.openobex.Error.ConnectionAttemptFailed"
- same problem with Fedora 10!

@roffik, to kno what happen you call launch nautilus-sendto ~/myfile.txt in a console to see what happen whit my package.

Here you are:

$ nautilus-sendto Xmodmap
Init pidgin plugin
Init gajim plugin
Init thunderbird plugin
Init sylpheed-claws plugin
Init evolution plugin
//And now, the window appears, I choose my device and click send:
Segmentation fault
//The end.

it would be nice to have some news from maintainer/packagers about this issue. Is there anybody fixing this?

there is nobody actively working on this ubuntu component, could somebody having the issue send the bug to bugzilla.gnome.org where the people writting the code will read it?

I've created a bug at gnome.org, please confirm it there..

http://bugzilla.gnome.org/show_bug.cgi?id=567485

I also have the problem but I tried with another one BT pen, and it worked... How could be possible?
Working Pen is Trust brand, the not working pen is unknown brand with ISSC chipset.
ISSC pen works under other OS, and also works under 8.0.4.1

Thank you

My pen (not working) is Energy Sistem Linnker 1550T.

Internal bluetooth in HP 6710b is not working with desktop menu in interpid. In hardy everything was fine.

Hello,
My not working (since Intrepid) dongle is, according to lsusb:
Bus 001 Device 006: ID 1131:1001 Integrated System Solution Corp. KY-BT100
Bluetooth Adapter.

I hope this helps.

I have the same problem and the same device than jorek!
luc@icone:~$ lsusb
Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

I have
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
and the same problem described here with nautilus send to.
But differently from the bug reported in gnome's bugzilla I can send file through bluetooth icon in the notification area.

I'm sorry. I can send by the notification area icon but not from nautilus.

$ lsusb
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
I cannot send through bluetooth icon
I cannot send with nautilus sendTo

Oh yeah! With version 1.1.1 of nautilus-sendto package I am now able to send files with right mouse button!

Check it yourself (build for jaunty i386, but works in intrepid):
https://launchpad.net/ubuntu/jaunty/i386/nautilus-sendto/1.1.1-0ubuntu1

If you get an error like "Can't find the device on the list" (more or less), remember that you have to add your device to the trusted list, for example by clicking left mouse button on bluetooth icon and "Setup new device...".

No way. I have the same problema with 1.1.1.

So I think I've got some more information about this.

1) There are two types of SDP records for OBEX, 0x1105 and 0x1106. If your phone supports 0x1106, then version 1.1.1 might just work for you. If it supports 0x1105 you'll probably need another patch to add support for it.

2) Not all phones always broadcast these SDP records. My Blackberry for example only shows my 0x1105 when I am in "File Receiving Mode". It has no way to always be in File Receiving mode.

I think upstream will need to add support to requery the SDP records to solve (2), and then also add a patch to support the other type of OBEX record to solve (1).

But the code, as it exists right now, is just plain silly. All devices are shown in the drop-down list, regardless of whether they can receive OBEX transfers. It's only after choosing one and clicking send that the program checks, and at that point it might as well just try sending the file.

In a future version, SDP should be used to filter the drop-down list to have only appropriate devices. For Intrepid, we can just skip the check that occurs immediately before sending the file.

I solved adding this repo:
# deb http://ppa.launchpad.net/ubuntu-kennynet/ppa/ubuntu intrepid main
# deb-src http://ppa.launchpad.net/ubuntu-kennynet/ppa/ubuntu intrepid main

- Update obex-data-server
- Restart bluetooth-applet and the service init.d/bluetooth
- *Important* Delete previously paired devices and re-pair it using the applet
- Done

Yes, it is solved there. Thanks.

petter@nattbrygga:/tmp$ sudo apt-get install obex-data-server=0.4.3~ppa1
...
The following packages have unmet dependencies:
  obex-data-server: Depends: libmagick10 but it is not installable

petter@nattbrygga:/tmp$ apt-cache policy libmagick10
libmagick10:
  Installed: (none)
  Candidate: (none)
  Version table:
     7:6.3.7.9.dfsg1-2ubuntu4 0
        100 /var/lib/dpkg/status

@ Amit Bhutani

I can also reproduce this issue on ubuntu/jaunty alpha 9.04 on a Dell Laptop 1720 to ubuntu 8.04 on a Dell D800.
I get also the "Obex Push file transfer unsupported" message when I try to send a file (compressed or no) using the Right click on file on say the Desktop--> Send To-->Send as:Bluetooth (OBEX Push)-->Send

When I try to send the file using the alternate GUI route which is:
Right Click Bluetooth icon-->Send files to device--><pick file>-->Select Device-->Connect:
the transfert is well performed ! :)

on ubuntu/jaunty:
ii bluez 4.29-0ubuntu1
ii bluez-compat 4.29-0ubuntu1
ii bluez-gstreamer 4.29-0ubuntu1
ii bluez-utils 4.29-0ubuntu1
ii libbluetooth3 4.29-0ubuntu1

ii bluez-gnome 1.8-0ubuntu2

nautilus 1:2.25.4-0ubuntu1
nautilus-sendto 1.1.1-0ubuntu1

Can't send files using Dell XPS M1210 to a Windows Mobile 6.1 phone, same problem "Obex Push file transfer unsupported". Has "paired" the phone and bt-device before I tryed to make the transfer.

One issue I found before was the short time out between I could enter the PIN in the phone and the time out in the computer. I had to try several times before I even could make them a pair.

There is something very wrong here....

How could I assist with more usefull information?

Regards rancor

Hi guys:

I've submitted a few patches upstream that got accepted to 1.1.2 that should hopefully fix this problem. Can people who are running into it try running version 1.1.2-0ubuntu1 on Ubuntu Jaunty?

Thanks,

Files are sent properly to a Nokia E60 mobile phone. Ability to compress on-the-fly works too.

Thanks for the patches!

Mario from Dell found and submitted a patch upstream.

I had this error too, fixed following the steps:

Download and install Nautilus-Sendto 1.1.1 DEB in:
https://launchpad.net/ubuntu/jaunty/i386/nautilus-sendto/1.1.1-0ubuntu1

Run the commands:

$ sudo hciconfig hci0 reset
$ sudo /etc/init.d/bluetooth restart

That's it, it should fix it, try to right click on a file and Send To.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530791

Today I've come across this issue once again on Jaunty (and SonyEricsson mobile phone). I've 2 users, and none of them were able to send files via 'Send to...'. After re-pairing the device for one user I still couldn't send files but surprisingly I could browse the phone and exchange files from there!

Later I dug on another bug and changed some settings for the other user in gconf-editor. I believe I changed '/desktop/gnome/file_sharing/enabled' and some similar settings (I just don't remember). And you know what - I can send files now!

So the problem may lurk not in Bluetooth, but inside Nautilus GConf settings, or am I wrong?

Oh and one more question about GConf settings: does '/desktop/gnome/file_sharing/bluetooth_obexpush_enabled' mean anything if '/desktop/gnome/file_sharing/enabled' is set to False? Or maybe it's just that the Bluetooth manager sets it's own variable assuming that all other settings (which override the bluetooth ones) be done by someone else?

I have Ubuntu 9.04 jaunty... and still have the same problem. I have tried some of the things above, but without success... can anybody help me?

I'm having same issue in Karmic, can't send files to phone, and I can't send files from my phone, so it is still broken despite the false claims of "great and reliable bluetooth support in Karmic & Gnome"

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1305946