Ubuntu
gnome-media package

gnome-volume-control crashed with SIGABRT in raise()

Bug #763106 reported by David Lerouvillois on 2011-04-16

This bug report is a duplicate of: Bug #741155: gnome-volume-control crashed with SIGABRT in raise(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-media (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gnome-media

There is no sound.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-media 2.32.0-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 16 23:20:02 2011
ExecutablePath: /usr/bin/gnome-volume-control
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: gnome-volume-control --page=applications
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANGUAGE=fr_FR:en
LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: gnome-media
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-volume-control crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to natty on 2011-04-16 (0 days ago)
UserGroups: adm admin cdrom dialout fax lpadmin plugdev sambashare vboxusers

Tags:

Revision history for this message

David Lerouvillois (deados) wrote on 2011-04-16:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-04-16: 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 #741155, 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.