Bug #16184: Intermittent test failures on the devel branch: fails to login "Failed to fully start up daemon: Permission denied"

Bug #16184

Intermittent test failures on the devel branch: fails to login "Failed to fully start up daemon: Permission denied"

Added by intrigeri 2018-12-03 13:41:12 . Updated 2019-01-30 11:50:05 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Tails_3.12

Start date:

2018-12-03

Due date:

% Done:

100%

Feature Branch:

bugfix/16352-16184-systemd-v240+force-all-tests

Type of work:

Code

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

Keeping track of regressions brought by tracking systemd/stretch-backports:

Dec 03 11:36:29 amnesia gdm-password][4026]: pam_unix(gdm-password:session): session opened for user amnesia by (uid=0)
Dec 03 11:36:29 amnesia systemd[1]: Stopped /run/user/0 mount wrapper.
Dec 03 11:36:29 amnesia systemd[1]: Started /run/user/1000 mount wrapper.
Dec 03 11:36:29 amnesia systemd[1]: Created slice User Slice of UID 1000.
Dec 03 11:36:29 amnesia systemd[1]: Starting User Manager for UID 1000...
Dec 03 11:36:29 amnesia systemd-logind[1331]: New session 5 of user amnesia.
Dec 03 11:36:29 amnesia systemd[1]: Started Session 5 of user amnesia.
Dec 03 11:36:29 amnesia systemd[4040]: pam_unix(systemd-user:session): session opened for user amnesia by (uid=0)
Dec 03 11:36:29 amnesia systemd[4040]: Failed to fully start up daemon: Permission denied
Dec 03 11:36:29 amnesia systemd[4041]: pam_unix(systemd-user:session): session closed for user amnesia
Dec 03 11:36:29 amnesia systemd[1]: user@1000.service: Failed with result 'protocol'.
Dec 03 11:36:29 amnesia systemd[1]: Failed to start User Manager for UID 1000.
Dec 03 11:36:29 amnesia systemd[1]: user-runtime-dir@1000.service: Unit not needed anymore. Stopping.
Dec 03 11:36:29 amnesia systemd[1]: Stopping /run/user/1000 mount wrapper...
Dec 03 11:36:29 amnesia gdm-password][4026]: pam_systemd(gdm-password:session): Failed to create session: Start job for unit user@1000.service failed with 'failed'
Dec 03 11:36:29 amnesia gdm-session-worker[4026]: Entering PostLogin

This looks like a systemd bug:

It happens only rarely, is unlikely to affect human users, and is probably fixed in systemd v240. So for now, let’s ignore this and if it gets too painful, upgrade to systemd v240.

Subtasks

Related issues

Related to Tails - ~~Bug #16100~~: Fix systemd CVE-2018-15687	Rejected	2018-11-05
Related to Tails - ~~Bug #16352~~: Fix systemd vulnerabilities: CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866	Resolved	2019-01-13
Blocks Tails - ~~Feature #15507~~: Core work 2019Q1: Foundations Team	Resolved	2018-04-08

History

#1 Updated by intrigeri 2018-12-03 13:41:20

related to ~~Bug #16097~~: Memory erasure tests regression on the devel branch added

#2 Updated by intrigeri 2018-12-03 13:41:29

related to ~~Bug #16100~~: Fix systemd CVE-2018-15687 added

#3 Updated by intrigeri 2018-12-03 13:43:17

blocks ~~Feature #15507~~: Core work 2019Q1: Foundations Team added

#4 Updated by intrigeri 2018-12-03 15:47:43

Assignee set to intrigeri

#5 Updated by intrigeri 2019-01-10 19:43:03

related to deleted (~~~~Bug #16097~~: Memory erasure tests regression on the devel branch~~)

#6 Updated by intrigeri 2019-01-10 20:06:38

Description updated

#7 Updated by intrigeri 2019-01-10 20:07:05

Description updated

#8 Updated by intrigeri 2019-01-10 20:07:38

Description updated

#9 Updated by intrigeri 2019-01-10 20:18:39

On the devel branch, this error appears 36 times, among 145 *.journal files saved on test suite failures. So it does not happen as rarely as I thought.

I’ll quicky check why I thought this “is unlikely to affect human users”. If I don’t easily find a convincing answer, I’ll work on the upgrade to v240, which we might need anyway due to a local root exploit that was disclosed yesterday by Qualys.

#10 Updated by intrigeri 2019-01-13 08:28:13

related to ~~Bug #16352~~: Fix systemd vulnerabilities: CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 added

#11 Updated by intrigeri 2019-01-13 11:29:58

Status changed from Confirmed to In Progress

Applied in changeset commit:tails|407d9a0f96d5c2c1b6d613f0864e22f4db781f73.

#12 Updated by intrigeri 2019-01-13 18:34:41

% Done changed from 0 to 50
Feature Branch set to bugfix/16352-16184-systemd-v240+force-all-tests

The test suite has not been run often enough with systemd v240 for this to have any statistical significance, but FWIW: this error is nowhere to be found in the *.journal saved by failed scenarios on Jenkins nor in my local test suite runs. This is consistent with my initial research (see ticket description) that suggests the root cause for this problem was fixed in v240.

#13 Updated by intrigeri 2019-01-13 18:40:47

Assignee deleted (~~intrigeri~~)
QA Check set to Ready for QA

Same as ~~Bug #16352~~.

#14 Updated by lamby 2019-01-14 14:07:31

Assignee set to lamby

Mon 14 14:06 < intrigeri> lamby: OK. So please take <del><a class='issue tracker-1 status-3 priority-6 priority-default closed child' href='/code/issues/16352' title='Fix systemd vulnerabilities: CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866'>Bug #16352</a></del> + <del><a class='issue tracker-1 status-3 priority-4 priority-default closed child' href='/code/issues/16184' title='Intermittent test failures on the devel branch: fails to login &#34;Failed to fully start up daemon: Permission denied&#34;'>Bug #16184</a></del> (same branch). And anonym offered to do the other remaining one (<del><a class='issue tracker-1 status-3 priority-5 priority-default closed child' href='/code/issues/16261' title='Upgrade Thunderbird to 60.4'>Bug #16261</a></del>)

Taking