gnome-alsamixer crashed with SIGSEGV in gtk_accel_group_connect_by_path()

StacktraceTop:
 _gtk_accel_map_add_group (accel_path=0x251250e "<Actions>/MainActions/FileMenu", accel_group=0x2523d40) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkaccelmap.c:860
 quick_accel_add (accel_group=0x2523d40, accel_key=0, accel_mods=0, accel_flags=GTK_ACCEL_VISIBLE, closure=0x2514250, path_quark=611) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkaccelgroup.c:508
 IA__gtk_accel_group_connect_by_path (accel_group=0x2523d40, accel_path=0x251250e "<Actions>/MainActions/FileMenu", closure=0x2514250) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkaccelgroup.c:685
 IA__gtk_action_connect_accelerator (action=0x253c100) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkaction.c:1905
 gtk_menu_item_set_related_action (action=0x253c100, menu_item=0x25999b0) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkmenuitem.c:759

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

I uploaded a fix on my PPA : https://launchpad.net/~gilir/+archive/updates
Could someone affected by this bug report if it's working for him with this package ?
Thanks.

It works perfectly with your fix! I finally able to use my jack output!
Thanks!

I added your ppa to Ubuntu Studio 11.10 amd64, and the alsamixer still will
not launch when I click on it.

On , Julien Lavergne <email address hidden> wrote:
> I uploaded a fix on my PPA : https://launchpad.net/~gilir/+archive/updates

> Could someone affected by this bug report if it's working for him with
> this package ?

> Thanks.

> --

> You received this bug notification because you are subscribed to the bug

> report.

> https://bugs.launchpad.net/bugs/849415

> Title:

> gnome-alsamixer crashed with SIGSEGV in

> gtk_accel_group_connect_by_path()

> Status in “gnome-alsamixer” package in Ubuntu:

> In Progress

> Status in “gnome-alsamixer” source package in Oneiric:

> New

> Status in “gnome-alsamixer” source package in Precise:

> In Progress

> Status in “gnome-alsamixer” package in Debian:

> New

> Bug description:

> Ubuntu 11.10

> Downloaded and installed the GNOME Alsa mixer, and it will not launch

> ProblemType: Crash

> DistroRelease: Ubuntu 11.10

> Package: gnome-alsamixer 0.9.7~cvs.20060916.ds.1-2ubuntu1

> ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4

> Uname: Linux 3.0.0-11-generic x86_64

> NonfreeKernelModules: nvidia

> ApportVersion: 1.22.1-0ubuntu2

> Architecture: amd64

> CrashCounter: 1

> Date: Tue Sep 13 15:42:02 2011

> ExecutablePath: /usr/bin/gnome-alsamixer

> ProcCmdline: gnome-alsamixer

> ProcEnviron:

> PATH=(custom, no user)

> LANG=en_US.UTF-8

> SHELL=/bin/bash

> SegvAnalysis:

> Segfault happened at: 0x7f11ff896f10: mov 0x20(%r12),%rdi

> PC (0x7f11ff896f10) ok

> source "0x20(%r12)" (0x00000020) not located in a known VMA region
> (needed readable region)!

> destination "%rdi" ok

> SegvReason: reading NULL VMA

> Signal: 11

> SourcePackage: gnome-alsamixer

> StacktraceTop:

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> gtk_accel_group_connect_by_path () from
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> gtk_action_connect_accelerator () from
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> Title: gnome-alsamixer crashed with SIGSEGV in
> gtk_accel_group_connect_by_path()

> UpgradeStatus: Upgraded to oneiric on 2011-09-13 (0 days ago)

> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

> To manage notifications about this bug go to:

> https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/849415/+subscriptions

@Brian
Could you check the version of gnome-alsamixer you have installed ? Could you also launch gnome-alsamixer in a terminal and paste the output on this bug report ?

gnome-alsamixer 0.9.7~cvs.20060916.ds.1-2ubuntu1

(gnome-alsamixer:2991): GLib-GObject-WARNING **: invalid (NULL) pointer
instance

(gnome-alsamixer:2991): GLib-GObject-CRITICAL **: g_signal_connect_data:
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_has_icon:
assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gnome-alsamixer:2991): GLib-CRITICAL **: g_hash_table_lookup: assertion
`hash_table != NULL' failed

(gnome-alsamixer:2991): GLib-CRITICAL **: g_hash_table_insert_internal:
assertion `hash_table != NULL' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_has_icon:
assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_has_icon:
assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_icon_theme_has_icon:
assertion `GTK_IS_ICON_THEME (icon_theme)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed

(gnome-alsamixer:2991): GLib-GObject-CRITICAL **: g_object_get: assertion
`G_IS_OBJECT (object)' failed

(gnome-alsamixer:2991): Gdk-CRITICAL **:
IA__gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)'
failed

(gnome-alsamixer:2991): Pango-CRITICAL **:
pango_context_set_font_description: assertion `context != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_context_set_base_dir:
assertion `context != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_context_set_language:
assertion `context != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_layout_new: assertion
`context != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_layout_set_text: assertion
`layout != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_layout_get_pixel_extents:
assertion `PANGO_IS_LAYOUT (layout)' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_layout_set_text: assertion
`layout != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICAL **: pango_layout_get_pixel_extents:
assertion `PANGO_IS_LAYOUT (layout)' failed

(gnome-alsamixer:2991): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(gnome-alsamixer:2991): Gdk-CRITICAL **:
IA__gdk_pango_context_get_for_screen: assertion `GDK_IS_SCREEN (screen)'
failed

(gnome-alsamixer:2991): Pango-CRITICAL **:
pango_context_set_font_description: assertion `context != NULL' failed

(gnome-alsamixer:2991): Pango-CRITICA...

@Brian
The version should be 0.9.7~cvs.20060916.ds.1-2.1ubuntu0.1
Please do in a terminal "sudo apt-get update" and "sudo apt-get upgrade" and make sure you have the new package installed.

@Julien Lavergne,

Hello ,
I'm happy to see that You are working on this bug, I'm just migrated with one off my pc's to the new 11.10 oneiric.
The only think which does not work is gmome-alsamixer. Wich I really need. Yesterday I filled in a bug repport concerning this problem, Since googling around I'm far from alone to have this bug.

It did not catch that there was already a bug. bassicaly it's just the same bug as I filled yesterday.

Here the link.

https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/882488

There Is al info needed. I tried to work self on it. Now just succeeded to have a succesfull recompile with you latest changes. But is same problem. I also have just reinstalled the whole 11.10. Fully updated (x86_amd64) futher info is in bug mentioned above. It's still the same. This is ter info

@Julien Lavergne,

I just updated alsa-mixer with Your work on ppa:gilir/updates

IT work's GREAT Thank You

The last did it

I just installed the update, and everything's fine. Thanks for the effort.

On , Christophe Van Reusel <email address hidden> wrote:
> @Julien Lavergne,

> I just updated alsa-mixer with Your work on ppa:gilir/updates

> IT work's GREAT Thank You

> The last did it

> --

> You received this bug notification because you are subscribed to the bug

> report.

> https://bugs.launchpad.net/bugs/849415

> Title:

> gnome-alsamixer crashed with SIGSEGV in

> gtk_accel_group_connect_by_path()

> Status in “gnome-alsamixer” package in Ubuntu:

> In Progress

> Status in “gnome-alsamixer” source package in Oneiric:

> New

> Status in “gnome-alsamixer” source package in Precise:

> In Progress

> Status in “gnome-alsamixer” package in Debian:

> New

> Bug description:

> Ubuntu 11.10

> Downloaded and installed the GNOME Alsa mixer, and it will not launch

> ProblemType: Crash

> DistroRelease: Ubuntu 11.10

> Package: gnome-alsamixer 0.9.7~cvs.20060916.ds.1-2ubuntu1

> ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4

> Uname: Linux 3.0.0-11-generic x86_64

> NonfreeKernelModules: nvidia

> ApportVersion: 1.22.1-0ubuntu2

> Architecture: amd64

> CrashCounter: 1

> Date: Tue Sep 13 15:42:02 2011

> ExecutablePath: /usr/bin/gnome-alsamixer

> ProcCmdline: gnome-alsamixer

> ProcEnviron:

> PATH=(custom, no user)

> LANG=en_US.UTF-8

> SHELL=/bin/bash

> SegvAnalysis:

> Segfault happened at: 0x7f11ff896f10: mov 0x20(%r12),%rdi

> PC (0x7f11ff896f10) ok

> source "0x20(%r12)" (0x00000020) not located in a known VMA region
> (needed readable region)!

> destination "%rdi" ok

> SegvReason: reading NULL VMA

> Signal: 11

> SourcePackage: gnome-alsamixer

> StacktraceTop:

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> gtk_accel_group_connect_by_path () from
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> gtk_action_connect_accelerator () from
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

> Title: gnome-alsamixer crashed with SIGSEGV in
> gtk_accel_group_connect_by_path()

> UpgradeStatus: Upgraded to oneiric on 2011-09-13 (0 days ago)

> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

> To manage notifications about this bug go to:

> https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/849415/+subscriptions

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

This bug was fixed in the package gnome-alsamixer - 0.9.7~cvs.20060916.ds.1-2.1ubuntu1

---------------
gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2.1ubuntu1) precise; urgency=low

  * Sync with Debian unstable.
  * debian/patches
   - 06-use-libgnome-headers.patch: Correctly use libgnomeui. (LP: #849415)

gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2.1) unstable; urgency=low

  * Non-maintainer upload.
  * Fix "FTBFS: gnome-app-helper.h:620:2: error: expected specifier-
    qualifier-list before 'GtkCallbackMarshal'": add patches from Ubuntu /
    Julien Lavergne:
    + debian/patches:
      - 05-remove-G_CONST_RETURN.patch: Remove usage of G_CONST_RETURN.
      - 06-use-libgnome-headers.patch: Use correct headers.
    + debian/rules:
      - Remove deprecated flags.
    Closes: #622067, LP: #749291
 -- Julien Lavergne <email address hidden> Sat, 29 Oct 2011 00:48:17 +0200

@Julien Lavergne

Hello, I've seen That You changed again the status from this bug in oneiric to New.

It is well the same bug as was in precise, wich you fixed now. Thank's

Your patched version off gnome-alsamixer does work perfect in oneiric .

Can it not be placed into oneiric ubuntu oneiric as well ?

Hello.
I also installed this update in oneiric and it does indeed fix the problem. Thanks for that!
However, this version of gnome-alsamixer does not offer the same functions, the versions in natty and before offered (ex. no mute-checkboxes for the "master" and other sound card elements, except for "beep"-element.)

This may not be an issue for most people, but muting (checkbox) the master-element of my internal soundcard is, at least for me, the only option to completely disable (power off) my laptops internal speakers.

@Moko

here by me all channels with mute box in the just patched gnome-alsamixer.

But to mute You're speakers completely You always can use ubuntu's standard volume controle.

@Christophe Van Reusel

strange....I get no mute checkboxes, but instead a new auto-mute checkbox. But this does not get the desired result.

I know about the normal audio controls, but these won't do the trick.
My laptops internal sound card really sucks, it emitts a slight hissing sound everytime the gpu gets under load.
There is no option to disable the onboard card hardware-side and a "normal" mute in the volume controls will mute the internal card, but not turn it off completely.
Only checking "mute" in the master-element of the internal sound card in gnome-alsamixer disables the card completely (no more hissing). But the necessary "mute" checkbox does not exist in this fixed version.

I know, it's a strange problem, but that's the way it is...

It sounds like You automatic sense of audio card type did not went ok. This problem is also by my pc since ubuntu used kernel I think it from 2.6.30 and higher linu kernel versions. (it's kernel not ubuntu related)

adding correct sound card into /etc/modprobe.d/alsa-base.conf does solve this problem.

I had to add : options snd-hda-intel model=asus-p5q

First look up your correct card into alsa data base (or google around concerning sound ubuntu with your laptop)

Here a good link for it

http://www.mjmwired.net/kernel/Documentation/sound/alsa/HD-Audio-Models.txt

Insert correct model number for your lap model=xxxxx

And restart your pc

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

Thanks ! Works for me now.

--Amit

On Fri, Oct 28, 2011 at 5:33 PM, Julien Lavergne
<email address hidden>wrote:

> I uploaded a fix on my PPA : https://launchpad.net/~gilir/+archive/updates
> Could someone affected by this bug report if it's working for him with
> this package ?
> Thanks.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (853195).
> https://bugs.launchpad.net/bugs/849415
>
> Title:
> gnome-alsamixer crashed with SIGSEGV in
> gtk_accel_group_connect_by_path()
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/849415/+subscriptions
>

@Christophe Van Reusel

Too bad, but that's not it.
Everything's set right and I can control in internal sound card, as well as the usb one with this fixed version.
I just don't get mute-checkboxes, where I need them.

@Christophe Van Reusel

Sorry, you were right after all with the alsa-base.conf
Took this noob a while, but I figured it out.
Thank you sooo much!

So, this fix really works perfectly, after all.

same problem with Dell 1558 Studio
Oneiric 64bit

I added following in/etc/modprobe.d/alsa-base.conf and it worked for Dell 1558 Studio

options snd-hda-intel model=auto

@Moko & @userdce

Thank's for informing it did worked out with alsa-base.conf.

> Julien Lavergne (gilir) wrote on 2011-10-28: #6
> I uploaded a fix on my PPA : https://launchpad.net/~gilir/+archive/updates
> Could someone affected by this bug report if it's working for him with this package ?
> Thanks.

Works for me on 11.10 with Openbox

Hi all,
Just to clarify the situation, updates for a stable release of Ubuntu follow a different process (see https://wiki.ubuntu.com/StableReleaseUpdates). Please keep the status as "New" for now.

@Julien Lavergne

Ok I readed That. This bug is a severe regression on 11.10, ... that's my personal view. The main ubuntu maintainers do have an other point off view concerning audio in general in ubuntu.

In despit off some good improvements concerning audio since 10.10 The overall compatibility went seriousely down on ubuntu.
Many users are left with non or bad working audio.

This off course is not Your fault. Thank's for Your work on gnome-alsamixer. Now that it is released in precise, users can always download it with this link and the install with dpkg.

http://launchpadlibrarian.net/83939881/gnome-alsamixer_0.9.7%7Ecvs.20060916.ds.1-2.1ubuntu1_amd64.deb

Can I get the location for 32bit package..

Thank you
Mukesh

On Thu, Nov 3, 2011 at 2:46 PM, Christophe Van Reusel <
<email address hidden>> wrote:

> @Julien Lavergne
>
> Ok I readed That. This bug is a severe regression on 11.10, ... that's
> my personal view. The main ubuntu maintainers do have an other point off
> view concerning audio in general in ubuntu.
>
> In despit off some good improvements concerning audio since 10.10 The
> overall compatibility went seriousely down on ubuntu.
> Many users are left with non or bad working audio.
>
> This off course is not Your fault. Thank's for Your work on gnome-
> alsamixer. Now that it is released in precise, users can always download
> it with this link and the install with dpkg.
>
> http://launchpadlibrarian.net/83939881/gnome-
> alsamixer_0.9.7%7Ecvs.20060916.ds.1-2.1ubuntu1_amd64.deb
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (874273).
> https://bugs.launchpad.net/bugs/849415
>
> Title:
> gnome-alsamixer crashed with SIGSEGV in
> gtk_accel_group_connect_by_path()
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/849415/+subscriptions
>

I'm not shure if it's the latest one . Here for i386

http://launchpadlibrarian.net/83932052/gnome-alsamixer_0.9.7%7Ecvs.20060916.ds.1-2.1ubuntu1_i386.deb

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

Hello Brian, or anyone else affected,

Accepted gnome-alsamixer into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Hello Martin

Just tested the proposed updates. But gnome-alsamixer is not in yet. Perhaps it will take a couple of hours more.

At this time still package 0.9.7~cvs.20060916.ds.1-2ubuntu1 which is same as before and does not work seg fault. is still version from 12 september 2011

Will wait untill 0.9.7~cvs.20060916.ds.1-2.1ubuntu1 shows up I gues ?

Ter info I work with x86-64

@Martin Pitt

I double checked but in ubuntu oneiric-proposed the latest package updates are from 09 november .

Hm, it certainly is on archive.ubuntu.com at least:

gnome-alsamixer | 0.9.7~cvs.20060916.ds.1-2ubuntu1 | oneiric/universe | source, amd64, armel, i386, powerpc
gnome-alsamixer | 0.9.7~cvs.20060916.ds.1-2.1ubuntu0.1 | oneiric-proposed/universe | source, amd64, armel, i386, powerpc

@Martin Pitt
Hello, Now it's there (I was a little to inpatient -:)

It does work fine on x86-64 ubuntu oneiric 11.10 kernel 3.0.0-13 oneiric-proposed version 0.9.7~cvs.20060916.ds.1-2.1ubuntu0.1

Thank's

Splendid, thanks for testing!

After enabling proposed for oneiric and installing latest package, it worked for me too.

This bug was fixed in the package gnome-alsamixer - 0.9.7~cvs.20060916.ds.1-2.1ubuntu0.1

---------------
gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2.1ubuntu0.1) oneiric-proposed; urgency=low

  * Sync with Debian unstable.
  * debian/patches
   - 06-use-libgnome-headers.patch: Correctly use libgnomeui. (LP: #849415)

gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2.1) unstable; urgency=low

  * Non-maintainer upload.
  * Fix "FTBFS: gnome-app-helper.h:620:2: error: expected specifier-
    qualifier-list before 'GtkCallbackMarshal'": add patches from Ubuntu /
    Julien Lavergne:
    + debian/patches:
      - 05-remove-G_CONST_RETURN.patch: Remove usage of G_CONST_RETURN.
      - 06-use-libgnome-headers.patch: Use correct headers.
    + debian/rules:
      - Remove deprecated flags.
    Closes: #622067, LP: #749291
 -- Julien Lavergne <email address hidden> Sat, 29 Oct 2011 01:05:45 +0200

Today's update fixed the problem for me...gnome-alsamixer now runs without crashing. I had not previously applied any patches, so this definitely provided the fix. Thanks!