Bug 84034 - input-method.xml has a factory for wl_keyboard causing version conflict
Summary: input-method.xml has a factory for wl_keyboard causing version conflict
Status: RESOLVED MOVED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-18 09:23 UTC by Pekka Paalanen
Modified: 2018-06-08 23:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Pekka Paalanen 2014-09-18 09:23:43 UTC
Request wl_input_method_context.grab_keyboard creates a new wl_keyboard object.

wl_seat.get_keyboard is the primary request for creating wl_keyboard objects.

This causes a runtime interface versioning conflict.

wl_keyboard in core is already at version 4, but you can only create wl_keyboard version 1 via wl_input_method_context. You cannot bump wl_input_method_context version without starting to get wl_keyboards of higher version. The major problem comes, when you bump input-method interface version beyond what is currently the highest version of wl_seat, and then someone adds a new thing to wl_keyboard. Input-method would start dealing out wl_keyboards automatically with a version claiming to support the new thing without clients or servers ever implementing the support.

wl_input_method_context.grab_keyboard should not be creating objects of type wl_keyboard, but the type should be unique for wl_input_method_context.
Comment 1 Jan Arne Petersen 2015-01-22 06:27:01 UTC
Yes that would be better.
Comment 2 GitLab Migration User 2018-06-08 23:53:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/54.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.