there is a workaround described in the bug. The glib2.0 upstream task state they want to make it handle the error better, that will likely happen before for gutsy, you are using an unstable distribution and such bugs happen there
there is a workaround described in the bug. The glib2.0 upstream task state they want to make it handle the error better, that will likely happen before for gutsy, you are using an unstable distribution and such bugs happen there