ubuntuone-preferences crashed with SIGSEGV in free()

Bug #620216 reported by LSL
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

Crashed out when trying to use the Ubuntu One preferences to make sure that the contacts and file downloads were marked for synchronization.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client-gnome 1.3.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 18 18:18:57 2010
ExecutablePath: /usr/bin/ubuntuone-preferences
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python /usr/bin/ubuntuone-preferences
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7fdd6ae7bc2d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7fdd6ae7bc2d) ok
 source "-0x8(%rdi)" (0x4c00b628) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ubuntuone-client
StacktraceTop:
 free () from /lib/libc.so.6
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc ()
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: ubuntuone-preferences crashed with SIGSEGV in free()
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
LSL (spesialstyrker) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #620692, 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.

visibility: private → public
tags: removed: need-amd64-retrace
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.