Support french keyboard layout #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With this patch we add support to run DRM-backend tests locally in the test suite. For now this won't work in the CI, as there are no cards available. But the plan is to achieve this by using VKMS (virtual KMS) in the future. To run DRM-backend tests locally, first of all the user has to set the environment variable WESTON_TEST_SUITE_DRM_DEVICE to 'card0', 'card1' or any other device where he wants to run the tests. Also, for now it only works if it is run as root, but in the future this problem will be solved. The tests will run on a non-default seat. The reason for that is that we want to avoid opening input devices unnecessarily. Also, since DRM-backend usage requires gaining DRM master status on a DRM KMS device, nothing else must be using the device at the same time. To achieve this we use a lock to run the DRM-backend tests sequentially. Signed-off-by: Leandro Ribeiro <[email protected]>
This adds the first DRM-backend test. It is very simple and was made in order to make easier to add more complex DRM-backend tests in the future. Signed-off-by: Leandro Ribeiro <[email protected]>
cms-colord uses cms-helper functions which require lcms2. Therefore, lcms2 must be added as a build dependency. Signed-off-by: Guillaume Champagne <[email protected]>
The missing build dependency was added. The override to disable this check can be removed. Signed-off-by: Guillaume Champagne <[email protected]>
This moves the creation of the blob to be earlier, to when the damage is calculated. It replaces the damage tracked inside of the plane state with the blob id itself. This should stop creating new blob ids for TEST_ONLY commits, and them being leaked in general, as the blob ids are now freed with the plane state. The FB_DAMAGE_CLIPS property is now always set if it's supported, and will be 0 in the case that we have no damage information, which signifies full damage to the kernel. Signed-off-by: Scott Anderson <[email protected]>
When there's neither configless nor surfaceless EGL extension
(i.e. not a Mesa driver), Weston falls back to a dummy pbuffer surface.
Weston attempts to find for that surface an EGL config but uses a NULL
array of pixel formats. This fails with the following messages:
EGL_KHR_surfaceless_context unavailable. Trying PbufferSurface
Found an EGLConfig matching { pbf; } but it is not usable because
neither EGL_KHR_no_config_context nor EGL_MESA_configless_context
are supported by EGL.
failed to choose EGL config for PbufferSurface
EGL error state: EGL_SUCCESS (0x3000)
Failed to initialise the GL renderer;
Signed-off-by: Tomek Bury <[email protected]>
Surface roles are permanent, so it should not be cleaned up. Fixes: #409 weston: ../libweston/compositor.c:4094: weston_surface_set_role: Assertion `role_name' failed. Signed-off-by: James Hilliard <[email protected]>
As in some circumstances there could be no output connected, avoid retrieving the width/height of the output if none was found/connected. Fixes: #384 Signed-off-by: Marius Vlad <[email protected]>
Fix the following build warning by moving the 'seals' declaration inside the
HAVE_MEMFD_CREATE guard:
../shared/os-compatibility.c: In function ‘os_ro_anonymous_file_get_fd’:
../shared/os-compatibility.c:341:6: warning: unused variable ‘seals’ [-Wunused-variable]
int seals, fd;
^
Signed-off-by: Frank Binns <[email protected]>
Launcher-direct does not allow us to run using a different seat from the default seat0. This happens because VTs are only exposed to the default seat, and users that are on non-default seat should not touch VTs. Add check in launcher-direct to skip VT/tty management if user is running on a non-default seat. Signed-off-by: Leandro Ribeiro <[email protected]>
In order to run DRM-backend tests, a DRM-device is needed. As we do not necessarily have control of the hardware that is going to run our tests in GitLab CI, DRM-backend tests were being skipped. This patch add support to run the tests using VKMS (virtual KMS). To achieve this, virtualization is needed, as we need to run a custom kernel during the CI job. We've decided to go with virtme, as it is simpler to setup and works good for our use case. Signed-off-by: Leandro Ribeiro <[email protected]>
we don't need to get the weston_config object before zalloc success.
…ails This adds a NULL check to fail when frame_create fails. This can happen crash in frame_resize_inside function if frame is NULL.
The core Wayland protocol explicitly states that wl_keyboard.modifiers must be send after wl_keyboard.enter. This commit also changes the behavior of `seat_get_keyboard` to not send `wl_keyboard.modifiers` in case where seat had pointer focus, but not keyboard one. Signed-off-by: Kirill Chibisov <[email protected]>
There's a log that advertises support for universal planes. That can make users think there's something wrong with Weston or their systems when universal planes are not supported, but that's not the case. Remove this log from the code. Signed-off-by: Leandro Ribeiro <[email protected]>
kiosk-shell is fullscreen shell for apps that use the xdg-shell protocol. The goal is to make life easier for people shipping embedded devices with simple fullscreen shell requirements, and reduce the proliferation of desktop-shell hacks. Top level surfaces are made fullscreen, whereas dialogs are placed on top in the center of the output and retain their natural sizes. Dialogs can be moved and (un)maximized, but resizing is currently not supported. An app can be directed to a particular output by populating the "app-ids" field with the app's XDG app id, in the relevant "[output]" section in the weston config file. Fixes: #277 Signed-off-by: Alexandros Frantzis <[email protected]>
These functions are all declared twice in the same file. Remove on of the two declarations. Signed-off-by: Michael Olbrich <[email protected]>
…_scene_view_print() Currently the debug output for 'drm-backend' can be confusing. In the output of debug_scene_view_print() views may be listed as 'not opaque' but later, during plane assignment, other views underneath such a view is reported as 'occluded on our output'. This happens because weston_view_is_opaque() has some extra checks to determine if a view is fully opaque, such as 'is_opaque' provided by the renderer for formats that have no alpha channel. Use weston_view_is_opaque() in debug_scene_view_print() as well to get more accurate results. Signed-off-by: Michael Olbrich <[email protected]>
…e_damage() compositor_accumulate_damage() is called for each output during repaint. The DRM backend will only set keep_buffer for the surfaces that are visible on the current output. So a buffer_ref is released that may still be needed. When the output that shows the surface is repainted, the buffer_ref is gone and the surface cannot be put on a plane. Ignore all surfaces that are not visible on the current output to avoid this. Signed-off-by: Michael Olbrich <[email protected]>
The refcount is not zero if the corresponding buffer is attached to multiple surfaces. Signed-off-by: Michael Olbrich <[email protected]>
after calling malloc() , be sure to determine whether the allocating for memory space is successful Signed-off-by: ganjing <[email protected]>
weston-info is now deprecated in favor of wayland-info which is part of wayland-utils. Add a note to weston-info to inform users that weston-info is deprecated and will be removed soon. Signed-off-by: Olivier Fourdan <[email protected]>
Introduce a helper function to reset the current state of a drm_plane. Signed-off-by: Alexandros Frantzis <[email protected]>
When dissociating a universal plane from a crtc, we currently don't reset the current state of the plane (plane->state_cur). When attempting to use this plane in the future, we can run into invalid memory accesses due to left over associations with potentially freed drm backend objects. This commit resets the state of the scanout and cursor universal planes associated with a crtc. The following scenario exhibits the problem: 1. Start a (fullscreen) client that is suitable for and assigned to the scanout plane. The plane's state_cur->output value is set. 2. Unplug the monitor: the scanout plane is "released" but still maintains the state_cur->output association. 3. Replug the monitor: the plane is deemed unavailable due to an existing, albeit invalid, state_cur->output value. Note the memory errors trying to access the drm_output which was freed at step (2). Signed-off-by: Alexandros Frantzis <[email protected]>
If a surface is not visible, then is does not matter if the view is on multiple outputs. It will be skipped anyways when the output is rendered. So check first if the surface is acually visible on the output before doing any checks that might force rendering. This avoids unnecessary rendering. Signed-off-by: Michael Olbrich <[email protected]>
The opaque region of a weston view is updated only if the alpha value is 1 and the transform matrix is of type WESTON_MATRIX_TRANSFORM_TRANSLATE. While using ivi-shell, opaque region is never updated, as we are performing scaling operations to the view transform matrix, even when the scaling factor is 1 and thereby changing the type to WESTON_MATRIX_TRANSFORM_SCALE. Perform scaling of the view transformation matrix only when the scaling factor is non-zero. Signed-off-by: Rajendraprasad K J <[email protected]>
…abled The pipewire plugin uses this API as well, not just the remoting plugin. So enable it if either is enabled. And disable pipewire in the no-gl-renderer CI build. The virtual outputs don't work without it. Signed-off-by: Michael Olbrich <[email protected]>
…tputs Building fails without it. So don't just warn about it but fail immediately. Signed-off-by: Michael Olbrich <[email protected]>
* rdp shell: add icon search retry * misc fixes * misc fixes * misc fixes Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <[email protected]>
…ted (#128) Co-authored-by: Hideyuki Nagase <[email protected]>
…ouse is moved (#130) * libweston-desktop: xwayland window is not visible upon commit * check XWAYLAND state instead of relying on added Co-authored-by: Hideyuki Nagase <[email protected]> Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
* sync window state with client * state transition between fullscreen and maximized * clear local move pending if mouse move is reported --------- Co-authored-by: Hideyuki Nagase <[email protected]>
…ible (#132) * send minmax info when window become visible * apply coordinate translation to min/max info * make minmax debug message verbose --------- Co-authored-by: Hideyuki Nagase <[email protected]> Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
* support window unsnap by keyboard shortcut and mouse * resize either from left or right at unsnap * report snap support to client --------- Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
* default to us keyboard when no layout * add Chinese Traditional Bopomofo language profile * add workaround for Windows 10 setting extended bit for right shift key --------- Co-authored-by: Hideyuki Nagase <[email protected]> Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
…ent (#137) Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
…ilure response to display loop (#138) Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
* draft: support window snap with no gap * no gap snap with window shadow enabled * adjust window unsnap position by pointer grab * unsnap only if when pointer is actually moved * adjust window unsnap position with window geometry * restore window (not back to snap) after snap->maximized->unmaximized * adjust debug message --------- Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3> Co-authored-by: Hideyuki Nagase <[email protected]>
* support restore from maximized by grabbing titlebar * adjust debug message --------- Co-authored-by: Hideyuki Nagase <[email protected]>
Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
* rdp backend: do not force us layout Do not force "us" layout when no xkb mapping is found. Weston will this way fallback to the keymap defined in compositor xkb_names which falls back to "us" if no layout is defined in weston.ini. * rdp backend: reset default keymap if mapping fails Reload default global compositor keymap when no xkb mapping is found for current keyboard layout. This will default to the keymap in weston.ini or to "us" if no keymap is defined there. Should allow to use custom KLC layouts for keymaps that exist in Linux but have no correspondence in Windows (e.g. altgr-intl). This should also partially fix #173. Still need a way to export weston.ini to the user.
* SVG rendering at system-distro name space * move fclose call --------- Co-authored-by: Hideyuki Nagase <hideyukn@HIDEYUKN-SB3>
Co-authored-by: Hideyuki Nagase <[email protected]>
* Fix incorrect keyboard variant for Canadian French * Revert "Fix incorrect keyboard variant for Canadian French" This reverts commit 6c70afd. * Fixes the correct entry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.