gnome-alsamixer crashed with SIGSEGV in gam_mixer_get_config_name()

Bug #270066 reported by jyb
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-alsamixer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-alsamixer

I got this crash report while running gnome-alsamixer via the Application menu.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-alsamixer
NonfreeKernelModules: nvidia
Package: gnome-alsamixer 0.9.7~cvs.20060916.ds.1-1
ProcAttrCurrent: unconfined
ProcCmdline: gnome-alsamixer
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-alsamixer
StacktraceTop:
 gam_mixer_get_config_name ()
 gam_mixer_get_visible ()
 ?? ()
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
Title: gnome-alsamixer crashed with SIGSEGV in gam_mixer_get_config_name()
Uname: Linux 2.6.24-19-server x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
jyb (jeanyves-bossard) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gam_mixer_get_config_name ()
gam_mixer_get_visible ()
?? ()
IA__g_object_newv (object_type=6843936, n_parameters=<value optimized out>, parameters=0x68a8f0)
IA__g_object_new_valist (object_type=6843936, first_property_name=0x0, var_args=0x7fff9ffc3760)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-alsamixer:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-alsamixer:
status: Incomplete → Invalid
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.