/etc/init.d/screen-cleanup causes ordering cycle when package is removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
screen (Ubuntu) |
Fix Released
|
Low
|
Axel Beckert |
Bug Description
I recently rebooted my computer, and NetworkManager didn't come online. Snooping dmesg revealed the problem:
[ 16.371556] systemd[1]: Breaking ordering cycle by deleting job network.
[ 16.371561] systemd[1]: Job network.
[ 16.371722] systemd[1]: Found ordering cycle on NetworkManager-
[ 16.371727] systemd[1]: Found dependency on NetworkManager.
[ 16.371732] systemd[1]: Found dependency on basic.target/start
[ 16.371736] systemd[1]: Found dependency on sockets.
[ 16.371739] systemd[1]: Found dependency on cups.socket/start
[ 16.371743] systemd[1]: Found dependency on sysinit.
[ 16.371747] systemd[1]: Found dependency on screen-
[ 16.371751] systemd[1]: Found dependency on remote-
[ 16.371754] systemd[1]: Found dependency on openafs-
[ 16.371758] systemd[1]: Found dependency on network-
[ 16.371762] systemd[1]: Found dependency on NetworkManager-
[ 16.371766] systemd[1]: Breaking ordering cycle by deleting job NetworkManager.
[ 16.371771] systemd[1]: Job NetworkManager.
Manually running `sudo systemctl start NetworkManager` brought it back online. But there shouldn't be an ordering cycle!
The problem seems to be that sockets wants cups, and then through a hilarious chain of events we hit openafs-client which obviously needs network. So for some reason, wants constraints are being honored too strictly.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu5
ProcVersionSign
Uname: Linux 3.19.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sat Jun 6 15:49:54 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-21 (562 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 7762K3U
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-05-29 (8 days ago)
dmi.bios.date: 02/21/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET25WW (1.11 )
dmi.board.name: 7762K3U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7762K3U
dmi.product.
dmi.sys.vendor: LENOVO
Related branches
Changed in screen (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Axel Beckert (xtaran) |
Changed in screen (Ubuntu): | |
status: | In Progress → Fix Committed |
[ 16.371747] systemd[1]: Found dependency on screen- cleanup. service/ start
This seems to be the culprit. screen-cleanup is a service which needs to run before the very early sysinit.target, but requires remote-fs.target, which is unsatisfiable once you have remote file systems like openafs. Is that coming from a (third-party?) package or is that something that you added? Please give the output of
systemctl cat screen-cleanup cleanup. service init.d/ screen- cleanup
dpkg -S screen-
Thanks!