error messages - let's be less ramatic and have fewer of these on start

various errors we have are not actual errors but mostly information or
debug or status messages, so don't use ERR or just don't do the thing
that triggers it as it's useless. This leads to a less
noisy/error-like start output. cleaner for a release for sure.
This commit is contained in:
Carsten Haitzler 2019-06-04 14:14:18 +01:00
parent af92895931
commit 6af9d75293
3 changed files with 7 additions and 5 deletions

View File

@ -3006,7 +3006,7 @@ e_comp_wl_init(void)
/* try to init ecore_wayland */
if (!ecore_wl2_init())
{
e_error_message_show(_("Enlightenment cannot initialize Ecore_Wl2!\n"));
fprintf(stderr, _("Enlightenment cannot initialize Wayland client connection.\n"));
return EINA_FALSE;
}
@ -3021,7 +3021,7 @@ e_comp_wl_init(void)
/* try to create a wayland compositor */
if (!_e_comp_wl_compositor_create())
{
e_error_message_show(_("Enlightenment cannot create a Wayland Compositor!\n"));
fprintf(stderr, _("Enlightenment cannot create a Wayland Compositor.\n"));
return EINA_FALSE;
}

View File

@ -5813,7 +5813,7 @@ e_comp_x_init(void)
Eina_List *h = NULL;
if (!ecore_x_init(NULL))
{
e_error_message_show(_("Enlightenment cannot initialize Ecore_X!\n"));
fprintf(stderr, _("Enlightenment cannot initialize X Connection...\n"));
return EINA_FALSE;
}

View File

@ -346,8 +346,10 @@ bz_obj_add(const char *path)
"PropertiesChanged",
cb_obj_prop_changed, o);
// disable the filter for discovery later
eldbus_proxy_call
(o->proxy, "SetDiscoveryFilter", cb_obj_discovery_filter, o, -1, "");
// XXX: this doesnt seem to exist on the bluez daemons i see
// so don't do this to avoid error noise and it's useless it seems
// eldbus_proxy_call
// (o->proxy, "SetDiscoveryFilter", cb_obj_discovery_filter, o, -1, "");
}
goto done;
}