Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P plymouth
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 85
    • Issues 85
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • plymouth
  • plymouth
  • Merge requests
  • !44

The source project of this merge request has been removed.
Closed
Created Jul 12, 2019 by Sebastien@seb128
  • Report abuse
Report abuse

Set default DeviceTimeout to 5.0, otherwise boot fails

  • Overview 6
  • Changes 1

The patch was added to Ubuntu by Dimitri John Ledkov when Ubuntu updated to 0.9.3 with that comment

' - Add a patch to unconditionally set DeviceTimeout to a non-zero value to prevent plymouthd asserts on boot.'

There is no details on the assert nor bug report reference that I can see. The default value in the config is non null but maybe it can be an issue for users who have a configuration file not including that key?

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: default-device-timeout