Ubuntu
indicator-sound package

indicator-sound-service crashed with SIGABRT in raise()

Bug #940740 reported by Bill on 2012-02-25

This bug report is a duplicate of: Bug #897218: indicator-sound-service assert failure: *** glibc detected *** /usr/lib/indicator-sound/indicator-sound-service: munmap_chunk(): invalid pointer: 0x0976cd68 ***. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	indicator-sound (Ubuntu)	New	Undecided	Unassigned

Bug Description

sorry

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-sound 0.8.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Sat Feb 25 02:12:50 2012
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120205)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
Signal: 6
SourcePackage: indicator-sound
StacktraceTop:
raise () from /lib/i386-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: indicator-sound-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-24 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Bill (e4xit) wrote on 2012-02-25:

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-25: This bug is a duplicate

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