plymouth --ping hangs, stalling dpkg configure

Bug #1715830 reported by nachokb
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Installed updates via apt, and it was getting stuck on keyboard-configuration.

I started playing around with its postinst script and realized it was stuck on
plymouth --ping (so I removes that line and had the script assume plymouth was
present as it is). Now I find the same problem on console-setup-linux.

Will fix doing the same thing, but now I'm sure this means that plymought has
really frozen on my system.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: plymouth 0.9.2-3ubuntu16
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 8 05:37:57 2017
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
InstallationDate: Installed on 2017-09-04 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170903)
MachineType: ASUSTeK COMPUTER INC. N56VZ
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic.efi.signed root=UUID=06d5f09c-095f-48b5-b863-9932af30cf73 ro quiet splash vt.handoff=7
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic.efi.signed root=UUID=06d5f09c-095f-48b5-b863-9932af30cf73 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
nachokb (nachokb) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
horizon brave (horizonbrave) wrote :

I've got the same bug after installing today's 17.10 daily image and trying to update with Software Updater. I added a comment here because I don't understand bug #1705345 (which this bug should be a duplicate of). Sorry for that

Revision history for this message
Jordon Moss (strikerthehedgefox) wrote :

Just got this today.

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.