mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-10 11:40:18 +01:00
a7aca2ab08
The bluetooth device *never* manages NAP connection. Hence, checking for
nm_bt_vtable_network_server in "nm-bluez-manager.c" is wrong.
Especially, because nm_bt_vtable_network_server is only initialized
much later, so during initial start, the bluetooth factory would wronly
claim to support it. This leads to a crash when having a NAP connection.
Also, the bridge factory requires the bluetooth plugin. It should only
claim to support NAP when the bluetooth plugin is present. That
way, we get a proper "missing plugin" error message, instead of failing
later during activation.
It seems to me, distributing the logic to various match_connection()
functions makes it more complicated, because the implementation is
spread out and interact in complicated ways. Anyway.
Fixes:
|
||
|---|---|---|
| .. | ||
| nm-bluez-common.h | ||
| nm-bluez-device.c | ||
| nm-bluez-device.h | ||
| nm-bluez-manager.c | ||
| nm-bluez4-adapter.c | ||
| nm-bluez4-adapter.h | ||
| nm-bluez4-manager.c | ||
| nm-bluez4-manager.h | ||
| nm-bluez5-dun.c | ||
| nm-bluez5-dun.h | ||
| nm-bluez5-manager.c | ||
| nm-bluez5-manager.h | ||
| nm-bt-error.c | ||
| nm-bt-error.h | ||
| nm-device-bt.c | ||
| nm-device-bt.h | ||