Bug 61812 - [regression] event-test.test_pointer_move_surface fails
Summary: [regression] event-test.test_pointer_move_surface fails
Status: VERIFIED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-04 19:47 UTC by U. Artie Eoff
Modified: 2013-03-04 19:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description U. Artie Eoff 2013-03-04 19:47:41 UTC
The event_test.test_pointer_move_surface test is failing when moving the client to the pointer.  That is, this test moves the pointer outside of the client surface so the surface does not have the pointer focus.  Then, the client surface is moved such that the pointer is now on the center of the client surface.  Originally, the client would receive a pointer enter event.  Now, that is no longer happening.

The first bad commit is:
http://cgit.freedesktop.org/wayland/weston/commit/?id=184df50d3e68aa53bdda06e14b7fe1531d633656

Test Output:

test-client: got global pointer 210 60
test-client: got keyboard keymap
test-client: got surface enter output 0x25ba740
test-client: got global pointer 50 50
event-test: event-test.c:38: check_pointer: Assertion `client->input->pointer->focus == client->surface' failed.
Comment 1 Kristian Høgsberg 2013-03-04 19:52:17 UTC
commit 82cb505287a324468b697b76825332db02727854
Author: Giulio Camuffo <giuliocamuffo@gmail.com>
Date:   Thu Feb 28 18:44:54 2013 +0100

    tests: attach the surface's buffer when moving it
    
    move_client() needs to attach the buffer, even if it was attached already,
    because since 184df50 configure() will be called only on newly attached
    surfaces, but the one that sets the test surface position is the configure
    function.


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.