[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2016-01-24 Thread Felipe Figueiredo
** Changed in: bluez-gnome (Baltix)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/214750

Title:
  browse device should not try to connect non-OBEX devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/214750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-10-08 Thread Mario Limonciello
This should be significantly improved in the BlueZ Gnome 1.8 package
that entered intrepid yesterday.  You won't be able to browse devices
that don't provide OBEX.

** Changed in: bluez-gnome (Ubuntu)
   Status: Confirmed = Fix Released

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-09-29 Thread inguanzo
Wopppa !!!

try this link, It rules, It worked for me at the very first try !

https://help.ubuntu.com/community/BluetoothHeadset

Hope It helps
Inguanzo

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-09-29 Thread Harri
Many thanx.

I had found this link:

http://fosswire.com/2008/01/11/a2dp-stereo-linux/

Regards

Harri

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-09-16 Thread Mike Dalrymple
I was having similar problems with a Logitech v470 bluetooth mouse.
After reading Onkar Shinde's post, I realized that I was using the UI
incorrectly.  When you right click on the Bluetooth icon there is the
Browse Device... option.   I was incorrectly reading this as Browse
FOR Devices...  To actually connect my mouse I had to do the following:

1. Right click the Bluetooth Icon
2. Select Preferences...
3. In the device's tab (mine was called fourtytwo-0, yours will be different) 
there is a pane for Bonded devices that was empty.
4. I put my mouse in discovery mode and it appeared in the bonded devices 
screen.
5. While it was in discovery mode I clicked the Add Trust button (actual name 
may be slightly different.

So now I had a trusted device but it still didn't work and when I went
to Services, it didn't show up.  It turns out that the discovery mode is
short lived and your device needs to be in discovery mode even if it is
trusted for it to appear in the services window.  So...

6. Click the Services tab.
7. Make sure the service you want is running.
8. Select the service you want to add your device to.
9. Cick the Add button.
10. Put your device (in my case my mouse) in discovery mode again and it should 
appear.

Bob's your uncle.  I hope this helps.

As far as the bug report goes, maybe a more helpful message like No
devices found that support browsing.  Unfortunately the term Browse
is incredibly overloaded in this business.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-08-06 Thread Marco Agudelo
I'm having the same problem connecting to a Logitech bluetooth headset.
The connection works with my Motorola Q phone.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-08-05 Thread DannyDei
Same problem with my laptop Samsung Q45  hardy-heron  MOTOROLA H700
detected  but I get

Couldn't display obex://[00:13:17:30:A9:E9]/. Error: Host down
Please select another viewer and try again.

 on connecting 
I have followed a very good explanation on

http://ubuntuforums.org/showthread.php?t=786640

of course I couldn't get as far as the pair the headset with a passkey
because the connection doesn't get me that far.

Any news on this BUG ?

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-08-05 Thread DannyDei
Might be helpful for others.

In a new attempt  I have selected on the BROWSE DEVICES  instead of
ALL TYPES just HEADSET and  the message got different :

Couldn't display obex://[00:13:17:30:A9:E9]/.
Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a 
reply (timeout by message bus)
Please select another viewer and try again.

but then trying again the HOST DOWN message comes back again an again.

By the way the Browse Device feature can only accept ALL CATEGORY and
with BOUNDED or TRUSTED  the device H700 disappears from the list of the
devices.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-07-28 Thread john
i only get this error if i connect 2 of the same bt devices. i have 2
m1330s each with a v470. i image from one laptop and restore to the
other. the mac addresses are different so i was able to connect the
first v470 without issue. once i connect the second v470, i got 'obex
host down'. and i think 'directory exists'. i haven't tried editing the
conf files yet which is my next step before completely reinstalling bt.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-06-24 Thread Jason Branco
i can also confirm this problem. I have Ubuntu 8.04 installed with a
Kensington bluetooth adapter and I get the same Host down error when
trying to connect to my Motorola S9 headset and Motorola A1200 phone.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-06-22 Thread Ittay Dror
Same problem here trying to browse my phone

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-05-28 Thread The_Shadow
** Also affects: bluez-gnome (Baltix)
   Importance: Undecided
   Status: New

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-05-24 Thread Kobus Prinsloo
I am also experiencing this problem. I am trying to connect Targus
Bluetooth Mouse AMB01 with Acer Travelmate 8104 running Ubuntu 8.04
Hardy Heron. I was able to connect my phone and copy files from phone to
laptop.

I had it working in 7.04 some time ago, but can't remember what I did to
get it working then. Since then I have tried all sorts of tips and
tricks and How-to's. All without success.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-05-06 Thread asif s
FYI: I am experiencing the exact same issue. Trying to connect a Logitech V470 
Wireless Bluetooth Laser Mouse on Ubuntu 8.04 Hardy Heron.   
Please help!  
I was able to get this working temporarily  by making changes to the 
/etc/default/bluetooth file, but now it has recently stopped working. No idea 
why this is happening.

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 214750] Re: browse device should not try to connect non-OBEX devices

2008-04-18 Thread Saïvann Carignan
I confirm this bug report and set the Importance to Wishlist. I changed
the description to suggest the removal of non-OBEX devices from the
Browse devices menu since the error would not show if only OBEX devices
would be there. Thanks for this bug report!

** Summary changed:

- Couldn't display obex
+ browse device should not try to connect non-OBEX devices

** Description changed:

  Binary package hint: bluez-gnome
  
  Scenario: Hardy, amd64, DVD live image of today (4/9/08). Set my
  Bluetooth headset (BTST-9300) to pairing mode. Select Browse device
  from the Bluetooth applet. It says:
  
  BTST-9300 headset
  
  Select it and click on [connect]. Then there is an error popup saying
  
  Couldn't display obex://[00:0A:94:A1:4A:42]
  
Error: host down
Please select another viewer and try again.
  
  Of course I did not select _any_ viewer, so this error message is not
  helpful to get Bluetooth working.
+ 
+ Update : This bug ask bluez-gnome to show only OBEX compatible devices
+ in browse devices. If this is not possible, Gnome/gvfs could just to
+ show a more comprehensible error message when connecting to the device
+ so the overall user can understand that the device is not browsable.

** Changed in: bluez-gnome (Ubuntu)
   Importance: Undecided = Wishlist
   Status: New = Confirmed

-- 
browse device should not try to connect non-OBEX devices
https://bugs.launchpad.net/bugs/214750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs