Bug 206885

Summary:	GnomeBaker fails to start - GThread error
Product:	[Fedora] Fedora	Reporter:	Peter Gordon <peter>
Component:	gnomebaker	Assignee:	Brian Pepple <bdpepple>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	extras-qa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.6.0-1.fc6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-09-18 16:14:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Peter Gordon 2006-09-17 18:37:31 UTC

Description of problem:
GnomeBaker will not start. It gives me the following error message when I
attempt to run it from a console:

[peter@tuxhugger ~]$ gnomebaker 
GTK Accessibility Module initialized

GThread-ERROR **: GThread system may only be initialized once.
aborting...
Aborted

The GDB backtrace doesn't give much more than that either, unfortunately:
(gdb) run
Starting program: /usr/bin/gnomebaker 
[Thread debugging using libthread_db enabled]
[New Thread -1208494384 (LWP 30370)]
GTK Accessibility Module initialized

GThread-ERROR **: GThread system may only be initialized once.
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1208494384 (LWP 30370)]
0xb7fa5402 in __kernel_vsyscall ()


Version-Release number of selected component (if applicable):
gnomebaker-0.5.1-5.fc6


How reproducible:
Always


Steps to Reproduce:
1. Install gnomebaker 0.5.1-5.fc6
2. Attempt to run it
  
Actual results:
GnomeBaker aborts immediately.

Expected results:
It should open the application. :)

Additional info:
This is on my Fedora Development workstation at home, up-to-date as of this morning.

Comment 1 Brian Pepple 2006-09-18 16:06:02 UTC

Are you experiencing this problem with the latest release (0.6.0)?

Comment 2 Peter Gordon 2006-09-18 16:14:33 UTC

Brian, I just updated to 0.6.0 this morning and am no longer experiencing this
issue. Thanks!