gnome-control-center crashed with SIGSEGV in memalign() while adding a new timezone

Bug #864932 reported by JudgeDredd
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Incomplete
Undecided
Unassigned
indicator-datetime (Ubuntu)
Expired
Medium
Unassigned

Bug Description

application crashed while trying to add a timezone to the clock applet.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-datetime 0.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Sun Oct 2 19:41:35 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: gnome-control-center indicator-datetime
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_PY.UTF-8
SegvAnalysis:
 Segfault happened at: 0xdf6ef4: mov 0x4(%esi),%eax
 PC (0x00df6ef4) ok
 source "0x4(%esi)" (0x00000007) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 memalign () from /lib/i386-linux-gnu/libc.so.6
 posix_memalign () from /lib/i386-linux-gnu/libc.so.6
Title: gnome-control-center crashed with SIGSEGV in memalign()
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
JudgeDredd (hcabanasg) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=0xf01400) at malloc.c:5153
 malloc_consolidate (av=0xf01400) at malloc.c:5089
 _int_malloc (av=0xf01400, bytes=528) at malloc.c:4373
 _int_memalign (av=0xf01400, alignment=256, bytes=248) at malloc.c:5492
 __GI___libc_memalign (alignment=256, bytes=248) at malloc.c:3880

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Olli Ries (ories) wrote :

please reopen if problem still exists

Changed in indicator-datetime:
status: New → Incomplete
Charles Kerr (charlesk)
Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
Revision history for this message
Charles Kerr (charlesk) wrote :

This appears to be a memory corruption issue -- as the subject suggests, this is happening deep inside the memory allocator, in this case when called by glib's slab allocator.

JD, thanks for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Precise Pangolin. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ .

If the crash persists in Precise, please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem. Thanks again and we appreciate your help.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.]

Changed in indicator-datetime (Ubuntu):
status: Incomplete → Expired
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.