Installing packages hangs on plymouth --ping

Bug #1705345 reported by giacof on 2017-07-19
610
This bug affects 117 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Critical
Brian Murray
Xenial
Undecided
Brian Murray
Artful
Undecided
Brian Murray

Bug Description

Impact
------
Many packages call pymouth --ping and if plymouthd is hung then the package installations can fail.

Test Case
---------
1) Run 'sudo /sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid'
2) Observe plymouthd is running ('ps aux | grep plymouth')
3) stop the plymouthd process 'sudo kill -STOP $PID'
4) Run 'plymouth --ping --debug'
5) Observe that the plymouth --ping command hangs

With the version of plymouth from -proposed you will receive the following output instead.

bdmurray@clean-artful-amd64:~$ plymouth --ping --debug
[ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6
[./plymouth.c:82] timeout_handler:ping: timed out waiting for plymouthd
[./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop

Notice how the ping command times out.

Regression Potential
--------------------
Its possible that the timeout of 2 seconds isn't long enough but that seems unlikely.

Original Description
--------------------
I tried to upgrade linux kernel, from 4.10.0-26 to 4.10.0-28, but the installation hung on the following output lines:

sudo apt-get install unrar linux-generic linux-headers-generic linux-image-generic linux-signed-generic linux-signed-image-generic
Configurazione di linux-image-4.10.0-28-generic (4.10.0-28.32)...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-28-generic /boot/vmlinuz-4.10.0-28-generic

Then I looked at the running processes, and noticed this one was blocking post-installation:

plymouth --ping

I could not but manually kill plymouth, then the script resumed just to freeze again a few line later and so on, but is that safe for the installation?

ProblemType: BugDistroRelease: Ubuntu 17.04
Package: plymouth 0.9.2-3ubuntu15
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 19 22:32:14 2017
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
InstallationDate: Installed on 2017-05-22 (58 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. Precision M4800
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed root=/dev/mapper/vg-root ro quiet splash vt.handoff=7SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

giacof (giacof) wrote :
giacof (giacof) on 2017-07-19
description: updated
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
tags: added: artful
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please check to see if the command 'plymouth --ping' continues to hang in a terminal. In the event that it does it would help us out if you could run it under strace e.g. 'strace plymouth --ping' so that we can determine why the process is hanging. Thanks for your assistance!

Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
tags: added: plymouth-ping

I hit this bug while trying to install a kernel upgrade (going from the default 4.13.0-16-generic to 4.13.8-041308, from the mainline PPA). I managed to get an strace from running "plymouth --ping". In the attached trace file, the hang happened on the last call to epoll_pwait.

I also tried attaching strace to plymouthd, but when I did that, it caused plymouthd to immediately exit (which in turn caused plymouth --ping to return). After that, subsequent runs of "plymouth --ping" returned immediately (getting ECONNREFUSED on the "/org/freedesktop/plymouthd" socket), and I haven't been able to reproduce the bug since.

David Wahler (dwahler) wrote :

And here's the trace from plymouthd.

Steve Langasek (vorlon) on 2017-10-18
Changed in plymouth (Ubuntu):
status: Incomplete → New
giacof (giacof) wrote :

Here is mine. It actually hangs on the last line.

antidrugue (antidrugue) on 2017-10-31
Changed in plymouth (Ubuntu):
status: New → Confirmed
Rolands Kusiņš (tower98) wrote :

In attachment output of:
# strace plymouth --ping

Currently used:
# uname -r
4.13.0-16-generic

Trying update to:
4.13.0-17-generic

Killed plymouth --ping from parallel session between upgrade steps.

A. R. (aroman-a) wrote :

Same problem here, apt upgrade froze when doing regular upgrade from 4.13.0-16-generic to 4.13.0-17-generic.

giacof (giacof) on 2017-11-22
description: updated
description: updated
cljk (marcel-pokrandt) wrote :

I have the same issue.... on last dist-ugprade the system hang on updating apport and now on updating the kernel

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-17-generic /boot/vmlinuz-4.13.0-17-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-17-generic /boot/vmlinuz-4.13.0-17-generic

Killling "plymouth --ping" kind of "helps"

Sven (buurman) wrote :

I have the same issue, apparently a sudo apt full-upgrade hung and I interrupted it by shutting down my laptop. Upon trying to install something unrelated it told me I had to run sudo dpkg --configure -a to continue with the previous upgrade. That still hangs:

$ sudo dpkg --configure -a
Setting up linux-image-4.13.0-21-generic (4.13.0-21.24) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-21-generic
vmlinuz(/boot/vmlinuz-4.13.0-21-generic
) points to /boot/vmlinuz-4.13.0-21-generic
 (/boot/vmlinuz-4.13.0-21-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-21-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-21-generic /boot/vmlinuz-4.13.0-21-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-21-generic /boot/vmlinuz-4.13.0-21-generic

I can see using ps axuf that it hangs on a plymouth ping, this hangs in a terminal as well. See the attachment for the output of strace plymouth --ping

Sven (buurman) wrote :

Update to #10:
After killing the original plymouthd process (the one running '@sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid' as root) the installation continued and seems to have installed succesfully.

After reboot ubuntu started succesfully and I can also install the other tools I originally wanted to install.

This seems to be a workaround though I'd advice rebooting immediately after the apt install or update completed successfully, since plymouth is responsible for the splash/login screen and logging out/suspending will likely result in a crash of some kind.

Stephen Early (steve-greenend) wrote :

I am seeing the same thing. plymouthd doesn't hang around after every boot, but it does so a reasonably large percentage of the time. Additionally, when plymouthd continues to run after boot, machine shutdown hangs for a long time before completing (presumably some kind of systemd timeout).

Running strace against plymouthd when it's stuck causes it to exit normally.

root@asp:~# ps axu |grep plymouth
root 320 0.0 0.2 164820 44100 ? S 12:23 0:00 @sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid
root 1166 0.0 0.0 12936 1016 ? Ss 12:23 0:00 /bin/plymouth --wait
root 1311 0.0 0.0 12936 1020 ? S 12:23 0:00 /bin/plymouth quit
root 5398 0.0 0.0 12936 1024 pts/2 SN+ 12:26 0:00 plymouth --ping
root 6023 0.0 0.0 12936 1020 ? S 12:28 0:00 plymouth --ping
root 7537 0.0 0.0 14356 1060 pts/3 S+ 12:58 0:00 grep --color=auto plymouth
root@asp:~# strace -p 320
strace: Process 320 attached
ioctl(10, PIO_CMAP, 0x559a2b77f178) = 0
epoll_ctl(3, EPOLL_CTL_MOD, 10, {EPOLLERR|EPOLLHUP, {u32=730276688, u64=94120643601232}}) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 10, NULL) = 0
rt_sigaction(SIGWINCH, {sa_handler=SIG_DFL, sa_mask=[WINCH], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0996fec140}, {sa_handler=0x7f09975b2820, sa_mask=[WINCH], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0996fec140}, 8) = 0
ioctl(10, TIOCSLCKTRMIOS, {B0 -opost -isig -icanon -echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost -isig -icanon -echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost -isig -icanon -echo ...}) = 0
ioctl(10, SNDCTL_TMR_START or TCSETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(10, TCGETS, {B38400 opost isig icanon echo ...}) = 0
close(10) = 0
close(7) = 0
unlink("/run/plymouth/pid") = 0
sendto(8, "\6", 1, MSG_NOSIGNAL, NULL, 0) = 1
epoll_ctl(3, EPOLL_CTL_DEL, 4, NULL) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 6, NULL) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 7, NULL) = -1 EBADF (Bad file descriptor)
epoll_ctl(3, EPOLL_CTL_DEL, 11, NULL) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 12, NULL) = 0
epoll_ctl(3, EPOLL_CTL_DEL, 8, NULL) = 0
close(11) = 0
close(12) = 0
close(8) = 0
close(2) = 0
exit_group(0) = ?
+++ exited with 0 +++
root@asp:~# ps axu |grep plymouth
root 5405 0.0 0.0 14356 1080 pts/3 S+ 12:59 0:00 grep --color=auto plymouth

dino99 (9d9) wrote :

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

To get a real idea about such issue, do a fresh install, as 'rolling' upgrade brings conflicting/borked old settings.

Changed in plymouth (Ubuntu):
status: Confirmed → Invalid
Steve Langasek (vorlon) on 2018-01-16
Changed in plymouth (Ubuntu):
status: Invalid → Confirmed
Morsok (morsok) wrote :

This is clearly not invalid dino99 i'm having the issue for months now, it's a pain and I installed 17.10 directly.

cljk (marcel-pokrandt) wrote :

Nothing new on this?
On every update I have to call "killall plymouth" several times....

Does it have sth to do with nvidia driver?

Dan McDonald (danmcdonald) wrote :
Download full text (16.3 KiB)

Just want to add some additional details to this that might help.

$ systemctl status
● dan-Lenovo-Y50-70
    State: starting
     Jobs: 6 queued
   Failed: 7 units
    Since: Mon 2018-01-29 07:19:45 MST; 13h ago
...

$ sudo tail -n 15 /var/log/boot.log
[ OK ] Reached target Network.
[ OK ] Started Unattended Upgrades Shutdown.
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
         Starting Network Name Resolution...
         Starting Network Manager Wait Online...
[ OK ] Started Permit User Sessions.
         Starting GNOME Display Manager...
         Starting Hold until boot process finishes up...
         Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started Hostname Service.
[ OK ] Started GNOME Display Manager.
[ OK ] Started Modem Manager.
[ OK ] Started OpenBSD Secure Shell server.

$ systemctl list-units --state=failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed AppArmor initialization
● hylafax.service loaded failed failed LSB: Start and stop the hylafax server
● trousers.service loaded failed failed LSB: starts tcsd
● virtualbox.service loaded failed failed LSB: VirtualBox Linux kernel module
● xinetd.service loaded failed failed LSB: Starts or stops the xinetd daemon.

$ journalctl -u apparmor
-- Logs begin at Mon 2018-01-29 07:19:45 MST, end at Mon 2018-01-29 21:20:13 MST. --
Jan 29 07:19:46 dan-Lenovo-Y50-70 systemd[1]: Starting AppArmor initialization...
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: * Starting AppArmor profiles
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardwar
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor at li
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardwar
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor at li
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Jan 29 07:19:46 dan-Lenovo-Y50-70 apparmor[886]: ...fail!
Jan 29 07:19:46 dan-Lenovo-Y50-70 systemd[1]: apparmor.service: Main process exited, code=exited, status...

dino99 (9d9) wrote :

To all affected users:
- always 'purge' when removing a package, to also remove its settings (avoiding disturbing the system later)
- often run gtkorphan & bleachbit (as root carefully) to get a cleaned system

This report probably should be against a particular app not having the expected settings (ex: webbrowser, above). So purging that (these) app(s) might help.

Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
Steve Langasek (vorlon) wrote :

This has nothing to do with purging packages. Please ignore the previous comment.

Changed in plymouth (Ubuntu):
status: Incomplete → Triaged
Nemanja Boric (4burgos) wrote :

I have the same problem, encountered at the first update after fresh 17.10 installation.

tags: added: id-5a862ec3e29bfd25c55193e7
Steve Langasek (vorlon) on 2018-02-23
Changed in plymouth (Ubuntu):
importance: Undecided → Critical
Pi Delport (pi-delport) wrote :

I'm consistently hitting this bug on kernel upgrades, among other things, on Ubuntu 17.10.

I'm working around it by manually killing the hung "plymouth --ping" process, which seems to make dpkg proceed successfully.

summary: - Installing new kernel hangs on plymouth --ping
+ Installing packages hangs on plymouth --ping
tags: added: bugpattern-written
Brian Murray (brian-murray) wrote :

It'd be interesting to see the output of 'plymouth --debug --ping' when plymouth is hanging. Thanks in advance.

Brian Murray (brian-murray) wrote :

Ah, I was able to recreate the problem of 'plymouth --ping' hanging with the following test case on an Ubuntu 16.04 system.

1) Run 'sudo /sbin/plymouthd --mode=boot --attach-to-session --pid-file=/run/plymouth/pid'
2) Observe plymouthd is running ('ps aux | grep plymouth')
3) stop the plymouthd process 'sudo kill -STOP $PID'
4) Run 'plymouth --ping --debug'

bdmurray@clean-xenial-amd64:~$ plymouth --ping --debug
[ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6

Sven (buurman) wrote :

I just tested plymouth --ping and it hangs again. Aborting and rerunning it with --debug gives the same output as you:

haster@schootbak3:~
$ plymouth --ping
^C

haster@schootbak3:~
$ plymouth --debug --ping
[ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6

Changed in plymouth (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.9.3-1ubuntu4

---------------
plymouth (0.9.3-1ubuntu4) bionic; urgency=medium

  * debian/patches/timeout-for-ping.ptach: Don't wait forever for a reply from
    a ping command. (LP: #1705345)

 -- Brian Murray <email address hidden> Fri, 30 Mar 2018 07:41:54 -0700

Changed in plymouth (Ubuntu):
status: Triaged → Fix Released
Changed in plymouth (Ubuntu Xenial):
status: New → In Progress
Changed in plymouth (Ubuntu Artful):
status: New → In Progress
Changed in plymouth (Ubuntu Xenial):
assignee: nobody → Brian Murray (brian-murray)
Changed in plymouth (Ubuntu Artful):
assignee: nobody → Brian Murray (brian-murray)
description: updated

Hello giacof, or anyone else affected,

Accepted plymouth into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu19 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in plymouth (Ubuntu Artful):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-artful
Łukasz Zemczak (sil2100) wrote :

Hello giacof, or anyone else affected,

Accepted plymouth into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu13.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in plymouth (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed-xenial
Brian Murray (brian-murray) wrote :

Verified in artful:

Setting up plymouth-theme-ubuntu-text (0.9.2-3ubuntu19) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-logo (0.9.2-3ubuntu19) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.125ubuntu12) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-21-generic
bdmurray@clean-artful-amd64:~$ plymouth --ping --debug
[ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6
[./plymouth.c:82] timeout_handler:ping: timed out waiting for plymouthd
[./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop

Brian Murray (brian-murray) wrote :

Verified in xenial:

Setting up plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-label (0.9.2-3ubuntu13.4) ...
Setting up plymouth-theme-ubuntu-logo (0.9.2-3ubuntu13.4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.122ubuntu8.1) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-38-generic
bdmurray@clean-xenial-amd64:~$ plymouth --ping --debug
[ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6
[ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6
[./plymouth.c:82] timeout_handler:ping: timed out waiting for plymouthd
[./ply-boot-client.c:810] ply_boot_client_detach_from_event_loop:detaching from event loop

tags: added: verification-done verification-done-artful verification-done-xenial
removed: verification-needed verification-needed-artful verification-needed-xenial
Harald Sitter (apachelogger) wrote :

Pretty sure the change caused bug #1761478

On Thu, Apr 05, 2018 at 11:08:55AM -0000, Harald Sitter wrote:
> Pretty sure the change caused bug #1761478

That is incorrect.

--
Brian Murray

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.9.2-3ubuntu19

---------------
plymouth (0.9.2-3ubuntu19) artful; urgency=medium

  * debian/patches/timeout-for-ping.ptach: Don't wait forever for a reply from
    a ping command. (LP: #1705345)

 -- Brian Murray <email address hidden> Mon, 02 Apr 2018 10:47:26 -0700

Changed in plymouth (Ubuntu Artful):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for plymouth has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.9.2-3ubuntu13.4

---------------
plymouth (0.9.2-3ubuntu13.4) xenial; urgency=medium

  * debian/patches/timeout-for-ping.ptach: Don't wait forever for a reply from
    a ping command. (LP: #1705345)

 -- Brian Murray <email address hidden> Mon, 02 Apr 2018 10:55:21 -0700

Changed in plymouth (Ubuntu Xenial):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers