projects / NetworkManager.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a0206a4) | patch
manager: make some error reporting a bit more specific
authorLubomir Rintel <lkundrak@v3.sk>
Wed, 30 Mar 2016 07:00:06 +0000 (09:00 +0200)
committerLubomir Rintel <lkundrak@v3.sk>
Wed, 30 Mar 2016 11:24:49 +0000 (13:24 +0200)
commit6b62536ce62a2d34258ee5636ccdf0dac13b7582
tree1223b50db07e7ad55b9dde9c85337312a6aff9fctree | snapshot
parenta0206a4f5eb7f9e4a57941b9949bb2dae44bf1d8commit | diff
manager: make some error reporting a bit more specific

Make sure there's always the device and connection as well as the reason
when a slave activation fails. The slave connection could in fact be
chosen automatically on "nmcli d connect" and the user might not be
aware activation of which connection was attempted:

  $ nmcli d connect enp0s25
  Error: Device activation failed: Master connection not found or invalid
src/nm-manager.c diff | blob | history
Network connection manager and user applications