GNOME Bugzilla – Bug 318584
hang on the splash if the loopback interface is no correctly configured
Last modified: 2013-01-13 18:34:25 UTC
If the "lo" interface is not correctly configured gnome-session hangs for some time, that's a quite frequent issue for users.
A proposed solution to this problem is to display a warning dialog very soon in the login process, explaining there is no loopback and how to fix it, and asking whether the user wants to login nevertheless. This should avoid all lockups that can happen in this case.
Further to https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/108761 both localhost and ip6-localhost should be pinged while determining whether the loopback interface is configured correctly.
Did anybody look at why this is happening?
Sebastien, is this still happening?
you want some testing on 2.23 I guess? I'm still running 2.22 for the moment, but it's easy enough to try, just logout, ifdown lo and try login-in again
Yeah, testing on 2.23 would be nice. I tried it here and it seems that g-s 2.23.x doesn't hang on splash but on logout when loopback interface is down. Need to investigate that.
I have https://bugzilla.novell.com/show_bug.cgi?id=411682 on OpenSuse-11.0. I wonder if there is a mechanism (e.g. env-var) to get it logging what it starts.
This shouldn't be a problem anymore. If the problem still occurs, please reopen after testing with GNOME 3.6 or newer.