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 386711 - crash in Volume Control: I am installed and this ...
crash in Volume Control: I am installed and this ...
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other All
: High critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-17 08:32 UTC by gmstudio
Modified: 2007-01-11 18:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description gmstudio 2006-12-17 08:32:04 UTC 
What were you doing when the application crashed?
I am installed and this was the first boot. The error message appear after login.


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

Memory status: size: 36044800 vsize: 0 resident: 36044800 share: 0 rss: 6373376 rss_rlim: 0
CPU usage: start_time: 1166343896 rtime: 0 utime: 3 stime: 0 cutime:3 cstime: 0 timeout: 0 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 -1226462608 (LWP 4872)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94783

Thread 1 (Thread -1226462608 (LWP 4872))

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






Comment 1


palfrey





          2006-12-17 18:10:50 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 2


palfrey





          2006-12-17 18:11:37 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


Tim-Philipp Müller





          2007-01-11 18:18:30 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!

Not much we can do about this with this stack trace.