indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Bug #1681255 reported by Antonio Contreras
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

It appears every time I start the OS. Installed using daily build of the 8th April 2017.
OS: Ubuntu 17.04

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu3
Architecture: i386
CurrentDesktop: Unity:Unity7
Date: Sun Apr 9 20:11:45 2017
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2017-04-09 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta i386 (20170408)
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
ProcEnviron:
 LANG=es_ES.UTF-8
 LANGUAGE=es
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=<optimized out>) at malloc.c:301
 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 <main_arena>) at malloc.c:2400
 _int_malloc (av=av@entry=0xb6dd7780 <main_arena>, bytes=bytes@entry=260) at malloc.c:3862
 __GI___libc_malloc (bytes=260) at malloc.c:2925
 operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Antonio Contreras (asusg71v) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb77bacf9 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 0xb77bacf9 in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

StacktraceTop:
 __malloc_assert (assertion=assertion@entry=0xb6d84f38 "(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", file=file@entry=0xb6d81696 "malloc.c", line=line@entry=2403, function=<optimized out>) at malloc.c:301
 sysmalloc (nb=nb@entry=264, av=av@entry=0xb6dd7780 <main_arena>) at malloc.c:2400
 _int_malloc (av=av@entry=0xb6dd7780 <main_arena>, bytes=bytes@entry=260) at malloc.c:3862
 __GI___libc_malloc (bytes=260) at malloc.c:2925
 operator new (sz=260) at ../../../../src/libstdc++-v3/libsupc++/new_op.cc:50

Revision history for this message
Brian Murray (brian-murray) wrote : Stacktrace.txt
Revision history for this message
Brian Murray (brian-murray) wrote : StacktraceSource.txt
Revision history for this message
Brian Murray (brian-murray) wrote : ThreadStacktrace.txt
Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Antonio Contreras (asusg71v) wrote :

Wrong! The duplicate is https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1681870

This is the original. Please see the date

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.