Ubuntu
chromium-browser package

  1. Bug #523915
  2. Comment #7

Comment 7 for bug 523915

Revision history for this message
darvids0n (darvids0n-deactivatedaccount) wrote :

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.