Bug 459388

Summary: Bluetooth Phone Sync fails on "At least one objenit hat problems while connecting"
Product: [Fedora] Fedora Reporter: A. Folger <afolger>
Component: libopensyncAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-24 12:12:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description A. Folger 2008-08-18 11:26:44 UTC
Description of problem:
In Fedora 8, I used to sync my phone with KDEPIM perfectly. However, since the upgrade to FC9, I cannot sync - the "leg" that connects to the phone fails with the error message "At least one objenit hat problems while connecting".

Version-Release number of selected component (if applicable):
libopensync-0.36-2.fc9.x86_64
libopensync-plugin-kdepim-0.36-1.fc9.x86_64
libopensync-plugin-file-0.36-1.fc9.x86_64
libopensync-plugin-irmc-0.36-1.fc9.x86_64
kdepim-3.5.9-10.fc9.x86_64
kdepim-libs-3.5.9-10.fc9.x86_64
kdepimlibs-4.0.5-1.fc9.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Start your favorite syncing application (for me: Kitchensync)
2. Make sure it is set up properly (I checked with the bluez-tools, esp. 'hcitool scan' and 'sdptool browse <mac addr>')
3.
  
Actual results:
Failure to syncronize and appearance of error message "At least one objenit hat problems while connecting"

Expected results:
Syncronization with addressbook, as it worked in FC8.

Additional info:
Phone is a SonyEricsson K800i

Comment 1 A. Folger 2008-08-18 11:31:01 UTC
OOPS, step 3 to reproduce is obviously "syncronize". By the way, I googled for the error message and found nothing particularly helpful.

Comment 2 A. Folger 2008-10-24 12:11:05 UTC
I now realize that this is essentially a duplicate of bug #447557, which I had filed previously. But the problem is still present, and it is quite crippling for desktop users.

Comment 3 A. Folger 2008-10-24 12:12:41 UTC

*** This bug has been marked as a duplicate of bug 447557 ***