I just booted in an older kernel, and then the problem does not occur.
It happens when I boot to 2.6.31-10-generic.
Which older kernel? When you boot with the new one, can you please
attach /var/log/kern.log after a failed gdm startup? Anything helpful
there?
--
GDM doesn't start when DNS
Also, please do
sudo tar czvf /tpm/gdm-logs.tar.gz /var/log/gdm
and attach /tmp/gdm-logs.tar.gz here.
--
GDM doesn't start when DNS lookups aren't available
https://bugs.launchpad.net/bugs/436515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Hi Martin, I re-installed the machine this morning with the latest daily
build, and it doesn't happen anymore. I suppose whatever caused the
breakage was fixed (marking bug so), I'll keep an eye out for when it
happens again.
** Changed in: gdm (Ubuntu)
Status: New = Fix Released
--
GDM
Thank you for your bug report, did that start happening recently? There
was no gdm change which should make a difference there
** Summary changed:
- [karmic] GDM doesn't start when DNS lookups aren't available
+ GDM doesn't start when DNS lookups aren't available
** Changed in: gdm (Ubuntu)
It started today after I upgraded my karmic installation to the newest
packages. My last upgrade was in the last two days or so.
I just booted in an older kernel, and then the problem does not occur.
It happens when I boot to 2.6.31-10-generic. Perhaps related to
something that might have changed
is your lo interface correctly configured?
--
GDM doesn't start when DNS lookups aren't available
https://bugs.launchpad.net/bugs/436515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
My /etc/network/interfaces file contains:
auto lo
iface lo inet loopback
It seems to come up fine:
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX
