Gnomebaker doesn't start. It fails with a GThread-ERROR

This bug also exists if compiled from 0.5.1 source

Thanks for your bug report. Could you please try to obtain a backtrace by following the instructions
on http://wiki.ubuntu.com/DebuggingProgramCrash - thanks.

Thanks fpr taking care of this bug. The backtrace looks like this:

---
# gdb gnomebaker

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) run
Starting program: /usr/bin/gnomebaker
[Thread debugging using libthread_db enabled]
[New Thread -1225976128 (LWP 2418)]
GTK Accessibility Module initialized

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

Program received signal SIGABRT, Aborted.
[Switching to Thread -1225976128 (LWP 2418)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 1 (Thread -1225976128 (LWP 2418)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb72fc9a1 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb72fe2b9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7441fa6 in g_logv () from /usr/lib/libglib-2.0.so.0
#4 0xb7441fda in g_log () from /usr/lib/libglib-2.0.so.0
#5 0xb75e0499 in g_thread_init () from /usr/lib/libgthread-2.0.so.0
#6 0x08052567 in main (argc=1, argv=0xbffad394) at main.c:61
(gdb) quit
---

Thanks
 Christoph

Confirm that this bug is still occuring in an up-to-date dapper.

You can "solve" the problem by disabling the accessibility support.

I and many people turn this on, because after you disabled the option /apps/metacity/general/reduced_resources in gconf (to get rid of the - sorry - crappy animation when you minimize/maximize windows), you only see a wire-frame, when you move a windows around. With the accessibility support turned on, windows stay "whole" again while moving them.

http://www.ubuntuforums.org/showpost.php?p=1283681&postcount=2:

--
The problem is gnomebaker is not getting along with the accessibility
module. If accessibility support is not a requirement for you, it can be
disabled with the gconf-editor. The relevant key
is /desktop/gnome/interface/accessibility. Uncheck the box and then
restart your session.
--

Looks like this is fixed. Feel free to reopen this bug report if it's not the case.