Hi,

It happens almost every day, so testing won't be a problem.

Regards,

Jeroen


Op do 12 apr. 2018 19:51 schreef Brian Murray <email address hidden>:

> Does this happen to anybody on a regular basis? Would you be able to
> test a package from a PPA and confirm that the crash is no longer
> happening?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1761948).
> https://bugs.launchpad.net/bugs/1745406
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   In Progress
> Status in plymouth package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello,
>
>   I do not know why this happened
>
>   Regards,
>   --
>   Cristian
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: plymouth 0.9.3-1ubuntu1
>   Uname: Linux 4.15.0-041500rc9-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   Date: Thu Jan 25 09:05:56 2018
>   DefaultPlymouth:
> /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   ExecutableTimestamp: 1516196236
>   InstallationDate: Installed on 2017-10-13 (103 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170926)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
>   ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
> --attach-to-session
>   ProcCwd: /
>   ProcEnviron:
>    LANG=es_CL.UTF-8
>    LANGUAGE=es_CL:es
>    PATH=(custom, no user)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   SegvAnalysis:
>    Segfault happened at: 0x7faef226f480 <script_obj_deref_direct>:
> cmpl   $0x1,(%rdi)
>    PC (0x7faef226f480) ok
>    source "$0x1" ok
>    destination "(%rdi)" (0x00000000) not located in a known VMA region
> (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>    script_obj_deref_direct () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>    script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>    script_execute_object () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>    script_lib_plymouth_on_display_normal () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>    () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>   TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-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/15/2013
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: P14AAJ
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: SAMSUNG_NP1234567890
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: FAB1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
>   dmi.product.family: ChiefRiver System
>   dmi.product.name: 530U3C/530U4C
>   dmi.product.version: 0.1
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plymouth/+bug/1745406/+subscriptions
>