diff options
| author | Lubomir Rintel <lkundrak@v3.sk> | 2022-10-11 18:28:13 +0200 |
|---|---|---|
| committer | Lubomir Rintel <lkundrak@v3.sk> | 2022-10-14 22:22:55 +0200 |
| commit | ebc42cf28acae39d813a9c8bcc172099250be279 (patch) | |
| tree | 5805053319b88b0303cddb87be88b386eed7b9fb /data/nm-shared.xml | |
| parent | 77508aea59c0d6b826f15d1717b241d2d0121c79 (diff) | |
| download | NetworkManager-lr/unmanaged-err.tar.gz | |
core/device: demote "strictly unamanged" errorlr/unmanaged-err
The "device ... not available because device is strictly unmanaged" is
almost certainly the least interesting of the reasons why connection
can't be activated on a device.
Invent a new error level for it and demote it.
Before:
Error: Connection activation failed: No suitable device found
for this connection (device lo not available because
device is strictly unmanaged).
After
Error: Connection activation failed: No suitable device found
for this connection (device eth0 not available because
profile is not compatible with device (...)).
Diffstat (limited to 'data/nm-shared.xml')
0 files changed, 0 insertions, 0 deletions