After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 513390 - crash in Volume Control: adding volume module to ...
crash in Volume Control: adding volume module to ...
Status: RESOLVED DUPLICATE of bug 513018
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-31 09:49 UTC by neosimago
Modified: 2008-01-31 12:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description neosimago 2008-01-31 09:49:08 UTC 
What were you doing when the application crashed?
adding volume module to panel. 


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.1 2007-11-21 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-gentoo-r8-reiser4-nfs4-amd64 #11 SMP PREEMPT Sat Jan 26 16:22:02 PST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 232910848 vsize: 232910848 resident: 14127104 share: 9908224 rss: 14127104 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201772929 rtime: 11 utime: 9 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/mixer_applet2'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b92aba90520 (LWP 11648)]
0x0000003e5f60dfcf in waitpid () from /lib/libpthread.so.0

+ Trace 187556

Thread 1 (Thread 0x2b92aba90520 (LWP 11648))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 bugbuddy_segv_handle
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 gst_ossmixer_track_new
    at gstossmixertrack.c line 177
  • #6 gst_ossmixer_list_tracks
    at gstossmixer.c line 154
  • #7 gst_audio_mixer_filter_check_element
    from /usr/lib/libgstaudio-0.10.so.0
  • #8 gst_audio_default_registry_mixer_filter
    from /usr/lib/libgstaudio-0.10.so.0
  • #9 gnome_volume_applet_toplevel_configure_handler
  • #10 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_widget_event_internal
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gdk_event_dispatch
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #23 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #24 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (29 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Gianluca Borello 2008-01-31 12:49:06 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 513018 ***