[Impact]
Plymouth is crashing regularly for users of releases before Ubuntu 18.04. The crash reporting dialogs must be annoying for those experiencing the crash.
[Test Case]
We have not figured out how to recreate the crash, but the errors bucket (https://errors.ubuntu.com/bucket/?id=/sbin/plymouthd%3A11%3Ascript_obj_deref_direct%3Ascript_obj_as_custom%3Ascript_execute_object_with_parlist%3Ascript_execute_object%3Ascript_lib_plymouth_on_update_status) is updated hourly from people who encounter the crash. Checking the errors bucket for an absence of the new version should be sufficient to confirm that the crash is not occurring.
[Regression Potential]
The fix for this bug involved dropping an undocumented patch from plymouth which is rather risky. That being said the fix has been in Ubuntu 18.04 since mid April and no regressions have turned up. While I'm checking the Error Tracker for new plymouth crashes regularly it would be best to let this SRU age for longer than the 7 day period to be sure nothing is amiss.
Ubuntu 12.04 LTS (development branch)
ProblemType: CrashDistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 6 07:03:15 2012
DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
MachineType: Foxconn AMD HDZS01
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7effe6b50ea0 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
PC (0x7effe6b50ea0) ok
source "$0x1" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11SourcePackage: plymouth
StacktraceTop:
script_obj_deref_direct () from /lib/plymouth/script.so
script_obj_as_custom () from /lib/plymouth/script.so
script_execute_object () from /lib/plymouth/script.so
script_lib_plymouth_on_update_status () from /lib/plymouth/script.so
?? ()
TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A93F1022
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: AHD1S
dmi.board.vendor: Foxconn
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA93F1022:bd04/19/2011:svnFoxconn:pnAMDHDZS01:pvrTobefilledbyO.E.M.:rvnFoxconn:rnAHD1S:rvr:
dmi.product.name: AMD HDZS01
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Foxconn
StacktraceTop: obj_deref_ direct (obj=0x0) at ./script- object. c:132 obj_as_ custom (obj=<optimized out>, user_func= 0x7effe6b509e0 <script_ obj_execute> , user_data= 0x7fff9f304cd0) at ./script- object. c:237 execute_ object_ with_parlist (parameter_ data=0x1630890, this=0x0, obj=0x0, state=0x160b6c0) at ./script- execute. c:286 execute_ object (state=0x160b6c0, function=0x0, this=0x0, first_arg= 0x163c1d0) at ./script- execute. c:667 lib_plymouth_ on_update_ status (state=0x160b6c0, data=0x161b9a0, new_status= <optimized out>) at ./script- lib-plymouth. c:242
script_
script_
script_
script_
script_