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.
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) spec_match_ list (device, unmanaged_specs) && !inhibit_managed) {
&& !nm_device_
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.