97758 2012-09-26 23:32:08 -0700 WebKitGTK 1.10.0 cannot start due to communication error with X 2012-10-03 01:11:44 -0700 1 1 1 Unclassified WebKit WebKit2 528+ (Nightly build) Other Linux RESOLVED INVALID P2 Normal --- 0 cf webkit-unassigned cf cgarcia mrobinson oldest_to_newest 729238 0 cf 2012-09-26 23:32:08 -0700 I have upgraded to WebKitGTK 1.10.0, however, when I start it I get the following: Acquired a message bus connection (II) pvr(0): gdlHideCursor Xlib: sequence lost (0x10000 > 0xe2) in reply type 0x0! Xlib: sequence lost (0x10000 > 0xe2) in reply type 0x0! Xlib: sequence lost (0x10000 > 0xe2) in reply type 0x0! Xlib: unexpected async reply (sequence 0x1)! Xlib: sequence lost (0x10000 > 0xe2) in reply type 0x0! Seems like some problem with the interaction with X. Have you seen this before? I have tried to run the MiniBrowser from gdb and got the following trace when quiting after the "Xlib: sequence lost (0x10000 > 0xe2) in reply type 0x0!" (gdb) bt #0 0xffffe424 in __kernel_vsyscall () #1 0xb5c96be9 in *__GI___poll (fds=0x8056840, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb451ecfd in _XWaitForReadable (dpy=<optimized out>) at XlibInt.c:503 #3 0xb451f16e in _XRead (dpy=0x80702b8, data=0xbfffe988 "\230\353\377\277\240\353\377\277\234\356\377\277\250\370\377\277", size=2040) at XlibInt.c:1126 #4 0xb451f1e7 in _XEatData (dpy=0x80702b8, n=2359224) at XlibInt.c:2254 #5 0xb451f36d in _XAsyncReply (dpy=0x80702b8, rep=<optimized out>, buf=0xbffff230 "\001", lenp=0xbffffa18, discard=1) at XlibInt.c:1913 #6 0xb4520d07 in _XEventsQueued (dpy=0x80702b8, mode=2) at XlibInt.c:909 #7 0xb450edb8 in XPending (dpy=0x80702b8) at Pending.c:56 #8 0xb61ae0a3 in gdk_check_xpending (display=0x8075810) at gdkeventsource.c:267 #9 0xb61ae11b in gdk_event_source_check (source=0x807d4a8) at gdkeventsource.c:300 #10 0xb5d7a601 in g_main_context_check (context=0x807bc40, max_priority=2147483647, fds=0x81881d8, n_fds=3) at gmain.c:3170 #11 0xb5d7aabd in g_main_context_iterate (context=0x807bc40, block=1, dispatch=1, self=<optimized out>) at gmain.c:3289 #12 0xb5d7affb in g_main_loop_run (loop=0x8189868) at gmain.c:3486 #13 0xb6356403 in gtk_main () at gtkmain.c:1164 #14 0x08051a1f in main () (gdb) Furthermore, I have tried to downgrade webkit to webkit 1.8 again. This gives the same error, so I'm thinking it might be a problem with some of the dependecies that I have upgraded during the webkit upgrade. My upgrades include: GLib -> 2.34.0 GTK+ -> 3.4.4 Pango -> 1.30.1 GDK -> 2.26.4 libsoup -> 2.40.0 GTK+-2.0 -> 2.24.12 Atk -> 2.6.0 729494 1 cf 2012-09-27 06:59:35 -0700 After upgrading a couple of libraries I know get the following: ------------------------------------------------------------------ ** (MiniBrowser:1158): WARNING **: AT-SPI: Could not obtain desktop path or name ** (MiniBrowser:1158): WARNING **: atk-bridge: get_device_events_reply: unknown signature ** (MiniBrowser:1158): WARNING **: atk-bridge: get_device_events_reply: unknown signature ** (MiniBrowser:1158): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature ** (WebKitWebProcess:1167): WARNING **: AT-SPI: Could not obtain desktop path or name ** (WebKitWebProcess:1167): WARNING **: atk-bridge: get_device_events_reply: unknown signature ** (WebKitWebProcess:1167): WARNING **: atk-bridge: get_device_events_reply: unknown signature ** (WebKitWebProcess:1167): WARNING **: atk-bridge: GetRegisteredEvents returned message with unknown signature Xlib: sequence lost (0x100fa > 0x234) in reply type 0x0! Xlib: sequence lost (0x10000 > 0x234) in reply type 0xe! Xlib: sequence lost (0x10000 > 0x76) in reply type 0xe! ------------------------------------------------------------------ I know have these packages: GLib -> 2.34.0 GTK+ -> 3.6.0 Pango -> 1.30.1 GDK -> 2.26.4 libsoup -> 2.40.0 GTK+-2.0 -> 2.24.13 Atk -> 2.6.0 at-spi2-core -> 2.6.0 at-spi2-atk -> 2.6.0 733425 2 cf 2012-10-03 01:11:44 -0700 This bug was related to updating GTK+. The newer version of this only supports Xinput-2 however this was not supported in my setup, therefore each time an Xi2 event occured the application would crash.