actually it is not an issue with libxcb, it is an issue with the broken application, in this case either gtk/gdk or openoffice itself and thus it should not be closed or making a duplicate of any other xcb assertion related bugs.
workaround could be to recompile xcb so that it does not abort when locking braindamage is done, however such approach is *definitely* wrong.
actually it is not an issue with libxcb, it is an issue with the broken application, in this case either gtk/gdk or openoffice itself and thus it should not be closed or making a duplicate of any other xcb assertion related bugs.
workaround could be to recompile xcb so that it does not abort when locking braindamage is done, however such approach is *definitely* wrong.