Bug #7338
NetworkManager persistence setting is not migrated
Start date:
05/29/2014
Due date:
% Done:
100%
Feature Branch:
bugfix/7338-migrate-nm-persistence-setting
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:
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.
Related issues
History
#1 Updated by BitingBird over 5 years ago
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 over 5 years ago
- 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 over 5 years ago
- Assignee changed from intrigeri to anonym
- % Done changed from 10 to 40
- QA Check set to Ready for QA
#4 Updated by intrigeri over 5 years ago
- Blocked by Bug #7343: Changed t-p-s numeric UID breaks persistence.conf access rights check added
#5 Updated by anonym over 5 years ago
- Assignee changed from anonym to intrigeri
- QA Check changed from Ready for QA to Dev Needed
#6 Updated by intrigeri over 5 years ago
- 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 over 5 years ago
- 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 about 5 years ago
- Status changed from Fix committed to Resolved