Introduction

Bugs relating to Plymouth package

How to file

When filing a bug against Plymouth, it is always necessary to provide:

1. A detailed description of the problem, including any error message or special visual phenomenon you might notice.

2. The file created by this command in a terminal : sudo lspci -vvnn > lspci-vvnn.txt

3. The file created by this command in a terminal : cat /boot/grub/grub.cfg > grub.cfg

4. The file created by this command in a terminal : uname -a > uname-a.txt

5. A photo of the problem is often very useful.

Bug tags

todo

Debugging procedure

Please see https://wiki.ubuntu.com/Plymouth#Debugging

How to Triage

When triaging bugs in Plymouth, it's important to make sure that the bug describes a genuine bug in Plymouth. If a bug describes a problem that might not be related to Plymouth, the bug reporter should be asked to try reproducing the bug without Plymouth (as indicated in the Debugging procedure). When the bug can be reproduced without plymouth, the package should be changed for the appropriate one.
It's also important to make sure that the bug reporter gave sufficient information like described in the "How to file" section. When some information are missing, it's always a good idea to set the status of the bug to Incomplete, subscribe yourself to the bug report and to ask the reporter for the missing information.

Stock Reply

1. Please use this one-time boot procedure to get a plymouth log.
2. Power on system
 1. Hold down the `SHIFT` key until the Grub boot menu appears
 2. Type "`e`" to edit the default kernel command-line
 3. Use the arrow keys to go to the end of the line which starts "`linux /boot/vmlinuz ...`"
 4. Add a space character, followed by "`plymouth:debug`"
 <<BR>>Notes:
   * If you're interested in the overall boot, you may wish to remove the "`quiet`" keyword too)
 5. Type `CONTROL+x` to boot
 6. Once the system has booted, you can view all the Plymouth debug output in file `var/log/plymouth-debug.log`.
 7. Please attach the /var/log/plymouth-debug.log to this bug report.

Thanks in advance.

Known bugs

Non-bugs

todo

CategoryBugSquad CategoryDebugging