package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned

Bug #1755010 reported by Ben Romer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Tried upgrading from Artful to Bionic this weekend, had problems.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 11 13:47:24 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-10-08 (153 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. G752VY
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt 1.6~beta1
SourcePackage: systemd
Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VY.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Ben Romer (bromer) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.