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 357560 - Hangs at "initialising player engine"
Hangs at "initialising player engine"
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other All
: Normal critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-25 06:36 UTC by Jeff Supodsson
Modified: 2006-10-04 10:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeff Supodsson 2006-09-25 06:36:14 UTC 
Steps to reproduce:
1. Run banshee

Stack trace:

+ Trace 73174

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #3 g_option_context_parse
    from /usr/lib/libglib-2.0.so.0
  • #4 gst_init_check
    from /usr/lib/libgstreamer-0.10.so.0
  • #5 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #6 gstreamer_initialize
    from /usr/lib/banshee/libbanshee.so
  • #7 (wrapper managed-to-native) Banshee.Gstreamer.Utilities:gstreamer_initialize
  • #8 ??
  • #9 Banshee.Gstreamer.Utilities:Initialize
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ?? 


Other information:
Comment 1 Aaron Bockover 2006-09-25 19:24:15 UTC 
This looks to be a GStreamer problem in gst_init.
Comment 2 Tim-Philipp Müller 2006-09-25 22:56:59 UTC 
 - what core version exactly?

 - does this also happen with the core version 0.10.9 or 0.10.10 or CVS
   and the environment variable GST_REGISTRY_FORK set to 'no' ?

 - could you attach a debug log, starting banshee with

    $ GST_DEBUG=*:5 banshee 2>dbg.log

   from a command line?
Comment 3 Tim-Philipp Müller 2006-09-28 12:01:50 UTC 
Ping?
Comment 4 Tim-Philipp Müller 2006-10-04 10:02:35 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!