ubuntuone-login crashed with SIGSEGV

[Chris Jones]

Binary package hint: ubuntuone-client

I started the Ubuntu One item in System->Preferences and it crashed on startup.

ProblemType: Crash
.home.cmsj..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.cmsj..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 2048000
 write_limit = 112640
 on = True
.home.cmsj..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 1
 bookmarked = True
Architecture: amd64
Date: Thu Mar 4 14:21:27 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
InterpreterPath: /usr/bin/python2.6
Package: ubuntuone-client-gnome 1.1.2-0ubuntu2
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.utf8
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x7f15dc8d24e0: movl $0xffffffff,0x4(%rdi)
 PC (0x7f15dc8d24e0) 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-15-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd 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.