← Back to team overview

me-tv-development team mailing list archive

[Bug 190291] Re: GThread system may only be initialized once

 

Whew, how fast time can pass at times ... and yeah, gstreamer is not
there *yet*.

Unfortunately, there has not been shed more light on this issue since
when I reported it. The repository maintainers told me that this must be
resolved, before they would approve my package. I was checking out 0.6
this afternoon, but there seems to be a runtime problem with glibmm (at
least on my main machine). I'll open up another report for this specific
issue.

I hope 0.6 will no longer cause any threading problems of this kind. As
we found out earlier, input_gnome_vfs is/was the culprit here, and with
the introduction of gio the former is obsolete anyways.

-- 
GThread system may only be initialized once
https://bugs.launchpad.net/bugs/190291
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.

Status in Me TV, it's TV for me computer: Incomplete

Bug description:
Hi,

I'm failing to launch me-tv (0.5.9) on a Fedora (8) machine. Me-tv will crash everytime due to some threading issue. All this happens on a dual core2 intel machine, with a non-64 bit  2.6.23.14 kernel. Gnome is at 2.20.2, GTK2 at 2.12.5. All dependencies at compile-time were met - or at least autogen / gcc did never complain about anything missing. 

Description of problem:
The main window appears, but soon after the application crashes. There is no way to interact with the application before the crash takes place. From what I can tell it has something to do with GThread, but I haven't had the time yet to digg any deeper. Started from the command line, me-tv will last output "GThread-ERROR **: GThread system may only be initialized once. aborting... " before crashing. Detailed Debuginfo file is attached. 

How to reproduce:
Launch me-tv (may have to create initial config files)
Wait for Main Window to appear
App will crash 

I'll gladly provide any further information needed to resolve this issue. 

Cheers,

Matthias