diff options
| author | Owen W. Taylor <otaylor@fishsoup.net> | 2015-10-28 10:52:03 -0400 |
|---|---|---|
| committer | Owen W. Taylor <otaylor@fishsoup.net> | 2015-11-06 17:03:59 -0500 |
| commit | 3ec3cc248db95384ab8be89e90703908cf37717c (patch) | |
| tree | 428d576de1006dac64b64c3c48a2f1bbd082c093 /src/backends | |
| parent | 7fb3ecc12ccd8e633c6a3bfb6ffe3456f1d95bba (diff) | |
| download | mutter-3ec3cc248db95384ab8be89e90703908cf37717c.tar.gz | |
Exit, not abort, when we fail to initialize Clutter
Failing to initialize Clutter isn't something it's useful to report
into automatic bug tracking systems or get a backtrace for - in fact,
the most common case is that DISPLAY is unset or points to a
non-existent X server. So simply exit rather than calling g_error().
https://bugzilla.gnome.org/show_bug.cgi?id=757311
Diffstat (limited to 'src/backends')
| -rw-r--r-- | src/backends/meta-backend.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/backends/meta-backend.c b/src/backends/meta-backend.c index 4a88c89d1..79e5f2e2f 100644 --- a/src/backends/meta-backend.c +++ b/src/backends/meta-backend.c @@ -626,7 +626,10 @@ meta_clutter_init (void) meta_create_backend (); if (clutter_init (NULL, NULL) != CLUTTER_INIT_SUCCESS) - g_error ("Unable to initialize Clutter.\n"); + { + g_warning ("Unable to initialize Clutter.\n"); + exit (1); + } /* * XXX: We cannot handle high dpi scaling yet, so fix the scale to 1 |