| Summary: | Clipboard doesn't properly store data of client that closes | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | nerdopolis1 |
| Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | call wl_data_device_set_keyboard_focus in seat_get_keyboard | ||
|
Description
nerdopolis1
2013-02-10 21:33:57 UTC
Created attachment 74985 [details] [review] call wl_data_device_set_keyboard_focus in seat_get_keyboard For me ctrl+v doesn't work for any newly opened client, until I explicitly activate it with mouse click, but I think both use cases are related. I investigated a bit, and it is because during first call to weston_surface_activate wl_seat.focus_resource is not set up, due to seat_get_keyboard being called later. Proposed patch calls wl_data_device_set_keyboard_focus in seat_get_keyboard, so it can send data offer for newly created client. Or maybe better fix is to somehow delay first weston_surface_activate until seat_get_keyboard is called first? (In reply to comment #1) > Created attachment 74985 [details] [review] [review] > call wl_data_device_set_keyboard_focus in seat_get_keyboard > > For me ctrl+v doesn't work for any newly opened client, until I explicitly > activate it with mouse click, but I think both use cases are related. > > I investigated a bit, and it is because during first call to > weston_surface_activate wl_seat.focus_resource is not set up, due to > seat_get_keyboard being called later. > > Proposed patch calls wl_data_device_set_keyboard_focus in seat_get_keyboard, > so it can send data offer for newly created client. > > Or maybe better fix is to somehow delay first weston_surface_activate until > seat_get_keyboard is called first? That sounds right, good analysis. Committed to master and 1.0 branch, thanks. |
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.