Bug 264428 - amarok doesn't start with new phonon gstreamer
Summary: amarok doesn't start with new phonon gstreamer
Status: RESOLVED UPSTREAM
Alias: None
Product: phonon-backend-gstreamer
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-27 10:00 UTC by omega
Modified: 2011-04-27 21:19 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
first log (4.91 KB, application/octet-stream)
2011-01-28 08:42 UTC, omega
Details
second log (8.23 KB, text/x-log)
2011-01-28 08:42 UTC, omega
Details

Note You need to log in before you can comment on or make changes to this bug.
Description omega 2011-01-27 10:00:13 UTC
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

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:5012): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed

and amarok doesn't start

Reproducible: Didn't try
Comment 1 Harald Sitter 2011-01-27 15:32:03 UTC
Well, since that is an assert in gstreamer there isn't much we can do about that... please report the issue there.
Comment 2 Tim-Philipp M 2011-01-28 00:15:02 UTC
> Well, since that is an assert in gstreamer there isn't much we can do about
> that...

Hi, GStreamer developer here. This assertion shouldn't be fatal unless G_DEBUG=fatal_warnings is set (in which case it will abort with a message saying so). Also, it's most likely caused by a bug in a library or application using GStreamer. The exact caller can be tracked down running the application in gdb with the G_DEBUG=fatal_warnings environment variable set and then getting a stack trace when it aborts.

However, as I said, this shouldn't be fatal under normal circumstances, so I'm not sure what's going on here or that the application not starting actually has something to do with GStreamer.
Comment 3 Harald Sitter 2011-01-28 00:27:12 UTC
Curious, I did not know that those are not critical by default, good to know though. Thanks.

Well, lets get some debugging going then.

omega, please run kdebugdialog and select everything, then apply and exit the app again.
On a terminal run the following:

export PHONON_PULSEAUDIO_DEBUG=5
export PHONON_GST_DEBUG=5
export PHONON_GST_GST_DEBUG=3
export PHONON_DEBUG=5

and finally start amarok from that terminal using

amarok --nofork --debug 2> log

That will spit a log file in the present working directory, please attach it to this bug.

Additionally it would be good to find the root of that assert, so please also do the following in a terminal:

export G_DEBUG=fatal_warnings
gdb --args amarok --nofork

At some point this will terminate (i.e. when the assert is printed), then type

bt

this will spit out a couple of lines, please also save those in a file and attach them to this bug report.

(you can then leave gdb by entering quit ;))
Comment 4 omega 2011-01-28 08:42:18 UTC
Created attachment 56556 [details]
first log
Comment 5 omega 2011-01-28 08:42:43 UTC
Created attachment 56557 [details]
second log
Comment 6 Tim-Philipp M 2011-01-28 13:04:25 UTC
Ok, the stack trace shows that the GStreamer-critical is actually triggered from within GStreamer, so that's a GStreamer bug then.

The log in the GStreamer bug report (https://bugzilla.gnome.org/show_bug.cgi?id=640771) also shows that it's aborting due to the warning, so I suspect ubuntu or the user has G_DEBUG=fatal_warnings set for some reason, but in any case, it's clear now that it does abort because of the warning:

> GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
> aborting...

So this can be closed after all and we'll continue this in the GStreamer bug tracker (sorry for the noise).

Thanks for providing the logs omega.
Comment 7 Harald Sitter 2011-01-28 13:06:09 UTC
Thank you :)
Comment 8 omega 2011-02-03 19:24:39 UTC
you're welcome :)
Comment 9 Myriam Schweingruber 2011-04-27 21:19:10 UTC
reassigning to the new bugzilla product for better bug tracing of the various backends. Sorry for the noise.