Thank you Javier for reporting and digging into it. It should affect everybody but strangely not much people are complaining about it here. I tried the workaround you pointed out, it only works in the environment that is not expecting ibus inputs. I.e., launching cromium-browser from xterm that does not accept ibus input would work, yet launching cromium-browser from rxvt that does takes ibus inputs would fail, and eventually freeze the whole system.
Although the new google Aura graphics stack is a good thing, I do agree that it's too early for Canonical to enable Aura in Chromium 34 in Ubuntu 14.04, because even the official Google Chrome 34 is released with Aura disabled. Instead of going 35 (or better? 36), I've concluded that *for me*, the *safest* way is to uninstalled chromium for 14.04 and download chrome from google -- https://www.google.com/chrome/browser/?platform=linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308125 Title: ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
