Couldn't display "obex://fa:ce:fe:ed:be:ef]".

Bug #190124 reported by Konrads Smelkovs
This bug report is a duplicate of:  Bug #186973: obexftp does not work in hardy + gvfs. Edit Remove
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-vfs-obexftp (Ubuntu)
Undecided
Unassigned

Bug Description

To reproduce:
1) Click on Bluetooth Manager,
2) then Browse Device,
3) then select a previously paired device (mine is SonyEricsson K750i),
4) wait
5) Observe error message:
    Couldn't display "obex://fa:ce:fe:ed:be:ef]".
    Check if the service is available.
Syslog reports:
Feb 8 09:29:27 talon NetworkManager: <debug> [1202455767.783136] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_bluetooth_hci_bluetooth_hci').
Feb 8 09:29:32 talon hcid[5282]: link_key_request (sba=00:0F:B3:17:64:78, dba=00:18:13:5E:22:E9)
Feb 8 09:29:34 talon NetworkManager: <debug> [1202455774.232348] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_bluetooth_hci_bluetooth_hci').

Before this error appeared, I was able to pair the device and transfer some files. I left the obex nautilus window linger overnight. Refresh attempts would fail and repeated connection would produce the above mentioned errors.

Revision history for this message
Yorga (yorgabr) wrote :

I confirm the bug because I have the same trouble. I'm a Motorola V3i and Ubuntu 7.10 user.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

This is due to the new gio library which replace gnome-vfs, and gio doesn't yet support obex.

Revision history for this message
Greg Yates (gyates) wrote :

Same bug with a "Microsoft Bluetooth Notebook Mouse 5000" using Hardy Alpha 4.
Will gio support obex soon?

Revision history for this message
Konrads Smelkovs (konrads-smelkovs) wrote : Re: [Bug 190124] Re: Couldn't display "obex://fa:ce:fe:ed:be:ef]".

Just a quick note - I launched kbluetooth with the gnome bluetooth
manager running and got same error, perhaps bluetooth susbsystem is to
blame?

On Feb 10, 2008 10:28 PM, Greg Yates <email address hidden> wrote:
> Same bug with a "Microsoft Bluetooth Notebook Mouse 5000" using Hardy Alpha 4.
> Will gio support obex soon?
>
>
> --
> Couldn't display "obex://fa:ce:fe:ed:be:ef]".
> https://bugs.launchpad.net/bugs/190124
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Konrads Smelkovs
Applied IT sorcery.

Revision history for this message
Paulo Fernandes (pasouza) wrote :

I had the same problem with a Nokia N95. I excluded the device from the pairede list and included it again, and now it works fine.

Revision history for this message
Nik Ahmad Faris (teslarage) wrote :

Same problem here. It kept saying 'Check if the service is available.'

Revision history for this message
Nik Ahmad Faris (teslarage) wrote :

Okay here is an update.

It seems that I can connect to my phone (SE w810i) again (after switching off the phone and switching it back on); but I cannot leave the connection idle or I will end up with the same error message.

So, its like I have to do my browsing as fast as possible or I am going to lose my connection and forced to restart my phone again.

I really am not sure where the problem is coming from.

Revision history for this message
Everthon Valadão (valadao) wrote :

Same problem here: I can send files via nautilus-sendto (obex push) but when I try to browse my Motorola A1200 via obex:// I get the error "Couldn't display obex:// Nautilus cannot handle obex".

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

@Everthon,

Please don't comment on the bug that is marked as duplicate.
Also this problem is solved long time ago with obex support in gvfs. Please install latest updates.

Revision history for this message
Rene Horn (the-rhorn) wrote :

I'm getting it with the same Microsoft mouse mentioned above, but I think that's a related bug, but not the same one.

Revision history for this message
Rene Horn (the-rhorn) wrote :

Oh, and the reason I think it's a different bug is because mice have no need for OBEX, so I'm pretty sure that GNOME is just incorrectly recognizing it as OBEX when it should just connect.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Rene Horn : your bluetooth mouse can be configured inside the preferences of the bluez-gnome applet, with few easy steps. However, the error that you get while accessing your mouse via OBEX is normal since your mouse does not support OBEX and does not contains any files, but it could be interesting that non-OBEX devices does not show in "browse devices" since they are not compatible. This request already exist, it is bug 214750.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers