nis client fails to start due to dbus stuff

Bug #105651 reported by Jesper Krogh
2
Affects Status Importance Assigned to Milestone
nis (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nis

On an edgy/amd64 system upgraded to feisty the nis client fails to start due to something with dbus.

Setting $YPBINDOPTS=-no-dbus in /etc/default/nis solves this problem but the default configuration of the nis-client was broken.

Revision history for this message
Mark Brown (broonie) wrote :

This is caused by having Network Manager installed on a system where Network Manager is not supported (for example, one using a static network configuration) which causes Network Manager to report that the network is unavailable when in fact it is available.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.