Debian Bug report logs - #532670
network-manager: system lockup with LDAP lookup for group

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: submit@bugs.debian.org

Subject: network manager causes system to fail to boot

Date: Wed, 10 Jun 2009 18:55:25 +0100

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...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Welcome my son, welcome to the machine.

Message #10 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Steve McIntyre <steve@einval.com>, 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: network manager causes system to fail to boot

Date: Wed, 10 Jun 2009 20:52:14 +0200

[Message part 1 (text/plain, inline)]

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?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: network manager causes system to fail to boot

Date: Wed, 10 Jun 2009 20:09:47 +0100

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.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Dasmohapatra

Message #20 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Steve McIntyre <steve@einval.com>, 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: network manager causes system to fail to boot

Date: Wed, 10 Jun 2009 22:06:06 +0200

[Message part 1 (text/plain, inline)]

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 (application/pgp-signature, attachment)]

Message #25 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: network manager causes system to fail to boot

Date: Wed, 10 Jun 2009 21:10:23 +0100

On Wed, Jun 10, 2009 at 10:06:06PM +0200, Michael Biebl wrote:
>Steve McIntyre wrote:
>> On Wed, Jun 10, 2009 at 08:52:14PM +0200, Michael Biebl wrote:
>>
>>> 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.

Sure, I can give that a try tomorrow when I'm back in the office. I'm
wondering how that might work, though: this is well before anybody
even attempts to log in, i.e. before gdm displays the login box. I
don't know if I made that clear before...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Who needs computer imagery when you've got Brian Blessed?

Message #30 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: network manager causes system to fail to boot

Date: Thu, 11 Jun 2009 11:56:30 +0100

On Wed, Jun 10, 2009 at 09:10:23PM +0100, Steve McIntyre wrote:
>On Wed, Jun 10, 2009 at 10:06:06PM +0200, Michael Biebl wrote:
>>Steve McIntyre wrote:
>>> On Wed, Jun 10, 2009 at 08:52:14PM +0200, Michael Biebl wrote:
>>>
>>>> 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.
>
>Sure, I can give that a try tomorrow when I'm back in the office. I'm
>wondering how that might work, though: this is well before anybody
>even attempts to log in, i.e. before gdm displays the login box. I
>don't know if I made that clear before...

OK, that didn't help at all I'm afraid. After the delay, the system
continued on and hung in just the same way at gdm startup.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

Message #35 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: network manager causes system to fail to boot

Date: Mon, 15 Jun 2009 16:43:26 +0100

On Thu, Jun 11, 2009 at 11:56:30AM +0100, Steve McIntyre wrote:
>On Wed, Jun 10, 2009 at 09:10:23PM +0100, Steve McIntyre wrote:
>>On Wed, Jun 10, 2009 at 10:06:06PM +0200, Michael Biebl wrote:
>>>Steve McIntyre wrote:
>>>> On Wed, Jun 10, 2009 at 08:52:14PM +0200, Michael Biebl wrote:
>>>>
>>>>> 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.
>>
>>Sure, I can give that a try tomorrow when I'm back in the office. I'm
>>wondering how that might work, though: this is well before anybody
>>even attempts to log in, i.e. before gdm displays the login box. I
>>don't know if I made that clear before...
>
>OK, that didn't help at all I'm afraid. After the delay, the system
>continued on and hung in just the same way at gdm startup.

Debugging further, running gdm under strace shows that the last useful
thing it does is send "AUTH EXTERNAL 30" via dbus. I'm looking at dbus
now to see what's happening there.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Message #40 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Sascha Silbe <sascha-debian-bugs-network-manager-2@silbe.org>

To: Debian Bug Tracking System <532670@bugs.debian.org>

Subject: patch to include policy in network-manager

Date: Sat, 27 Jun 2009 16:46:58 +0200

[Message part 1 (text/plain, inline)]

Package: network-manager
Tags: patch

The attached patch adds the policy to the network-manager package, 
sparing me from installing 52 packages occupying 271MB on disk.
Since the file is named differently in network-manager-kde there should 
be no issue with conflicting files even if network-manager-kde doesn't 
get patched to remove the file there.

CU Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/

[network-manager-0.7.1-userpolicy.patch (text/x-diff, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #45 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 532670@bugs.debian.org, Steve McIntyre <steve@einval.com>

Cc: control@bugs.debian.org

Subject: downgrading

Date: Wed, 22 Jul 2009 14:35:09 +0200

[Message part 1 (text/plain, inline)]

tags 532670 unreproducible
severity 532670 important
thanks

Hi Steve,

given the fact that I can't reproduce the problem and it doesn't seem to be a
common problem (no other users confirming the issue), I'm downgrading the
severity to important. Actually it seems more like a bug to me that is triggered
by network-manager, not in network-manager itself.

Steve, if you found out more in between w.r.t gdm etc, please let us know.

Cheers,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #54 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: downgrading

Date: Wed, 5 Aug 2009 18:16:44 +0100

On Wed, Jul 22, 2009 at 02:35:09PM +0200, Michael Biebl wrote:
>tags 532670 unreproducible
>severity 532670 important
>thanks
>
>Hi Steve,

Hi Michael,

>given the fact that I can't reproduce the problem and it doesn't seem to be a
>common problem (no other users confirming the issue), I'm downgrading the
>severity to important. Actually it seems more like a bug to me that is triggered
>by network-manager, not in network-manager itself.

Hmmm. What have you tried in an attempt to reproduce the bug? I can
reproduce it at will here, and I can also see clearly related problems
reproduced by people elsewhere:

https://bugzilla.redhat.com/show_bug.cgi?id=385721
(closed because of Fedora's policy to close all bugs against old
 releases *spit*)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500998
(also reported against network-manager)

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510678
(reported against libnss-ldap but clearly the same problem)

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/399626
(looks like it could be the same issue, but the report is a little
vague)

We have a real problem here, which I think may be a major design bug
somewhere in network-manager or dbus or possibly gdm. I don't know
enough about the internals of any of them to say who is responsible,
but the bug is serious and I'm convincing it needs fixing. Maybe you
need to talk to upstream about this; I can happily add debug versions
of software here if needed and do simple debugging and logging, but I
don't have the time to find the fix on my own.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

Message #59 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Steve McIntyre <steve@einval.com>, 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: downgrading

Date: Wed, 05 Aug 2009 20:25:38 +0200

[Message part 1 (text/plain, inline)]

Steve McIntyre wrote:
> On Wed, Jul 22, 2009 at 02:35:09PM +0200, Michael Biebl wrote:
>> tags 532670 unreproducible
>> severity 532670 important
>> thanks
>>
>> Hi Steve,
> 
> Hi Michael,
> 
>> given the fact that I can't reproduce the problem and it doesn't seem to be a
>> common problem (no other users confirming the issue), I'm downgrading the
>> severity to important. Actually it seems more like a bug to me that is triggered
>> by network-manager, not in network-manager itself.
> 
> Hmmm. What have you tried in an attempt to reproduce the bug? I can
> reproduce it at will here, and I can also see clearly related problems
> reproduced by people elsewhere:

Could you please disable gdm for the time being, so that you can login on the
console.

I assume you have no network connection at this point, bug please double check.
As you are using LDAP/NIS (please attach you configuration, nsswich.conf etc.
and if you use nscd/nslcd).

Then stop the running network-manager instance and start it with
"NetworkManager --no-daemon" and attach the output.
Does NM successfully acquire an IP address via DHCP?

If not, what happens if you disable LDAP/NIS in your nsswitch configuration
(will probably also require a restart of dbus).




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #64 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@teco.edu>

To: 532670@bugs.debian.org

Cc: Steve McIntyre <steve@einval.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: downgrading

Date: Wed, 05 Aug 2009 22:23:03 +0200

[Message part 1 (text/plain, inline)]

How does your system behave, if you are using ifupdown (NM disabled) and
you boot with the network cable unplugged?

Michael

[signature.asc (application/pgp-signature, attachment)]

Message #69 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@debian.org>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: downgrading

Date: Thu, 6 Aug 2009 14:03:10 +0100

[Message part 1 (text/plain, inline)]

On Wed, Aug 05, 2009 at 08:25:38PM +0200, Michael Biebl wrote:
>Steve McIntyre wrote:
>> 
>> Hmmm. What have you tried in an attempt to reproduce the bug? I can
>> reproduce it at will here, and I can also see clearly related problems
>> reproduced by people elsewhere:
>
>Could you please disable gdm for the time being, so that you can login on the
>console.

OK, done.

>I assume you have no network connection at this point, bug please double check.

Correct, I do not have working networking at boot: no DHCP lease and
no DHCP client that I can see running.

>As you are using LDAP/NIS (please attach you configuration, nsswich.conf etc.
>and if you use nscd/nslcd).

We're using nscd. Attached tarball contains the nsswitch.conf,
pam_ldap.conf and libnss_ldap.conf

>Then stop the running network-manager instance and start it with
>"NetworkManager --no-daemon" and attach the output.

It hangs showing just one line (see typescript output). After 5
minutes I got bored and killed it.

Script started on Thu 06 Aug 2009 13:49:36 BST
smcintyre4:~# NetworkManager --no-daemon
NetworkManager: <info>  starting...
Script done on Thu 06 Aug 2009 13:54:36 BST

>Does NM successfully acquire an IP address via DHCP?

Doesn't look like, no.

>If not, what happens if you disable LDAP/NIS in your nsswitch configuration
>(will probably also require a restart of dbus).

If I disable LDAP in nsswitch and reboot, NetworkManager gets a lease
from DHCP straight away.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"Because heaters aren't purple!" -- Catherine Pitt

[conf.tar.gz (application/octet-stream, attachment)]

Message #74 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Michael Biebl <biebl@teco.edu>

Cc: 532670@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#532670: Bug#532670: downgrading

Date: Thu, 6 Aug 2009 14:12:32 +0100

On Wed, Aug 05, 2009 at 10:23:03PM +0200, Michael Biebl wrote:
>How does your system behave, if you are using ifupdown (NM disabled) and
>you boot with the network cable unplugged?

I've disabled NM and re-enabled gdm and the system boots just fine to
the gdm login prompt, no hang. Of course, I can't log in usefully as
an LDAP user (*grin*) but the system works at this point.

This suggests the hang I mentioned in the previous mail is the culprit
here...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
< sladen> I actually stayed in a hotel and arrived to find a post-it
          note stuck to the mini-bar saying "Paul: This fridge and
          fittings are the correct way around and do not need altering"

Message #83 received at 532670@bugs.debian.org (full text, mbox, reply):

From: boris <boris@macbeth.rhoen.de>

To: Debian Bug Tracking System <532670@bugs.debian.org>

Subject: network-manager: no network connection with nsswitch.conf-> passwd: compat ldap

Date: Sun, 23 Aug 2009 12:54:14 +0200

Package: network-manager
Version: network-manager_0.6.6-3
Followup-For: Bug #532670

Hi,
I can confirm this too.
When trying to boot into a newly installed lenny system - configured with
_ldap_ in nsswitch.conf (_passwd:_ and _group:_).
It seems that NM doesn't set up the network.
In my case kdm hangs exactly as described by Steve (for gdm).
Starting without kdm doesn't work here - login on the console hangs
after displaying /etc/motd.
And removing network-manager solves the problem.

boris

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-486
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                   3.110          add and remove users and groups
ii  dbus                      1.2.1-5+lenny1 simple interprocess messaging syst
ii  dhcdbd                    3.0-5          D-Bus interface to the ISC DHCP cl
ii  hal                       0.5.11-8       Hardware Abstraction Layer
ii  ifupdown                  0.6.8+nmu1     high level tools to configure netw
ii  iproute                   20080725-2     networking and traffic control too
ii  libc6                     2.7-18         GNU C Library: Shared libraries
ii  libdbus-1-3               1.2.1-5+lenny1 simple interprocess messaging syst
ii  libdbus-glib-1-2          0.76-1         simple interprocess messaging syst
ii  libgcrypt11               1.4.1-1        LGPL Crypto library - runtime libr
ii  libglib2.0-0              2.16.6-2       The GLib library of C routines
ii  libgpg-error0             1.4-2          library for common error values an
ii  libhal1                   0.5.11-8       Hardware Abstraction Layer - share
ii  libiw29                   29-1.1         Wireless tools - library
ii  libnl1                    1.1-2          library for dealing with netlink s
ii  libnm-util0               0.6.6-3        network management framework (shar
ii  lsb-base                  3.2-20         Linux Standard Base 3.2 init scrip
ii  wpasupplicant             0.6.4-3        Client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
pn  network-manager-gnome | netwo <none>     (no description available)

network-manager suggests no packages.

Maybe also important:
ii  libldap-2.4-2                        2.4.11-1
ii  libnss-ldap                          261-2.1
ii  libpam-ldap                          184-4.2
ii  libnss3-1d                           3.12.0-6
ii  nscd                                 2.7-18
ii  heimdal-clients                      1.2.dfsg.1-2.1
ii  heimdal-kcm                          1.2.dfsg.1-2.1
ii  heimdal-servers                      1.2.dfsg.1-2.1

# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp

foo.bar:/home on /home type nfs4 (rw,sec=krb5p,addr=192.168.0.1)
foo.bar:/mail on /var/mail type nfs4 (rw,sec=krb5p,addr=192.168.0.1)

Message #90 received at 532670@bugs.debian.org (full text, mbox, reply):

From: Toomas Tamm <tt-deb@kky.ttu.ee>

To: 532670@bugs.debian.org

Subject: confirming that the problem still exists

Date: Thu, 16 Dec 2010 09:56:56 +0200

Package: network-manager
Version: network-manager_0.6.6-3
Followup-For: Bug #532670

Hello!

I am another admin hit by this problem. I think the bug needs a proper
fix. The situation is made worse by the fact that it does not initially
manifest itself as a network-manager / ldap issue. Instead, the first
symptom is complete system lockup at X starting stage (only the cursor
can be moved with mouse) and no way to recover the box (no response to
keyboard, no network connectivity for remote login). Through several
tries, all ending in hitting the power switch, I lost the integrity of a
disk partition and had to reinstall the whole system!

Then it takes several hours of studying the logs and reading on the net
before one can reach the conclusion that it is a netmanager + ldap
problem.

Several workarounds have been proposed, the easiest being uninstalling
(or not starting) networkmanager. It should be noted that
network-manager (through dependency on network-manager-gnome) is
installed by default as a part of the gnome-desktop task. Once LDAP
authentication gets configured (usually later after installation), the
box no longer boots properly.

-- 
Toomas Tamm                                 e-mail: tt-deb (at) kky.ttu.ee
Chair of Inorganic Chemistry                voice:  INT+372-620-2810
Tallinn University of Technology            fax:    INT+372-620-2828
Ehitajate tee 5, EE-19086 Tallinn, Estonia  http://www.kk.ttu.ee/toomas/

Send a report that this bug log contains spam.