ubuntuone-syncdaemon crashed with ImportError in get_interfaces_for_object(): No module named Dee

Just got this bug myself it occurred as I went to login to ubuntu one for the first time.

As a temporary workaround, you can "apt-get remove gir1.2-unity-3.0" which will stop the crashing.

Workaround for Ubuntu One:

Run the following in the terminal:

sudo apt-get remove gir1.2-unity-3.0

This will remove the library that is used by syncdaemon to provide the progress information to Unity and therefore the broken library will not be used.

This originally seemed to be an isolated incident on Natty, but since the latest Natty updates (2011-03-08 21:00 UTC) apport is now catching a, relatively debilitating, infinite loop of Ubuntu One crashes.
Removing gir1.2-unity-3.0 caused Ubuntu One to report "connection restored".

This bug was fixed in the package libunity - 3.6.2-0ubuntu2

---------------
libunity (3.6.2-0ubuntu2) natty; urgency=low

  * src/Unity-3.0.gir
    - Added include for Dee (LP: #731023)
  * debian/control
    - Bump build depends for libdee-dev to >= 0.5.12-0ubuntu2 to make sure
      we build against the version of libdee with needed vapi fixes
 -- Ken VanDine <email address hidden> Tue, 08 Mar 2011 17:00:47 -0500

what's that? i just wanted to sing in UBUNTU ONE :(

Please, try to update. The last update fixed the issue. It was released
several hours ago.

2011/3/9 Angel Ayala <email address hidden>

> what's that? i just wanted to sing in UBUNTU ONE :(
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (731601).
> https://bugs.launchpad.net/bugs/731023
>
> Title:
> ubuntuone-syncdaemon crashed with ImportError in
> get_interfaces_for_object(): No module named Dee
>
> Status in “libunity” package in Ubuntu:
> Fix Released
>
> Bug description:
> Binary package hint: ubuntuone-client
>
> Intel 4500HD
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: ubuntuone-client 1.5.5-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> Architecture: amd64
> Date: Tue Mar 8 05:55:39 2011
> ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
> InterpreterPath: /usr/bin/python2.7
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python
> /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
> ProcCwd: /
> ProcEnviron:
> SHELL=/bin/bash
> LANGUAGE=ru_RU:ru:en_AU:en_CA:en_GB:en_NZ:en_US:en
> LANG=ru_RU.UTF-8
> PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
> SourcePackage: ubuntuone-client
> Title: ubuntuone-syncdaemon crashed with ImportError in
> get_interfaces_for_object(): No module named Dee
> UbuntuOneSyncdaemonExceptionsLog:
>
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/731023/+subscribe
>

I used Roman Yepishev's workaround earlier
  ( sudo apt-get remove gir1.2-unity-3.0 )
which seemed to fix things for me.

Later on I noticed the libunity update had been pushed out, and I did not notice a file named similarly to gir1.2-unity-3.0 in those updates.

This is probably a dumb question, but do I need to reinstall anything manually or would anything analogous to gir1.2-unity-3.0 have been handled in the dependencies of the most recent update?

The problem still seems to be resolved for me after the most recent update in any event.

No, You do not need to do anything. As far as I know, this update only
removed gir1.2-unity-3.0. The update did the same thing You did. There is no
change for You, as far as I know.

2011/3/9 bitu-derr <email address hidden>

> I used Roman Yepishev's workaround earlier
> ( sudo apt-get remove gir1.2-unity-3.0 )
> which seemed to fix things for me.
>
> Later on I noticed the libunity update had been pushed out, and I did
> not notice a file named similarly to gir1.2-unity-3.0 in those updates.
>
> This is probably a dumb question, but do I need to reinstall anything
> manually or would anything analogous to gir1.2-unity-3.0 have been
> handled in the dependencies of the most recent update?
>
> The problem still seems to be resolved for me after the most recent
> update in any event.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (731601).
> https://bugs.launchpad.net/bugs/731023
>
> Title:
> ubuntuone-syncdaemon crashed with ImportError in
> get_interfaces_for_object(): No module named Dee
>
> Status in “libunity” package in Ubuntu:
> Fix Released
>
> Bug description:
> Binary package hint: ubuntuone-client
>
> Intel 4500HD
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: ubuntuone-client 1.5.5-0ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
> Uname: Linux 2.6.38-5-generic x86_64
> Architecture: amd64
> Date: Tue Mar 8 05:55:39 2011
> ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
> InterpreterPath: /usr/bin/python2.7
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python
> /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
> ProcCwd: /
> ProcEnviron:
> SHELL=/bin/bash
> LANGUAGE=ru_RU:ru:en_AU:en_CA:en_GB:en_NZ:en_US:en
> LANG=ru_RU.UTF-8
> PythonArgs: ['/usr/lib/ubuntuone-client/ubuntuone-syncdaemon']
> SourcePackage: ubuntuone-client
> Title: ubuntuone-syncdaemon crashed with ImportError in
> get_interfaces_for_object(): No module named Dee
> UbuntuOneSyncdaemonExceptionsLog:
>
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/731023/+subscribe
>

I did a sudo apt-get update/upgrade this morning, and the problem is still existing for me.

Same as wolfger, I just did an update on a fresh install and bug persists. Let me know if any other information is needed / work-arounds need to be tested.

Thanks,

David

Noticed that some upgrades were held back. Manually installed them, seems to be working now.

Same as wolfger.
Works for me now.