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 640771 - amarok doesn't start with new phonon gstreamer
amarok doesn't start with new phonon gstreamer
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.32
Other Linux
: Normal blocker
: 0.10.33
Assigned To: Tim-Philipp Müller
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-27 22:19 UTC by biasquez
Modified: 2011-02-03 18:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
dbg log (1.03 KB, application/x-bzip)
2011-01-28 07:43 UTC, biasquez
Details
strace log (35.52 KB, application/x-bzip)
2011-01-28 07:46 UTC, biasquez
Details

Description biasquez 2011-01-27 22:19:11 UTC
hi, i have kde 4.6.0, amarok 2.4 and phonon/phonon backend gstreamer 4.4.4
when i launch amarok, i have this error:

KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work 

amarok: BEGIN: App::App() 
amarok: BEGIN: void App::continueInit() 
amarok: BEGIN: EngineController::EngineController() 
amarok: END__: EngineController::EngineController() [Took: 0s] 
amarok: BEGIN: void EngineController::initializePhonon() 

(amarok:4937): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
Comment 1 Tim-Philipp Müller 2011-01-27 22:32:31 UTC
What makes you think this is due to a bug in GStreamer (rather than amarok or phonon or phonon-gstreamer)?

The GStreamer-critical shouldn't have any adverse side effects (but looks like a bug in some component using GStreamer, not GStreamer itself).
Comment 2 biasquez 2011-01-27 22:43:36 UTC
see these bug reports:

https://bugs.kde.org/show_bug.cgi?id=264428
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/708508

moreover, in this forum: http://forum.kde.org/viewtopic.php?f=115&t=92892&p=186216#p186216

>biasquez, I've been talking with the developer of Phonon and phonon-gst. He says >that this is triggered by a bug in Gstreamer itself, and should be reported as a >bug against Gstreamer. https://bugzilla.gnome.org/enter_bug.cg ... =GStreamer is >where their bugzilla lives.
>
>It will help us all out if you take the time to report the bug, and work with >the gst developers to fix it.
>
>Thanks!


now, i don't know how i can debug and report better this issue..
Comment 3 Tim-Philipp Müller 2011-01-27 23:13:01 UTC
Well, what can I say. It's not clear to me at all that this is triggered by a bug in GStreamer itself. I'd love to hear some more details that support this claim (other than that warning, which shouldn't be fatal unless the G_DEBUG environment variable is set to fatal_warnings).

Could you do this:

a) start amarok from the command line like this:

   $ GST_DEBUG=*:5  amarok  2>dbg.log
   ... wait for it to exit ..
   $ bzip2 dbg.log

and attach the dbg.log.bz2 file to this bug report?


b) start amarok like this:

  $ strace -f amarok 2>strace.log
  ... wait for it to exit ..
  $ bzip2 strace.log.bz2

and attach the strace.log to this bug report?

Thanks!
Comment 4 biasquez 2011-01-28 07:43:46 UTC
Created attachment 179492 [details]
dbg log
Comment 5 biasquez 2011-01-28 07:46:51 UTC
Created attachment 179493 [details]
strace log

note: creating strace log, after 2 minutes, process hangs up and i closed it with ctrl+c
Comment 6 Tim-Philipp Müller 2011-01-28 12:10:28 UTC
The stack trace and logs in https://bugs.kde.org/show_bug.cgi?id=264428 indicate that the warning is triggered by this code in _gst_debug_init():

  /* we need to use the publicly visible address, so that one could remove it by
   * the same address */
  {
    GModule *module = g_module_open (NULL, 0);
    gpointer ptr;

    g_module_symbol (module, "gst_debug_log_default", &ptr);
    gst_debug_add_log_function (ptr, NULL);
    g_module_close (module);
  }

We need to get rid of all that and solve this properly.


biasquez: what is the output of:

  $ printenv | grep G_DEBUG

on your system? Does amarok start like this:

  $ G_DEBUG=  amarok

?
Comment 7 biasquez 2011-01-28 12:19:16 UTC
omega@omg-lin:~$ printenv | grep G_DEBUG
omega@omg-lin:~$
Comment 8 Tim-Philipp Müller 2011-02-03 11:17:57 UTC
Should be fixed in git now. Apologies for the breakage.

If you're an ubuntu user, you might want to consider using the GStreamer PPA. That way you will automatically get the pre-releases and we can discover such things before the final release. 


commit 74ff936752fdb8715bcafb7560726fbe4d0438ae
Author: Tim-Philipp Müller <tim.muller@collabora.co.uk>
Date:   Thu Feb 3 10:28:01 2011 +0000

    Revert "info: use the publicly visible address to fix the tests"
    
    This reverts commit eb56687a6dfd207507a4ca000eae53f93b5e33ea.
    
    While this commit may have fixed a problem on one of the build bots,
    it didn't actually fix the original bug reported for win32.
    
    Also, it causes other problems, such as the lookup failing when
    called from C++ code (gst-phonon, amarok).
    
    This needs to be fixed differently.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=640771
    https://bugzilla.gnome.org/show_bug.cgi?id=625396
Comment 9 biasquez 2011-02-03 18:24:57 UTC
i'm using kubuntu natty, gstreamer ppa doesn't support natty... thanks :)