Bug 437233

I seem unable to use logjam on F9 i386.  Yes, this is your latest build that
disables "unused" threads.  Are they really unused?

[warren@caprica tmp]$ rpm -q logjam
logjam-4.5.3-19.fc9.i386

[warren@caprica tmp]$ logjam

(process:29927): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:29927): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed

GLib-ERROR **: The thread system is not yet initialized.
aborting...
The program 'logjam' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 3340 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
logjam: Fatal IO error 0 (Success) on X server :0.0.
[warren@caprica tmp]$ logjam

(process:29944): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:29944): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed
[warren@caprica tmp]$ logjam

(process:29950): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:29950): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed

GLib-ERROR **: The thread system is not yet initialized.
aborting...
logjam: Fatal IO error 0 (Success) on X server :0.0.
[warren@caprica tmp]$ terminate called after throwing an instance of
'std::out_of_range'
  what():  vector::_M_range_check