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
This commit is contained in:
parent
7fb3ecc12c
commit
3ec3cc248d
1 changed files with 4 additions and 1 deletions
|
@ -626,7 +626,10 @@ meta_clutter_init (void)
|
||||||
meta_create_backend ();
|
meta_create_backend ();
|
||||||
|
|
||||||
if (clutter_init (NULL, NULL) != CLUTTER_INIT_SUCCESS)
|
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
|
* XXX: We cannot handle high dpi scaling yet, so fix the scale to 1
|
||||||
|
|
Loading…
Reference in a new issue