Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
Public bug reported:
I slightly messed up my /etc/network/interfaces, but never realized that
that was the reason that gnome was not starting. KDE, XFCE4 and icewm
were working fine. If localhost has to be up for gnome, it should at
least give back feedback to the user that it is down. Right now i
