Project

General

Profile

Bug #17026

Long delay while rebooting after applying an automatic upgrade

Added by intrigeri 2 months ago. Updated 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:
Upgrader

Description

This got reported for the 4.0~beta1 → 4.0~beta2 upgrade. I don't know yet if 3.x is affected.

User report:

The behavior that the first shutdown after the incremental upgrade takes
much longer was there again.
I pressed Esc and its one line which is constantly changing between:

(1 of 2) A stop job is running for User Manager for UID 112 ( x / 2 min)
and
(2 of 2) A stop job is running for User Manager for UID 1000 ( x / 2 min)

The x is counting up till 1 min 30 s then:
[ok] Stopped User Manager for UID 112.

and the shutdown process is going on.

On every other shutdown the whole shutdown process is done after a few
seconds but after an incremental update it takes minimum one and a half
minutes so i think at least after an upgrade the user should see that his
computer isnt done with shutting down after a few seconds.

Related issues

Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 08/31/2018
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 2 months ago

#2 Updated by intrigeri 2 months ago

  • Target version deleted (Tails_4.0)

UID 112 is Debian-gdm so I was tempted to blame the crazy GDM hacks I've introduced in 4.0~beta2. Except this problem happens while still running 4.0~beta1, so this can't be the explanation.

Besides, the user says "was there again", which suggests they've seen the problem in earlier automatic upgrades. Given that's the first time we offer automatic upgrades on 4.x, it implies they've seen it on 3.x ⇒ not a regression and not a 4.0 release blocker.

Regardless, something wrong is happening that makes user\@112.service take 1.5 minutes to stop. Next step to investigate this would be, after applying an automatic upgrade but before restarting, to:

  • check what's running in this CGroup
  • try to stop user\@112.service manually and see what part of it does not stop quickly

#3 Updated by intrigeri 2 months ago

  • Related to Feature #14544: Spend software developer time on smallish UX improvements added

Also available in: Atom PDF