Bug 383244 – crash in Volume Control: booting up.

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 383244 - crash in Volume Control: booting up.


Summary:	crash in Volume Control: booting up.


Status:	RESOLVED INCOMPLETE

Product:	GStreamer
Classification:	Platform
Component:	gstreamer (core)
Version:	0.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	git master
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-07 03:52 UTC by rixius
Modified:	2007-01-11 16:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description rixius 2006-12-07 03:52:45 UTC

What were you doing when the application crashed?
booting up.		


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 31887360 vsize: 0 resident: 31887360 share: 0 rss: 7196672 rss_rlim: 0
CPU usage: start_time: 1165402262 rtime: 0 utime: 18 stime: 0 cutime:17 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225693520 (LWP 4624)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92212

Thread 1 (Thread -1225693520 (LWP 4624))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_utf8_validate
from /usr/lib/libglib-2.0.so.0
#5 __gst_element_details_set
from /usr/lib/libgstreamer-0.10.so.0
#6 __gst_element_details_copy
from /usr/lib/libgstreamer-0.10.so.0
#7 gst_element_class_set_details
from /usr/lib/libgstreamer-0.10.so.0
#8 ??
from /usr/lib/gstreamer-0.10/libgstavi.so
#9 ??
#10 ??
from /usr/lib/gstreamer-0.10/libgstavi.so
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
from /usr/lib/libgobject-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 g_type_class_ref
from /usr/lib/libgobject-2.0.so.0
#21 g_type_class_ref
from /usr/lib/libgobject-2.0.so.0
#22 gst_element_register
from /usr/lib/libgstreamer-0.10.so.0
#23 ??
from /usr/lib/gstreamer-0.10/libgstavi.so
#24 ??
#25 ??
from /usr/lib/gstreamer-0.10/libgstavi.so
#26 ??
#27 ??
#28 ??
from /usr/lib/libgstreamer-0.10.so.0
#29 ??
#30 ??
#31 gst_plugin_get_name
from /usr/lib/libgstreamer-0.10.so.0
#32 gst_plugin_get_name
from /usr/lib/libgstreamer-0.10.so.0
#33 gst_plugin_load_file
from /usr/lib/libgstreamer-0.10.so.0
#34 gst_default_registry_check_feature_version
from /usr/lib/libgstreamer-0.10.so.0
#35 gst_registry_scan_path
from /usr/lib/libgstreamer-0.10.so.0
#36 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#37 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#38 g_option_context_parse
from /usr/lib/libglib-2.0.so.0
#39 gst_init_check
from /usr/lib/libgstreamer-0.10.so.0
#40 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#41 main
#0 __kernel_vsyscall

Comment 1 palfrey 2006-12-07 11:47:42 UTC

This appears to be a gstreamer bug, not a mixer issue.

Comment 2 palfrey 2006-12-11 13:39:55 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 3 Christian Kirbach 2006-12-11 16:57:24 UTC

you detected correctly, it is gstreamer

looks unique

please install all gstreamer and the glib package

Comment 4 Bruno Boaventura 2007-01-11 16:49:06 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!