Bug #10591

CUPS fails to start with read-only persistent configuration on Jessie

Added by intrigeri 2015-11-20 01:06:47 . Updated 2015-11-20 03:00:02 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_2.0
Start date:
2015-11-20
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

Nov 20 09:02:28 amnesia kernel: audit: type=1400 audit(1448010148.604:31): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/live/persistence/TailsData_unlocked/cups-configuration/cups-files.conf" pid=4657 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

Subtasks

Related issues

Blocks Tails - Feature #7563: Update the automated test suite for Jessie ISO images Resolved 2014-11-26 2016-01-15

History

#1 Updated by intrigeri 2015-11-20 01:07:00

  • blocks Feature #7563: Update the automated test suite for Jessie ISO images added

#2 Updated by intrigeri 2015-11-20 01:08:04

  • Priority changed from Elevated to High

anonym, it’s the root cause of the failure of Scenario: Writing files first to a read/write-enabled persistent partition, and then to a read-only-enabled persistent partition # features/persistence.feature:20.

#3 Updated by intrigeri 2015-11-20 01:35:27

  • Subject changed from CUPS fails to start with persistent configuration on Jessie to CUPS fails to start with read-only persistent configuration on Jessie

#4 Updated by intrigeri 2015-11-20 01:56:58

We’ve decided that read-only persistence support is best effort (Bug #8423) but here it would probably take me longer to adjust the test suite to this bug, than to actually fix it.

#5 Updated by intrigeri 2015-11-20 02:52:54

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

Applied in changeset commit:1863d4a37a2ef4f1c1e49b44a0fe4ffdb1df1c96.

#6 Updated by intrigeri 2015-11-20 03:00:02

  • Assignee deleted (intrigeri)