Bug #7338
NetworkManager persistence setting is not migrated
100%
Description
When migrating to Tails/Wheezy a Tails/Squeeze with NM persistence enabled, one “loses” their persistent networks. I think that’s acceptable. What is not acceptable is that if one then re-creates their network, and reboots, their settings are lost: we keep persisting the old location, but don’t start persisting the new one.
When the /home/amnesia/.gconf/system/networking/connections
persistence preset is enabled, live-persist should automatically make /etc/NetworkManager/system-connections
persistent.
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2014-05-30 |
History
#1 Updated by BitingBird 2014-05-29 17:13:36
I think it’s ok to forget the persistent networks, as long as it’s in the known issues for the release.
#2 Updated by intrigeri 2014-05-30 04:05:58
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Feature Branch set to bugfix/7338-migrate-nm-persistence-setting
#3 Updated by intrigeri 2014-05-30 13:30:31
- Assignee changed from intrigeri to anonym
- % Done changed from 10 to 40
- QA Check set to Ready for QA
#4 Updated by intrigeri 2014-05-30 13:33:32
- blocked by
Bug #7343: Changed t-p-s numeric UID breaks persistence.conf access rights check added
#5 Updated by anonym 2014-06-12 14:40:39
- Assignee changed from anonym to intrigeri
- QA Check changed from Ready for QA to Dev Needed
See https://mailman.boum.org/pipermail/tails-dev/2014-June/006119.html
#6 Updated by intrigeri 2014-06-21 20:10:16
- Assignee changed from intrigeri to anonym
- % Done changed from 40 to 50
- QA Check changed from Dev Needed to Ready for QA
Just tested, disabling pre-Wheezy NM persistence setting works fine for me.
#7 Updated by anonym 2014-06-22 11:37:38
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#8 Updated by BitingBird 2014-07-22 22:56:40
- Status changed from Fix committed to Resolved