osplugin crashed with TypeError in report_error()

Bug #437086 reported by Jean-Louis Dupond
72
This bug affects 14 people
Affects Status Importance Assigned to Milestone
opensync (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When trying to Sync HTC Diamond 2, between Evolution. I get this crash in the GUI when I press refresh

ProblemType: Crash
Architecture: amd64
Date: Sat Sep 26 10:47:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/opensync/osplugin
NonfreeKernelModules: nvidia
Package: libopensync0 0.22-2build1
ProcCmdline: /usr/lib/opensync/osplugin /home/username/.opensync-0.22/group1 2
ProcEnviron:
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: opensync
Title: osplugin crashed with TypeError in report_error()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jean-Louis Dupond (dupondje) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Revision history for this message
souplin (klage) wrote :

Same Problem here ->

msynctool --sync synce-sync
Synchronizing group "synce-sync"
The previous synchronization was unclean. Slow-syncing
DEBUG:SynCE:Connect() called
ERROR:SynCE:connect() failed: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/bin/sync-engine: Success
Member 2 of type evo2-sync just connected
Traceback (most recent call last):
  File "/usr/lib/opensync/python-plugins/synce-opensync-plugin-2x.py", line 131, in _CBConnectOnIdle
    ctx.report_error()
  File "/usr/lib/pymodules/python2.6/opensync.py", line 132, in report_error
    def report_error(*args): return _opensync.OSyncContext_report_error(*args)
TypeError: OSyncContext_report_error expected 3 arguments, got 1

Revision history for this message
ssokolow (sl0mka) wrote :

same here - i think
Member 2 of type evo2-sync just connected
All clients connected or error
DEBUG:SynCE:get_changeinfo() called
INFO:SynCE:initiating device synchronization
Traceback (most recent call last):
  File "/usr/lib/opensync/python-plugins/synce-opensync-plugin-2x.py", line 152, in get_changeinfo
    self._TriggerSync()
  File "/usr/lib/opensync/python-plugins/synce-opensync-plugin-2x.py", line 117, in _TriggerSync
    self.engine.Synchronize()
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.synce.SyncEngine.Error.NoBoundPartnership:
Member 1 of type synce-opensync-plugin had an error while getting changes: Error during get_changeinfo() method
DEBUG:SynCE:disconnect() called
Member 1 of type synce-opensync-plugin just disconnected
Member 2 of type evo2-sync just sent all changes
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
Error while synchronizing: Unable to read from one of the members

Revision history for this message
Mark Ellis (mark-mpellis) wrote :

Jean-Louis and souplin, you have identical problems. There is a bug in the synce-sync-engine package in karmic. If you edit the file /usr/share/dbus-1/services/org.synce.SyncEngine.service, where it says Exec=/usr/bin/sync-engine change it to read Exec=/usr/bin/synce-sync-engine

You could instead use the packages in the synce PPA

ssokolow, you have a completely different problem, you have no partnership set up that synce is paired to.

Revision history for this message
Jean-Louis Dupond (dupondje) wrote :

As there is a much newer version in Oneiric now this should be fixed.

Changed in opensync (Ubuntu):
status: New → Fix Released
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.