calendar-server: use g_warning instead of g_printerr

This way error messages include the process name and PID, so they're
picked up by bug reporting tools that grep ~/.xsession-errors.

https://bugzilla.gnome.org/show_bug.cgi?id=671177
This commit is contained in:
Giovanni Campagna 2012-03-05 21:33:15 +01:00
parent d68ff69c7a
commit 0ea690a2f2

View File

@ -630,7 +630,8 @@ app_load_events (App *app)
error = NULL;
if (!e_client_open_sync (E_CLIENT (cal), TRUE, NULL, &error))
{
g_printerr ("Error opening calendar: %s\n", error->message);
g_warning ("Error opening calendar %s: %s\n",
e_client_get_uri (E_CLIENT (cal)), error->message);
g_error_free (error);
continue;
}
@ -647,7 +648,8 @@ app_load_events (App *app)
NULL, /* cancellable */
&error))
{
g_printerr ("Error querying calendar: %s\n", error->message);
g_warning ("Error querying calendar %s: %s\n",
e_client_get_uri (E_CLIENT (cal)), error->message);
g_error_free (error);
g_free (query);
continue;
@ -680,7 +682,7 @@ app_load_events (App *app)
NULL, /* cancellable */
&error))
{
g_printerr ("Error setting up live-query on calendar: %s\n", error->message);
g_warning ("Error setting up live-query on calendar: %s\n", error->message);
g_error_free (error);
}
else