*** This bug is a duplicate of bug 82927 ***
https://bugs.launchpad.net/bugs/82927
** Changed in: nis (Debian)
Status: Confirmed => Fix Released
--
ypbind won't start on Feisty (without -no-dbus)
https://bugs.launchpad.net/bugs/90693
You received this bug notification because you are
*** This bug is a duplicate of bug 82927 ***
https://bugs.launchpad.net/bugs/82927
** This bug has been marked a duplicate of bug 82927
[feisty fawn] NetworkManager reports incorrect online status
--
ypbind won't start on Feisty (without -no-dbus)
https://bugs.launchpad.net/bugs/90693
You
** Changed in: nis (Debian)
Status: Unconfirmed => Confirmed
--
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 li
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, a
Upstream believes that the only sane fix is for Network Manager to not
start if it can't support the system. I'm beginning to agree with them
on that although I'm still looking at workarounds off and on.
The set of network configurations Network Manager supports is really
very limited; either dein
I also see this.
I my case, I have bound two ethernets together, and the Network manager
thinks I'm disconnected.
--- /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The l
Started work on this yesterday - suggested fix has trouble if we're in
the middle of a broadcast.
** Changed in: nis (Ubuntu)
Assignee: (unassigned) => Mark Brown
Status: Confirmed => In Progress
--
ypbind won't start on Feisty (without -no-dbus)
https://launchpad.net/bugs/90693
--
** Changed in: nis (Debian)
Status: Unknown => Unconfirmed
--
ypbind won't start on Feisty (without -no-dbus)
https://launchpad.net/bugs/90693
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hrm. On the one hand that's not what I'd consider helpful output from
Network Manager - I'm guessing that it has refused to play with eth0. On
the other hand ypbind ought to be able to handle the situation better.
The block on the dbus socket you're seeing is actually ypbind waiting
for events from
Problem can be seen by comparing Network Manager output & code; it
really seems like a Network Manager bug too but robustness seems good
and this'd also break with a local master.
** Changed in: nis (Ubuntu)
Status: Unconfirmed => Confirmed
--
ypbind won't start on Feisty (without -no-dbu
** Bug watch added: Debian Bug tracker #404131
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404131
** Also affects: nis (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404131
Importance: Unknown
Status: Unknown
--
ypbind won't start on Feisty (without -no-dbus)
Here's the output:
$ nm-tool
NetworkManager Tool
State: disconnected
print_devices(): didn't get a reply from NetworkManager.
There are no available network devices.
And just for the record (my exact IPs removed):
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
ifac
Could you please supply the output from 'nm-tool' (this will dump
diagnostic information about what Network Manager thinks is going on)?
If Network Manager is running then ypbind does a blocking DBUS call to
query the network interface status - I expect this is what is blocking.
--
ypbind won't
13 matches
Mail list logo
