Seems like the resolution for this is to either backport the GTK fix to 2.18.x or bring the base package up to 2.19 series. Doesn't look like a Chromium bug imo, if we're passed a bad xid to our own window then something lower-level has stuffed up.
-- chromium-browser crashed with signal 5 in gdk_x_error() https://bugs.launchpad.net/bugs/523915 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
