When configuring udev rules on a second pointing device to use the seat functionality, two pointers appear. One that is bound to the seat and the other that is not bound to the seat. Using the pointer which is not bound to the seat, user should be able to execute applications on both seated and not seated displays. But, applications always show on seated display irrespective of where they are executed from. Steps: 1. Cold plugged display1, pointing device and display2 2. Create udev rules in Weston.rules using device path of USB Example ACTION=="add", SUBSYSTEMS=="input", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb1/*", ENV{WL_SEAT}+="back0" 3. Configure Weston to seat the second pointing device on the display2 Example: Output Name=HDMI2 Seat=back0 4. plug a second pointing device into the USB hub( this will bound to display2) 5. Launch weston-launch. 6. Launch weston-terminal on display1 using mouse pointer( which is not bound to seat). Observe terminal showing on display2. Software: wayland (HEAD) 1.3.92-0-gc102c20 drm (HEAD) libdrm-2.4.50-0-g4c5de72 mesa (HEAD) remotes/origin/10.0-0-g3a62718 libva (HEAD) libva-1.2.1-0-g88ed1eb intel-driver (HEAD) 1.2.1-0-g8f306e3 weston (HEAD) 1.3.92-0-gb637a40
I couldn't exactly reproduce the bug, but what I noticed is that the application is launched on the same display as the first pointer is in. The code in weston_view_set_initial_position() does exactly that, looks for the first seat that has a pointer and if it finds one, launches the app in the same output as that pointer.
There is some discussion about this bug on the mailing list here: http://lists.freedesktop.org/archives/wayland-devel/2014-May/thread.html#14568
-- 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/32.
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.