Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gdk: gdk_window_set_user_time called on non-toplevel with Dartium 34 #17987

Closed
DartBot opened this issue Apr 2, 2014 · 5 comments
Closed

Gdk: gdk_window_set_user_time called on non-toplevel with Dartium 34 #17987

DartBot opened this issue Apr 2, 2014 · 5 comments
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@DartBot
Copy link

DartBot commented Apr 2, 2014

This issue was originally filed by javiersma...@gmail.com


What steps will reproduce the problem?

  1. Run Dartium from terminal
  2. Go to www.google.com (for example)
  3. When entering text in an input element an error pops in the console and can't write more. Not even in the omnibar at a new tab.

What is the expected output? What do you see instead?
Expected to continue working :). I see: I can't enter any text.

What version of the product are you using? On what operating system?
Just downloaded the beta version, Dartium version: 34.0.1847.0 aura (258268)
OS: Up to date Kubuntu 14.04 64 bits

Please provide any additional information below.
Tried stable (Dartium 33), all works.

The error show in console:

[7291:7291:0402/223917:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

[7291:7291:0402/223917:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

javi@litio:~/installs/dart/chromium$ ./chrome
[7392:7392:0402/224214:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

[7392:7392:0402/224214:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

I get one error per key pressed short after the first error shows up.

@anders-sandholm
Copy link
Contributor

Not sure I resolved Area properly.
Pls. reassign as you see fit.


Added Area-HTML, Triaged labels.

@blois
Copy link
Contributor

blois commented Apr 7, 2014

Removed Area-HTML label.
Added Area-Dartium label.

@DartBot
Copy link
Author

DartBot commented Apr 14, 2014

This comment was originally written by gary.trak...@gmail.com


Same problem here: https://code.google.com/p/chromium/issues/detail?id=360388

@a-siva
Copy link
Contributor

a-siva commented Apr 14, 2014

This seems to be a regular Chromium issue when used with Kubuntu 14.04
(see https://code.google.com/p/chromium/issues/detail?id=360388).

I don't see the issue locally (my machine is running Ubuntu 12.04).


Marked this as being blocked by #360388.

@DartBot
Copy link
Author

DartBot commented Apr 25, 2014

This comment was originally written by javier...@gmail.com


A workaround is given at the chromium issue thread. https://code.google.com/p/chromium/issues/detail?id=360388#c48.

I also worked on dartium (34.0.1847.0)

@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

6 participants