This bug still remains with 0.7 in intrepid. It's not a trivial missing-icon problem; nm_client_activate_connection apparently requires an active base connection to be able to start a VPN connection.
I'm not familiar with the design and API of NetworkManager so I might be wrong on this, but to me it looks like a bit of an architecture problem in NetworkManager itself; the bug should perhaps be filed on network-manager and sent upstream.
(0.7 handles manually configured interfaces, but that is imo not an excuse to consider this a non-issue. People still can have any number of reasons to want to keep their interfaces unmanaged. Mine in this case is that I need to set more dhcp options than NetworkManager allows me to.)
Second the motion to bump up the priority.
This bug still remains with 0.7 in intrepid. It's not a trivial missing-icon problem; nm_client_ activate_ connection apparently requires an active base connection to be able to start a VPN connection.
I'm not familiar with the design and API of NetworkManager so I might be wrong on this, but to me it looks like a bit of an architecture problem in NetworkManager itself; the bug should perhaps be filed on network-manager and sent upstream.
(0.7 handles manually configured interfaces, but that is imo not an excuse to consider this a non-issue. People still can have any number of reasons to want to keep their interfaces unmanaged. Mine in this case is that I need to set more dhcp options than NetworkManager allows me to.)