ubuntuone-client-applet showing ! crashed on login

[James Tait]

Binary package hint: ubuntuone-client

After a clean reboot I logged in as normal. The Ubuntu One Client Applet was showing the cloud with exclamation mark and things generally seemed to be taking longer than normal to boot. I left-clicked the applet and got the Apport window. It's not clear whether the act of clicking the applet caused the crash, or if the crash had already occurred.

jtait@ferrari:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

jtait@ferrari:~$ apt-cache policy ubuntuone-client
ubuntuone-client:
  Installed: 1.0.3-0ubuntu1
  Candidate: 1.0.3-0ubuntu1
  Version table:
 *** 1.0.3-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        100 /var/lib/dpkg/status
     1.0.2-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

ProblemType: Bug
.home.jtait..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.jtait..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = False
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: amd64
Date: Wed Mar 31 21:51:33 2010
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-20-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2055): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2103): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2089): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2086): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Duane Hinnen (duanedesign)]

James,
Thank you for taking the time to report this bug and helping to make Ubuntu better. Thanks to your detailed description I was able to determine this particular bug has already been reported and is a duplicate of bug 498444, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.