ubuntuone-login crashed with SIGSEGV

[Matthew Copple]

Binary package hint: ubuntuone-client

Attempted to use the MeMenu to login to Ubuntu-One. This is probably related to other problems with the MeMenu.

ProblemType: Crash
.home.mcopple..cache.ubuntuone.log.oauth.login.log:
 2010-03-19 22:30:48,920:920.938968658 UbuntuOne.Client.Applet Starting Ubuntu One client version 1.0.3
 2010-03-20 17:00:45,276:276.364088058 ubuntuone-login Starting Ubuntu One login manager version 1.1.4
.home.mcopple..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 show_applet = 1
 connected = True
 connect = 0
 bookmarked = True
Architecture: amd64
Date: Sat Mar 20 17:00:45 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: ubuntuone-client-gnome 1.1.4-0ubuntu1
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f83ee22e4e0: movl $0xffffffff,0x4(%rdi)
 PC (0x7f83ee22e4e0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ubuntuone-client
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: ubuntuone-login crashed with SIGSEGV
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #525064, so 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. Please continue to report any other bugs you may find.