Bluetooth sync stopped working in ubuntu 11.10

Bug #924223 reported by khul
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
syncevolution (Ubuntu)
Fix Released
Undecided
Micah Gersten

Bug Description

Syncing with my nokia N9 via bluetooth worked out of the box when I got it a few months ago. I then upgraded from ubuntu 11.04 to 11.10, and now it doesn't any more. The "Sync" dialogue box is much the same, but when I try to sync I get a red box saying it can't connect to the server. Seems this might be a bluetooth bug. I remove the phone and re-paired it, but the sync still fails and when I try to browse files in the bluetooth menu the bluetooth icon disappears.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: syncevolution (not installed)
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Jan 31 11:40:00 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: syncevolution
UpgradeStatus: Upgraded to oneiric on 2012-01-19 (11 days ago)

Revision history for this message
khul (klas-physto) wrote :

In the bluetooth control window ("gnome-control-center bluetooth") I can select my phone. It's listed as paired, but the "Connection" switch is off and locked in that position. I don't understand what that means, maybe nothing. If I click "Browse Files..." nothing seems to happen. If I click "Sync" I get the red box. I tried re-installing gnome-bluetotth and bluez, but that didn't change anything. The phone certainly considers itself paired with the laptop.

Revision history for this message
khul (klas-physto) wrote :

Tried changing to the latest syncevolution release (1.2.2, was 1.1.1 before). Still same problem. Running it in the terminal I get

$ syncevolution Khul
[INFO] addressbook: inactive
[INFO] memo: inactive
[ERROR] connect failed with error code 111
[ERROR] ObexTransport: Transport Exception in sdp_callback_impl
[ERROR] ObexTransport: connect request failed with error
[ERROR] connect failed with error code 111
[ERROR] ObexTransport: Transport Exception in sdp_callback_impl
[ERROR] ObexTransport: connect request failed with error
[ERROR] ObexTransprotAgent: Underlying transport error
[INFO] creating complete data backup after sync (enabled with dumpData and needed for printChanges)

Synchronization failed, see /home/klas/.cache/syncevolution/khul-2012-01-31-16-35/syncevolution-log.html for details.

Revision history for this message
Patrick Ohly (patrick-ohly) wrote :

Similar problems were observed with the N900. SyncEvolution is tracking that problem here:
https://bugs.meego.com/show_bug.cgi?id=4835

Keith Packard had the same issue with N900 + libsyncml (http://keithp.com/blogs/calypso/).
Seems to be a problem at the OBEX/Bluetooth layer, either on the host or device side.

Revision history for this message
khul (klas-physto) wrote :

Thanks for the links!

I had an N900 which I lost after about two years. First it worked with bluetooth, then it stopped working and I had to set up a syncML server. I was pleased when my new N9 "just worked" with bluetooth. It continued working after the firmware update in the phone. So it seems this might be a regression in ubuntu 10.11. Maybe I'll have to go back to syncML.

Revision history for this message
Micah Gersten (micahg) wrote :

This should be fixed with 1.2.2 which I'm about to sync

Changed in syncevolution (Ubuntu):
assignee: nobody → Micah Gersten (micahg)
status: New → In Progress
status: In Progress → Fix Released
Revision history for this message
Micah Gersten (micahg) wrote :

This bug was fixed in the package syncevolution - 1.2.2-1

---------------
syncevolution (1.2.2-1) unstable; urgency=medium

  * New upstream version
  * Fix upgrade from squeeze (Closes: #657001)
  * Re-add sync-ui icon file (Closes: #658519)

 -- Tino Keitel <email address hidden> Mon, 06 Feb 2012 19:33:08 +0100

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.