Commit bebd5020 authored by Debarshi Ray's avatar Debarshi Ray

wayland: Don't warn if the display is lost, skip exit handlers

There is no need to have every application log a warning when the
Wayland display server goes away, and we are using _exit instead of
exit elsewhere.

This is also what the X11 backend does (see gdk_x_io_error).

https://bugzilla.gnome.org/show_bug.cgi?id=745289
parent 1d523568
......@@ -20,7 +20,7 @@
#include "gdkinternals.h"
#include "gdkprivate-wayland.h"
#include <stdlib.h>
#include <unistd.h>
#include <errno.h>
typedef struct _GdkWaylandEventSource {
......@@ -200,15 +200,15 @@ _gdk_wayland_display_queue_events (GdkDisplay *display)
if (wl_display_dispatch_pending (display_wayland->wl_display) < 0)
{
g_warning ("Error %d (%s) dispatching to Wayland display.",
g_message ("Error %d (%s) dispatching to Wayland display.",
errno, g_strerror (errno));
exit (1);
_exit (1);
}
if (source->pfd.revents & (G_IO_ERR | G_IO_HUP))
{
g_warning ("Lost connection to Wayland compositor.");
exit (1);
g_message ("Lost connection to Wayland compositor.");
_exit (1);
}
source->pfd.revents = 0;
}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment