On Wed, Aug 12, 2015 at 02:41:08PM +0300, Pekka Paalanen wrote:
> On Mon, 25 May 2015 01:12:15 -0700
> Dima Ryazanov wrote:
>
> > Although defaulting to wayland-0 seems convenient, it has an undesirable
> > side effect: clients may unintentionally connect to the wrong compositor.
> > Generally, i
Although defaulting to wayland-0 seems convenient, it has an undesirable
side effect: clients may unintentionally connect to the wrong compositor.
Generally, it's safer to fail instead. Here's a real example:
In Fedora 22, Gtk+ prefers Wayland over X11, though the default session is still
a normal
Sounds good, will do!
On Wed, Aug 12, 2015 at 4:41 AM, Pekka Paalanen wrote:
> On Mon, 25 May 2015 01:12:15 -0700
> Dima Ryazanov wrote:
>
> > Although defaulting to wayland-0 seems convenient, it has an undesirable
> > side effect: clients may unintentionally connect to the wrong compositor.
>
We're coming up to our next scheduled release. I've got a few scattered
events and holidays but looking at my calendar, these dates look
feasible and fit the timeframe we wanted:
* 8/14 (Friday) - 1.8.91 (1.9 alpha)
* 9/01 (Tuesday) - 1.8.92 (1.9 beta)
+ Feature freeze
* 9/15 (Tuesday) - 1.
On Mon, 25 May 2015 01:12:15 -0700
Dima Ryazanov wrote:
> Although defaulting to wayland-0 seems convenient, it has an undesirable
> side effect: clients may unintentionally connect to the wrong compositor.
> Generally, it's safer to fail instead. Here's a real example:
>
> In Fedora 22, Gtk+ pr
xwayland source is checked, so it dispatches twice on any event.
If the other turn has no events to dispatch, we flush the connection
redundantly
v2. do not flood logs with 'unhandled event' messages
Signed-off-by: Marek Chalupa
Reviewed-by: Derek Foreman
---
xwayland/window-manager.c | 3 ++-
