indicator-sound-service assert failure: *** glibc detected *** /usr/lib/indicator-sound/indicator-sound-service: munmap_chunk(): invalid pointer: 0x000000000041e850 ***

[Brendan Donegan]

As far as I can tell, this just happened when selecting Sound Settings via indicator-sound. The settings applet still opened successfully but this crash occurred too.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-sound 0.8.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/lib/indicator-sound/indicator-sound-service: munmap_chunk(): invalid pointer: 0x000000000041e850 ***
Date: Mon Mar 19 09:26:05 2012
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120121)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
Signal: 6
SourcePackage: indicator-sound
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f9381a0f250 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 malloc_printerr (action=3, str=0x7f9381a0f340 "munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:5007
 ?? ()
 g_cclosure_marshal_VOID(unsigned int0_t, void) () 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-sound-service assert failure: *** glibc detected *** /usr/lib/indicator-sound/indicator-sound-service: munmap_chunk(): invalid pointer: 0x000000000041e850 ***
UpgradeStatus: Upgraded to precise on 2012-02-15 (33 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #957441, 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.