Bug 513083 – crash in Volume Control: trying to put the applet...

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 513083 - crash in Volume Control: trying to put the applet...


Summary:	crash in Volume Control: trying to put the applet...


Status:	RESOLVED DUPLICATE of bug 513018

Product:	gnome-applets
Classification:	Other
Component:	mixer
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-30 11:36 UTC by angelo.antico
Modified:	2008-01-30 18:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description angelo.antico 2008-01-30 11:36:04 UTC

What were you doing when the application crashed?
trying to put the applet on the panel


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.17012008 #1 SMP PREEMPT Thu Jan 17 12:39:39 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 34365440 vsize: 34365440 resident: 13332480 share: 9805824 rss: 13332480 rss_rlim: 4294967295
CPU usage: start_time: 1201692857 rtime: 26 utime: 20 stime: 6 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e696b0 (LWP 6439)]
0xb77c4321 in waitpid () from /lib/libpthread.so.0

+ Trace 187372

Thread 1 (Thread 0xb6e696b0 (LWP 6439))

#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 ??
from /usr/lib/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_oss_mixer_element_list_tracks
at gstossmixerelement.c line 69
#8 gst_mixer_list_tracks
at mixer.c line 154
#9 gst_audio_mixer_filter_check_element
at mixerutils.c line 91
#10 gst_audio_default_registry_mixer_filter
at mixerutils.c line 161
#11 ??
#12 ??
#13 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
[00000558] main video output warning: late picture skipped (17803745)
[00000558] main video output warning: late picture skipped (17770426)
[00000558] main video output warning: late picture skipped (17737107)
[00000558] main video output warning: late picture skipped (17727018)
[00000558] main video output warning: late picture skipped (17693756)
[00000558] main video output warning: late picture skipped (17660439)
[00000558] main video output warning: late picture skipped (17627129)
[00000558] main video output warning: late picture skipped (17593800)
[00000558] main video output warning: late picture skipped (17560482)
[00000558] main video output warning: late picture skipped (17527173)
[00000558] main video output warning: late picture skipped (17493843)
[00000558] main video output warning: late picture skipped (17480590)
[00000558] main video output warning: late picture skipped (17447418)
[00000558] main video output warning: late picture skipped (17414094)
[00000558] main video output warning: late picture skipped (17380776)
--------------------------------------------------

Comment 1 Gianluca Borello 2008-01-30 18:16:03 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 ***