I understand that Gutsy is not "stable" yet. :) I am just trying to help by validating this bug's importance for resolution.
Handling the error better is a good starting point, but ideally someone who knows the inner workings of GLib or one of the libraries that calls to it can isolate the bug and either update GLib or clearly state what libraries/apps are doing wrong now (i.e., what needs to change to be compatible with newer version of GLib). On 7/5/07, Sebastien Bacher <[EMAIL PROTECTED]> wrote: > > 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 > > -- > [gutsy] GSlice: g_thread_init() Warning messages > https://bugs.launchpad.net/bugs/116870 > You received this bug notification because you are a direct subscriber > of the bug. > -- [gutsy] GSlice: g_thread_init() Warning messages https://bugs.launchpad.net/bugs/116870 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
