Bug #11938

Deal with how NetworkManager dispatcher scripts are called on Stretch

Added by intrigeri 2016-11-16 18:13:05 . Updated 2016-11-16 19:01:48 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Target version:
Tails_3.0
Start date:
2016-11-16
Due date:
% Done:

100%

Feature Branch:
bugfix/11937-upgrade-network-manager
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/00-save-env: 6: [: =: unexpected o
Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/10-tor.sh: 7: [: =: unexpected ope
Nov 16 18:07:22 amnesia nm-dispatcher[3094]: /etc/NetworkManager/dispatcher.d/60-tor-ready.sh: 4: [: =: unexpect

… which means that $1 is empty.

Subtasks

History

#1 Updated by intrigeri 2016-11-16 18:22:20

I’ve see these scripts called with an empty 1st arg, and the 2nd being “connectivity-change”. Quoting $1 everywhere should deal with that.

#2 Updated by intrigeri 2016-11-16 18:36:47

  • Feature Branch set to bugfix/11937-upgrade-network-manager

#3 Updated by intrigeri 2016-11-16 19:01:48

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:5f51d1e8cce06518a00a63c4c891b52ddd969a57.