Comment 6 for bug 273507

There's a newer version of libcanberra released which may fix this problem. In 0.10 there's the option to use a gconf schema file to load the gtk module, rather than the GTK_MODULES variable. This may fix this bug. The full release notes for libcanberra 0.10 state:

This release includes a GConf schema file which can be used to
activate the libcanberra Gtk+ module more elegantly than via setting
$GTK_MODULES. Please note however that that will work only with very
new version of gnome-settings-daemon. In fact, with a version that is
so new it isn't even released yet! ;-)

This release also includes quite a few important fixes, so please make
sure to update. If you aren't shipping the new g-s-d version you can
safely drop the schema file from your distro package. It should be
safe to set GTK_MODULES and use the schema file in parallel. It might
even be wise for enabling input feedback sounds even in non-GNOME
sessions.

http://0pointer.de/lennart/projects/libcanberra/libcanberra-0.10.tar.gz
http://0pointer.de/lennart/projects/libcanberra/

Jasper Lievisse Adriaanse (1):
      missing stdarg.h inclusion for OpenBSD compatibility

Lennart Poettering (13):
      require gconf only if we build against gtk
      make ourselves resident
      fix a memory leak
      don't free sound_path on success
      explicitly cast to long to avoid compiler warning
      remove variable names from argument lists to avoid stupid
      compiler shadow warnings
      fix prefix of byte order macros
      move ca_proplist_merge_ap()/ca_proplist_from_ap() to proplist.c
      where it belongs
      implement ca_memdup()
      minor build system fixes
      call AM_GCONF_SOURCE_2 unconditionally
      remove AM_LIBADD again since it is pointless
      bump release and soname

Marc-André Lureau (1):
      Make tdb_context database static

Matthias Clasen (1):
      Enable canberra-gtk-module via GConf