summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorRay Strode <rstrode@redhat.com>2011-06-28 12:51:51 -0400
committerRay Strode <rstrode@redhat.com>2011-06-28 12:51:51 -0400
commitfc6ee4aa6d71d2c448a9b62aca24ba318163c590 (patch)
tree215de00c5920d73919a7f530aa0d2ee7f9a47e7d /common
parent8c5f0a79ffe0ceb876517802f5303004f3d5bd0f (diff)
downloadgdm-fc6ee4aa6d71d2c448a9b62aca24ba318163c590.tar.gz
common: don't tank on criticals
Tiny (or not so tiny) bugs in components below GDM in the stack can lead to critical warnings. In development releases, GDM by default will crash when encountering a critical warning. Losing the login screen is a big deal. We shouldn't automatically subject our users to "can't log in" in order to highlight bugs in development releases. This commit removes fatal criticals by default.
Diffstat (limited to 'common')
-rw-r--r--common/gdm-common.c9
-rw-r--r--common/gdm-common.h1
2 files changed, 0 insertions, 10 deletions
diff --git a/common/gdm-common.c b/common/gdm-common.c
index 7a4e26d8..865341a2 100644
--- a/common/gdm-common.c
+++ b/common/gdm-common.c
@@ -65,15 +65,6 @@ gdm_is_version_unstable (void)
return unstable;
}
-void
-gdm_set_fatal_warnings_if_unstable (void)
-{
- if (gdm_is_version_unstable ()) {
- g_setenv ("G_DEBUG", "fatal_criticals", FALSE);
- g_log_set_always_fatal (G_LOG_LEVEL_CRITICAL);
- }
-}
-
gboolean
gdm_get_pwent_for_name (const char *name,
struct passwd **pwentp)
diff --git a/common/gdm-common.h b/common/gdm-common.h
index 06300c8f..41ddf1c1 100644
--- a/common/gdm-common.h
+++ b/common/gdm-common.h
@@ -31,7 +31,6 @@
G_BEGIN_DECLS
gboolean gdm_is_version_unstable (void);
-void gdm_set_fatal_warnings_if_unstable (void);
int gdm_wait_on_pid (int pid);
int gdm_wait_on_and_kill_pid (int pid,