NetworkManager has stopped working

[Timothy Murphy]

When I re-booted my Thinkpad T43 laptop today, 
NM failed to start,
as far as I can see through a failure of wpa_supplicant :
--------------------------------
Mar 29 14:41:45 carrie NetworkManager: <info>  (eth1): driver supports SSID 
scans (scan_capa 0x21).
Mar 29 14:41:45 carrie NetworkManager: <info>  (eth1): new 802.11 WiFi 
device (driver: 'ipw2200')
Mar 29 14:41:45 carrie NetworkManager: <info>  (eth1): exported as 
/org/freedesktop/NetworkManager/Devices/1
Mar 29 14:41:45 carrie NetworkManager: <info>  modem-manager is now 
available
Mar 29 14:41:45 carrie NetworkManager: <WARN>  default_adapter_cb(): bluez 
error getting default adapter: The name org.bluez was not provided by any 
.service files
Mar 29 14:41:45 carrie NetworkManager: <info>  Trying to start the 
supplicant...
Mar 29 14:41:45 carrie NetworkManager: <info>  (eth1): supplicant manager 
state:  down -> idle
--------------------------------

The network service works fine
(on chkconfig-ing NetworkManager off, and network on,
and re-booting).
Also "sudo iwlist scan" sees my AP perfectly.

Can anyone suggest what the cause might be,
or how I can find out?

There appears to be no recent entry in /var/log/wpa_supplicant.log .

Actually, this is the second (of 5 or 6 machines)
on which NM is not running, although the network service works.
In both cases the problem seems to be connected to wpa_supplicant.

Any advice or suggestions gratefully received.

Ps I was grateful to find that the network service
seems to work better than it used to ...

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland