Bug 390019 – crash in Volume Control: avviando il sistema

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 390019 - crash in Volume Control: avviando il sistema


Summary:	crash in Volume Control: avviando il sistema


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	390020 392018 420627 431511 431512 431640 436868 458717 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-27 14:07 UTC by chungfu
Modified:	2007-07-26 05:04 UTC

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

Description chungfu 2006-12-27 14:07:24 UTC

What were you doing when the application crashed?
avviando il sistema


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

Memory status: size: 40771584 vsize: 0 resident: 40771584 share: 0 rss: 8609792 rss_rlim: 0
CPU usage: start_time: 1167228407 rtime: 0 utime: 20 stime: 0 cutime:18 cstime: 0 timeout: 2 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 -1226234192 (LWP 4737)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 97280

Thread 1 (Thread -1226234192 (LWP 4737))

#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 _dl_rtld_di_serinfo
from /lib/ld-linux.so.2
#5 _dl_make_stack_executable
from /lib/ld-linux.so.2
#6 _dl_rtld_di_serinfo
from /lib/ld-linux.so.2
#7 _dl_make_stack_executable
from /lib/ld-linux.so.2
#8 dlopen
from /lib/tls/i686/cmov/libdl.so.2
#9 _dl_rtld_di_serinfo
from /lib/ld-linux.so.2
#10 dlerror
from /lib/tls/i686/cmov/libdl.so.2
#11 dlopen
from /lib/tls/i686/cmov/libdl.so.2
#12 g_module_open
from /usr/lib/libgmodule-2.0.so.0
#13 gst_plugin_load_file
from /usr/lib/libgstreamer-0.10.so.0
#14 gst_default_registry_check_feature_version
from /usr/lib/libgstreamer-0.10.so.0
#15 gst_registry_scan_path
from /usr/lib/libgstreamer-0.10.so.0
#16 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#17 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#18 g_option_context_parse
from /usr/lib/libglib-2.0.so.0
#19 gst_init_check
from /usr/lib/libgstreamer-0.10.so.0
#20 gst_init
from /usr/lib/libgstreamer-0.10.so.0
#21 main
#0 __kernel_vsyscall

Comment 1 palfrey 2006-12-27 17:40:54 UTC

gstreamer issue

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 2 palfrey 2006-12-27 17:41:24 UTC

*** Bug 390020 has been marked as a duplicate of this bug. ***

Comment 3 Jonathon Jongsma 2007-01-02 21:46:30 UTC

*** Bug 392018 has been marked as a duplicate of this bug. ***

Comment 4 Tim-Philipp Müller 2007-01-30 11:13:04 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!

Hard to say what the problem is here. Since it's in gst_init(), I'll just blame it on late gthread init and memory corruptions for now. Stack trace isn't detailed enough and doesn't really make sense. There's one or two other things that could have caused memory corruptions that have been fixed in CVS, so closing for now until someone can either reproduce this with a current version or provide a more detailed stack trace.

Comment 5 Pedro Villavicencio 2007-04-20 00:27:11 UTC

*** Bug 431512 has been marked as a duplicate of this bug. ***

Comment 6 Pedro Villavicencio 2007-04-21 01:52:19 UTC

*** Bug 431640 has been marked as a duplicate of this bug. ***

Comment 7 palfrey 2007-04-30 14:40:12 UTC

*** Bug 420627 has been marked as a duplicate of this bug. ***

Comment 8 palfrey 2007-04-30 14:46:08 UTC

*** Bug 431511 has been marked as a duplicate of this bug. ***

Comment 9 palfrey 2007-05-09 11:18:42 UTC

*** Bug 436868 has been marked as a duplicate of this bug. ***

Comment 10 Philip Withnall 2007-07-26 05:04:22 UTC

*** Bug 458717 has been marked as a duplicate of this bug. ***