Yes, I added
YPBINDARGS=-no-dbus
to my /etc/default/nis to work around this issue. (Removing network-
manager isn't that appealing, since it would require removing ubuntu-
desktop and possibly losing out if new packages are added to the ubuntu-
desktop metapackage)
By the way, for the record, at some point Network Manager started being
able to cope with my network config; nm-tool now shows:
NetworkManager Tool
State: connected
- Device: eth0 ----------------------------------------------------------------
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Type: Wired
Driver: e1000
Active: yes
HW Address: 00:19:D1:02:13:C8
Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 100 Mb/s
Wired Settings
Hardware Link: yes
IP Settings:
IP Address: ---.---.---.---
Subnet Mask: 255.255.254.0
Broadcast: ---.---.---.---
Gateway: ---.---.---.---
Primary DNS: ---.---.---.---
Secondary DNS: ---.---.---.---
(with correct info for the IP addresses I've removed).
I'm not sure which Feisty update fixed NM for me, but I guess I could
revert my -no-bus option now. However I don't see any particular
advantage to doing that given the fact that my config is totally static.
--
ypbind won't start on Feisty (without -no-dbus)
https://bugs.launchpad.net/bugs/90693
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
