Steve McIntyre wrote: > On Wed, Jun 10, 2009 at 08:52:14PM +0200, Michael Biebl wrote: >> Steve McIntyre wrote: >>> Package: network-manager >>> Version: 0.6.6-3 >>> Severity: critical >>> Rationale: system lockup >>> >>> [ This might not be a network-manager bug directly, but simply >>> uninstalling it fixes the problem. ] >>> >>> On a whole range of newly-installed Lenny systems at work, we have a >>> major problem that seems to be caused by network-manager. The system >>> boots up and at starts gdm as normal. However, when gdm starts it >>> simply hangs at the X stipple screen rather than switching to the >>> default solid blue background. The mouse pointer responds, but >>> keyboard input fails to do anything (no response to numlock, can't >>> switch to a console). The box does not respond to pings either; we >>> have no option but to power-cycle. >>> >>> If we purge network-manager and simply enable dhcp directly from >>> /etc/network/interfaces then all works just fine. There doesn't seem >>> to be anything useful in the logs that I can see... >> Do you use any kind of network login / ldap / nis etc? > > You've beaten me to it; I was about to follow up to myself to mention > that. We've seen this using NIS on some machines, and again on newer > ones where we're trying out LDAP too.
My guess is, that it's a problem related to NSS, because network is not yet up when gdm is started. Could you try a small hack and add a sleep 30 to the network-manager init script, after the daemon has started, in order to give it some time to establish a network connection before gdm/X is started. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
