[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

[Daniel van Vugt]

My comment in #27 was current for daily images up to a few days ago.

Today I am using image 20180404 and can't reproduce the issue. So
Incomplete.

Like Doug I do find many systems still hang instead of shutting down
with 20180404, but there are different reasons for those and the error
message this bug is about does not appear. So they should be different
bugs.


** Changed in: systemd (Ubuntu Bionic)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Bionic:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions