Bug #6959

Persistence of printer broken in Tails 0.23

Added by mercedes508 2014-03-20 03:55:53 . Updated 2014-07-22 22:51:00 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Persistence
Target version:
Tails_1.1
Start date:
2014-03-20
Due date:
% Done:

100%

Feature Branch:
tails-greeter:bugfix/6959-persistent_printers
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Persistence of printer does not work in Tails 0.23.

Here is how I reproduced that bug:

1. Boot Tails 0.23, create & enable persistence, select printers and few other persistent settings
2. Reboot
3. Enable persistence
4. Add printers (2 actually) and modify other settings that are persistent as well
5. Reboot
6. Printers are not there anymore, but modified settings from 4. are saved.

Subtasks

History

#1 Updated by intrigeri 2014-03-20 04:02:04

  • Status changed from New to Confirmed
  • Assignee set to alant

Reassigning to the one who added this feature. Alan, if you don’t think you can take care of it, please clear the Assignee field. Thanks in advance!

#2 Updated by alant 2014-03-22 18:29:01

I’ll take care of this.

#3 Updated by alant 2014-04-04 12:30:42

  • % Done changed from 0 to 50
  • Feature Branch set to tails-greeter:bugfix/6959-persistent_printers

CUPS was not restared because a test used the old live-persistence.conf path.

I belive this is fixed by tails-greeter:bugfix/6959-persistent_printers.

#4 Updated by alant 2014-04-04 12:41:34

  • Assignee changed from alant to anonym
  • QA Check set to Ready for QA

I’m too lazy to build a package and upload it to experimental for such a tiny change. Dear RM, if you requires it just ask and I’ll do it.

#5 Updated by intrigeri 2014-05-02 11:14:46

  • Target version set to Tails_1.1

Too bad the fix for this serious regression was not merged yet, and the regression is presumably still present in 1.0, while the bugfix was proposed way ahead of the freeze. Let’s do better next time:

  • anonym, as a RM, you’ll need to monitor the “Ready for QA” tickets, and the pull requests sent on the ML more closely.
  • Alan, when requesting a merge, please set the milestone to the version of Tails you want your patch included in.

Thanks!

#6 Updated by intrigeri 2014-05-02 17:49:32

  • Status changed from Confirmed to In Progress

#7 Updated by anonym 2014-05-14 07:22:05

  • 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
  • Type of work changed from Research to Code

Sorry for missing this for 1.0. Merged now!

#8 Updated by BitingBird 2014-07-22 22:51:00

  • Status changed from Fix committed to Resolved