Skip to content
This repository has been archived by the owner on Aug 20, 2020. It is now read-only.

Adapt to the latest master branch #430

Closed
wants to merge 2 commits into from

Conversation

zoltan-ongithub
Copy link
Contributor

Tested with the latest Chromium master branch on an ARMv8 build with Mesa and Wayland 1.9.

@kalyankondapally
Copy link
Contributor

LGTM
@joone ping

@joone
Copy link
Contributor

joone commented Nov 3, 2015

@kuscsik what latest commit of Chromium did you test with your changes?

@kalyankondapally
Copy link
Contributor

@joone Thanks
@kuscsik You need to update chromium revision here https://github.com/01org/ozone-wayland/blob/master/.DEPS.git

@zoltan-ongithub
Copy link
Contributor Author

@joone @kalyankondapally Updated the .DEPS.git file as requested.

@kalyankondapally
Copy link
Contributor

For some reason, keyboard input seems to be broken.

[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No current XKB state

@zoltan-ongithub
Copy link
Contributor Author

I tested the patch set only with a mouse. I can reproduce the issue with
Mesa 11.
Seem like an issue with the XKB initialisation.

Z

On Wed, Nov 4, 2015 at 7:28 PM, kalyan kondapally notifications@github.com
wrote:

For some reason, keyboard input seems to be broken.

[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102321:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state
[6155:6155:1104/102322:ERROR:xkb_keyboard_layout_engine.cc(845)] No
current XKB state


Reply to this email directly or view it on GitHub
#430 (comment).

@joone
Copy link
Contributor

joone commented Nov 6, 2015

I saw the same keyboard problem.

@joone
Copy link
Contributor

joone commented Nov 7, 2015

I submitted a patch to fix the keyboard problem.

@kalyankondapally
Copy link
Contributor

Merged

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants