Ubuntu
gvfs package

  1. Bug #899858
  2. Comment #8

Comment 8 for bug 899858

Revision history for this message
James M. Leddy (jm-leddy) wrote :

I'm still investigating this on a motorola RAZR V3XX. I have the same behavior as comment #0, except I don't get a connection refused. Instead I get our favorite:

Error mounting location: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

In both cases it looks like it acutally went through on an obex level, since I get in my gnome-shell output:

** Message: has_config_widget 00:1D:BE:A4:8F:49 DialupNetworking
** Message: has_config_widget 00:1D:BE:A4:8F:49 OBEXObjectPush
** Message: has_config_widget 00:1D:BE:A4:8F:49 OBEXFileTransfer
** Message: has_config_widget 00:1D:BE:A4:8F:49 Headset_-_AG
** Message: has_config_widget 00:1D:BE:A4:8F:49 HandsfreeAudioGateway
** Message: has_config_widget 00:1D:BE:A4:8F:49 DialupNetworking
** Message: has_config_widget 00:1D:BE:A4:8F:49 OBEXObjectPush
** Message: has_config_widget 00:1D:BE:A4:8F:49 OBEXFileTransfer
** Message: has_config_widget 00:1D:BE:A4:8F:49 Headset_-_AG
** Message: has_config_widget 00:1D:BE:A4:8F:49 HandsfreeAudioGateway
** Message: Default Bluetooth adapter is powered

Also I've built obexd and obex-data-server for natty on oneiric and they haven't helped. I don't believe anything in the obex stack is at fault here, but whatever is supposed to be handling the dbus messages is.