Bug 71015 - weston-keyboard (VKB) always pops-up on primary display in multi-head setup
Summary: weston-keyboard (VKB) always pops-up on primary display in multi-head setup
Status: VERIFIED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: 1.3.0
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-29 18:51 UTC by U. Artie Eoff
Modified: 2014-04-28 19:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description U. Artie Eoff 2013-10-29 18:51:54 UTC
On a multi-head setup, weston's virtual keyboard always pops up on the primary output regardless of which output contains the app you are interacting with.  For example, one would expect that if the "weston-editor" was on the secondary output, then activating a text field would cause the virtual keyboard to pop-up on the same output as the weston-editor.

wayland (HEAD) heads/1.3-0-g84247b7
drm (HEAD) libdrm-2.4.46-0-gc6d73cf
mesa (HEAD) remotes/origin/9.2-0-g7ab2b8c
libva (HEAD) libva-1.2.1-0-g88ed1eb
intel-driver (HEAD) 1.2.1-0-g8f306e3
weston (HEAD) remotes/origin/1.3-0-g98562c3
Comment 1 Manuel Bachmann 2014-04-17 12:07:26 UTC
Hi,

This patch :
http://lists.freedesktop.org/archives/wayland-devel/2014-April/014279.html
fixes this.
Comment 2 Kristian Høgsberg 2014-04-21 21:32:20 UTC
commit f242d4ea74f7c1361855d36920039993bb09cdc9
Author: Manuel Bachmann <manuel.bachmann@open.eurogiciel.org>
Date:   Thu Apr 17 14:04:32 2014 +0200

    shell: display the input panel on the active output
    
    We now dynamically move the input panel (i.e. virtual
    keyboard) surface to the output containing the currently
    focused surface.
    
    https://bugs.freedesktop.org/show_bug.cgi?id=71015
    
    Signed-off-by: Manuel Bachmann <manuel.bachmann@open.eurogiciel.org>


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.