[Bug 1767760] Re: plymouth timeout prevents x-server from correct initialization

Thomas Schustek thomas at schustek.com
Sun Apr 29 07:33:55 UTC 2018


As already noted increasing the time-out up to 6.0 seconds works for me.

** Patch added: "Increases time-out for plymouth ping"
   https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1767760/+attachment/5129931/+files/timeout-for-ping-fix.patch

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

Title:
  plymouth timeout prevents x-server from correct initialization

Status in plymouth package in Ubuntu:
  New

Bug description:
  After upgrading from plymouth_0.9.2-3ubuntu13.3 to
  plymouth_0.9.2-3ubuntu13.4 about 50% of all x-server initializations
  failed and Xorg crashed after entering fail-save-mode. A typical
  reason for this behaviour was that it could not acquire DRM interface
  /dev/dri/card0 not have been release before by plymouth after a time-
  out condition.

  Downgrading to plymouth_0.9.2-3ubuntu13.3 fixed the issue same as
  elongating the time-out-interval from 2.0 to at least 6.0 seconds in
  src/client/plymouth.c.

  Ubuntu 16.04.4 is running on a about 9-year-old notebook with an Intel
  Core 2 Duo U9400 @ 1.4 GHz CPU and a non-solid-state-disk. Its rather
  complex xkb configuration takes more than a second to compile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1767760/+subscriptions



More information about the foundations-bugs mailing list