Bluetooth in Ibex has inconsistent behaviour

Bug #298430 reported by mac.ryan
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: bluetooth

RELATED BUGS - This bug is possibly related - but not the same as - #283064, #292030 and others mentioning problems in connecting devices to computer via bluetooth.

TESTING - This bug has been verified on two machines, both of them running on Ubuntu Intrepid Ibex 8.10 x64 (one with AMD and one with Intel chipsets), connecting with different BlueTooth adapters to different devices (Nokia 5300 and PalmOne Tungsten T5).

DESCRIPTION - Bluetooth adapter is properly recognised in all cases, and I can access the "preference" tab and configure various parameters. There are then a number of possibilities on different stages of process:
1) Visibility: while the computer is consistently always visible to the devices, the devices are visible to the computer only "at times".
2) Pairing: pairing never works when launched from the computer. It *sometimes* works when initiated from the device. Once the device is in the list of "known devices", pairing *never happens*, even if I remove the computer from the list of paired items on the device.
3) Sending files (via OBEX push). This has *never* happened, in either way.
4) Browsing files on the device from the computer: this has happened only once and I could not reproduce the behaviour although I tried various times. The only time I succeded, I managed to download 2 megs of pics from the telephone at about 50 K/s. After that, I closed the nautilus windows with the "browsed directory" and I could not reopen it anymore.

COMMON ERROR MESSAGES - (Translated back into English from i18n):
1) When trying to browse the files on the device: "It is impossible to show obex://[my-id-device-here]/ - Error: connexion to the device lost - Choose another viewer(?) and retry.
2) When trying to send files to the device: "An error has occurred: org.openobex.Error.Cancelled"

I am positive the device are OK as I can exchange files and data between them without problems. I am positive the BT adapters work as they work when attached to XP machines.

Revision history for this message
Rickard Nordbrandt (rickard-nordbrandt) wrote :

I have this aswell, i cant connect to my Nokia 5310, worked fine in Hardy. I can pair with the computer from the phone but not the other way around, also file transfers does not work, i have all the required obex and bluez packages installed.

"It is impossible to show obex://[my-id-device-here]/ - Error: connection to the device lost - Choose another viewer(?) and retry.

Revision history for this message
Amr Hassan (amr-hassan) wrote :

i'm affected by this bug. i use bluetooth with my nokia 6300 phone.

Details:
* Pairing:
     - i can pair successfully if i initiated the pairing from my phone.
     - if i initiate the pairing from my bluez applet, it discovers my phone but it can't connect to it. it fails.

* Sending files from my pc to my phone:
     - doesn't work from nautilus (send to) nor from the bluez applet (org.openobex.Error.ConnectionAttemptFailed). although it discovers my phone and others near me pretty well.

*Sending from my phone to my pc:
     - Fails, as it can't even find the device. my visibility is set to always visible. and i did the trick of changing it to "Hidden" and back to "Always Visible" but it didn't work.

* Using other bluetooth applications (servers):
     - Does not work. I use to use remuco-server all the time and now my phone can't find my pc to establish a connection.

This all used to work flawlessly on hardy with the same hardware. Sending stuff from my pc to my phone using the bluez applet or nautilus's "send to", sending files from my phone to my pc, and other bluetooth apps like remuco.

Revision history for this message
peddy (peddy22) wrote :

My generic BT Adapter works flawlessy, even in a *Hardy* liveCD, but not Intrepid live CD, nor a configured Intrepid installation. I have the same problems as Amr Hassan.

Revision history for this message
Pellervo Kässi (pellervo-kassi) wrote :

I'm also encoutering this bug using Lenovo R61i which has integrated bt-adapter. lsusb: Bus 001 Device 012: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller

I have also problems using the bluetooth DUN with my Nokia 6510 mobile phone. The connection stops working randomly (not depended on amount of transferred data or connection time).

Bluetooth worked in hardy.

Revision history for this message
exodus_7 (theexodius) wrote :

I've come across this problem on two of my three systems using a new Linksys bluetooth. USBBT100.

I believe that simply certain models are giving the Bluetooth features a hard time. My 8.04 system is capable of using my Linksys bluetooth just fine, however my other two 8.10 systems are having some more trouble. The free Logitech dongle that came with my mouse and keyboard, however, have been working for my 8.10 desktop without trouble, and I can even properly connect my other device through it without trouble.

By using the command "hcitools piscan" I got the Linksys to finally genuinely scan for devices, having them pop up in the "setup new device" window. However, it will neither show their proper names, and will not connect when selected. It will say it's connected, but the device itself will still be blinking as a sign of "looking for connection".

I also have to use that command every time I plug in the Linksys dongle in for it to do that much. And though 8.04 seems to work fine, it doesn't with the specific device I want to connect, so that's out of the question. When I first started it did show, and did display the proper name, but gave an error at each attempt to connect. I've done a fresh install since then, and what I've described is the current way it's behaving. This is really frustrating, and that's all I got.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.