I haven't upgraded to Feisty yet; and my "ping localhost" works. My
loopback device is fine. Yet, my system still "hangs" when I try to
access the GNOME Menu on occasion.
Thanks; and regards,
Robert
On 4/11/07, DerekBuranen <email address hidden> wrote:
> Here's the real culprit.
> *ping localhost
>
> This command wasn't working. Seems when I upgraded to Feisty and when I
> was setting a static IP, I commented EVERYTHING in
> /etc/network/interfaces. This is not good as the 'lo' or loopback
> device is needed. I uncommented auto lo and the iface line for lo, ran
> ;sudo ifup lo', and I was back with a fast Gnome and no gray screen in
> the corner.
>
> Hope this helps some of you out there. Thanks to seb for the tip.
>
> --
> Gnome settings manager error to start desktop
> https://bugs.launchpad.net/bugs/84876
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
Greetings, Derek:
I haven't upgraded to Feisty yet; and my "ping localhost" works. My
loopback device is fine. Yet, my system still "hangs" when I try to
access the GNOME Menu on occasion.
Thanks; and regards,
Robert
On 4/11/07, DerekBuranen <email address hidden> wrote: interfaces. This is not good as the 'lo' or loopback /bugs.launchpad .net/bugs/ 84876
> Here's the real culprit.
> *ping localhost
>
> This command wasn't working. Seems when I upgraded to Feisty and when I
> was setting a static IP, I commented EVERYTHING in
> /etc/network/
> device is needed. I uncommented auto lo and the iface line for lo, ran
> ;sudo ifup lo', and I was back with a fast Gnome and no gray screen in
> the corner.
>
> Hope this helps some of you out there. Thanks to seb for the tip.
>
> --
> Gnome settings manager error to start desktop
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>