indicator-datetime-preferences crashed with SIGSEGV in g_atomic_int_exchange_and_add()

Bug #741878 reported by cari
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: indicator-datetime

Try add more locations, but it not find what I need. Try close and it crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 24 17:42:25 2011
ExecutablePath: /usr/bin/indicator-datetime-preferences
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: indicator-datetime-preferences
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f6a93d2d0a2 <g_atomic_int_exchange_and_add+2>: lock xadd %eax,(%rdi)
 PC (0x7f6a93d2d0a2) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 g_atomic_int_exchange_and_add () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: indicator-datetime-preferences crashed with SIGSEGV in g_atomic_int_exchange_and_add()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
cari (borncari) 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 #737965, 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.