After rereading the bridge_ignore_without_connections.patch, i agree
with you about a problem with connection matching.
IMHO the problem are not the lines you referred to, they are only a
inherited error and aren't logged with a network-manager without the
patch. But:
<debug> [1390763529.436635] [nm-manager.c:1898] add_device(): MATT: should
inhibit: true
in conjunction with nm-manager.c:1947
if ( !manager_sleeping (self)
&& !nm_device_spec_match_list (device, unmanaged_specs) &&
!inhibit_managed) {
is resulting in a not called nm_device_set_managed. Obviously this is
the cause. The unanswered question is why nm-manager.c:1895
nm_device_connection_match_config returns NULL.
The config i'm using with network-manager (0.9.8.8-0ubuntu1) and
network-manager (0.9.8.8-0ubuntu1) minus
bridge_ignore_without_connections.patch is exactly the same and
attached.
** Attachment added: "/etc/NetworkManager/NetworkManager.conf"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+attachment/3963295/+files/NetworkManager.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273201
Title:
bridge_ignore_without_connections.patch breaks NM created bridge at
boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
