WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: glib error  (Read 2532 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14819
glib error
« on: May 07, 2012, 04:23:56 AM »
There are many references to this error (or something close to it) in google, but it's not at all clear to me where it originates:

With rygel/gupnp-tools when attempting to view a streamed video:
Code: [Select]
(rygel:8566): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed
..and something very similar happens when playing streamed music with rhythmbox, in both cases the application hangs. This didn't used to happen, but I'm not sure which of the glib/gtk/gstreamer/ffmpeg extensions causes it.

Does anybody have an idea where the fix might lie?

Offline AmatCoder

  • Full Member
  • ***
  • Posts: 179
    • AmatCoder Projects
Re: glib error
« Reply #1 on: May 10, 2012, 05:14:18 AM »
I can not reproduce it here (with rhythmbox), but I think that these errors are related to dbus/dbus-glib...


Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: glib error
« Reply #2 on: May 10, 2012, 05:18:13 AM »
Google said it's a bug in the app.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14819
Re: glib error
« Reply #3 on: May 10, 2012, 05:26:05 AM »
..but what I can't figure out (from google) is which app?

The version of rygel in the repo works, but if I compile the lastest rygel (and deps), it fails with this error.
« Last Edit: May 10, 2012, 05:27:36 AM by Juanito »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: glib error
« Reply #4 on: May 10, 2012, 06:27:04 AM »
Whichever app has the assert, of course :) Rygel in this case.
The only barriers that can stop you are the ones you create yourself.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14819
Re: glib error
« Reply #5 on: May 15, 2012, 12:46:41 PM »
Hmm - with the latest updates to the gst-* and ffmpeg extensions, the problem seems to have gone away.