Comment 71 for bug 185311

Revision history for this message
Stunts (f-pinamartins) wrote :

I'm getting something similar when running openoffice.org in ubuntu 8.04 AMD64:

Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7f26e6fd397c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x15) [0x7f26e6fd3a15]
#2 /usr/lib/libX11.so.6 [0x7f26eac9d323]
#3 /usr/lib/libX11.so.6(XCreateWindow+0x44) [0x7f26eac94d54]
#4 /usr/lib/libgdk-x11-2.0.so.0(gdk_window_new+0x395) [0x7f26e6b7dc05]
#5 /usr/lib/libgtk-x11-2.0.so.0 [0x7f26e220c4c8]
#6 /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x10f) [0x7f26e6011bcf]
#7 /usr/lib/libgobject-2.0.so.0 [0x7f26e6025386]
#8 /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x875) [0x7f26e60270d5]
#9 /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f26e6027483]
#10 /usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0x77) [0x7f26e21fd957]
#11 /usr/lib/openoffice/program/libvclplug_gtk680lx.so [0x7f26e25b576d]
#12 /usr/lib/openoffice/program/libvclplug_gtk680lx.so [0x7f26e25b616a]
#13 /usr/lib/openoffice/program/libvclplug_gtk680lx.so [0x7f26e25b682b]
#14 /usr/lib/openoffice/program/libvclplug_gtk680lx.so [0x7f26e258ef64]
#15 /usr/lib/openoffice/program/libvcl680lx.so [0x7f26ee53a4ed]
#16 /usr/lib/openoffice/program/libvcl680lx.so [0x7f26ee4cf322]
#17 /usr/lib/openoffice/program/libvcl680lx.so(_ZN9TabDialogC2EP6WindowRK5ResId+0x5f) [0x7f26ee50c1cf]
#18 /usr/lib/openoffice/program/libsvx680lx.so [0x7f26dac3b084]
#19 /usr/lib/openoffice/program/libsvx680lx.so [0x7f26dae0fdb4]

However, as I stated in bug #240911, which was marked a duplicate of this one, I have managed a few work arounds, that turn out not to be perfect, but do the trick:

1. sudo apt-get remove openoffice.org-gtk
    This will make openoffice look disgruntled from the rest of the theme in your desktop. It will also provoke other bugs such as oo.org impress in fulscreen staying behind the gnome panel
2. Create a new user account and run oo.org.
    It will run fine on my machine, even with openoffice.org-gtk package installed.
3. Run as sudo
    I know this should not be done, but for testing purposes, I tried it and it worked flawlessly...

Any better solutions?