Yeah every login after boot
On Fri., 13 Apr. 2018, 5:01 am Jeroen Donkervoort, < <email address hidden>> wrote:
> 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 > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1762146). > 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 >
Yeah every login after boot
On Fri., 13 Apr. 2018, 5:01 am Jeroen Donkervoort, <
<email address hidden>> wrote:
> Hi, /bugs.launchpad .net/bugs/ 1745406 obj_deref_ direct( ) 041500rc9- generic x86_64 plymouth/ themes/ ubuntu- logo/ubuntu- logo.plymouth tamp: 1516196236 /@/boot/ vmlinuz- 4.15.0- 041500rc9- generic 707d0f89- 4b1d-4432- 9d50-6058dc4c1e e9 ro rootflags=subvol=@ /run/plymouth/ pid /@/boot/ vmlinuz- 4.15.0- 041500rc9- generic 707d0f89- 4b1d-4432- 9d50-6058dc4c1e e9 ro rootflags=subvol=@ obj_deref_ direct> : obj_deref_ direct () at x86_64- linux-gnu/ plymouth/ script. so obj_as_ custom () at x86_64- linux-gnu/ plymouth/ script. so execute_ object () at x86_64- linux-gnu/ plymouth/ script. so lib_plymouth_ on_display_ normal () at x86_64- linux-gnu/ plymouth/ script. so x86_64- linux-gnu/ plymouth/ script. so plymouth/ themes/ ubuntu- text/ubuntu- text.plymouth obj_deref_ direct( ) asset.tag: Base Board Asset Tag NP1234567890 asset.tag: No Asset Tag version: 0.1 echnologiesLtd. :bvrP14AAJ: bd04/15/ 2013:svnSAMSUNG ELECTRONICSCO. ,LTD.:pn530U3C/ 530U4C: pvr0.1: rvnSAMSUNGELECT RONICSCO. ,LTD.:rnSAMSUNG _NP1234567890: rvrFAB1: cvnSAMSUNGELECT RONICSCO. ,LTD.:ct9: cvr0.1: version: 0.1 /bugs.launchpad .net/plymouth/ +bug/1745406/ +subscriptions /bugs.launchpad .net/bugs/ 1745406 obj_deref_ direct( ) 041500rc9- generic x86_64 plymouth/ themes/ ubuntu- logo/ubuntu- logo.plymouth tamp: 1516196236 /@/boot/ vmlinuz- 4.15.0- 041500rc9- generic 707d0f89- 4b1d-4432- 9d50-6058dc4c1e e9 ro rootflags=subvol=@ quiet /run/plymouth/ pid /@/boot/ vmlinuz- 4.15.0- 041500rc9- generic 707d0f89- 4b1d-4432- 9d50-6058dc4c1e e9 ro rootflags=subvol=@ quiet obj_deref_ direct> : obj_deref_ direct () at x86_64- linux-gnu/ plymouth/ script. so obj_as_ custom () at /usr/lib/ x86_64- linux-gnu/ plymouth/ script. so execute_ object () at /usr/lib/ x86_64- linux-gnu/ plymouth/ script. so lib_plymouth_ on_display_ normal () at x86_64- linux-gnu/ plymouth/ script. so x86_64- linux-gnu/ plymouth/ script. so plymouth/ themes/ ubuntu- text/ubuntu- text.plymouth obj_deref_ direct( ) asset.tag: Base Board Asset Tag NP1234567890 asset.tag: No Asset Tag version: 0.1 echnologiesLtd. :bvrP14AAJ: bd04/15/ 2013:svnSAMSUNG ELECTRONICSCO. ,LTD.:pn530U3C/ 530U4C: pvr0.1: rvnSAMSUNGELECT RONICSCO. ,LTD.:rnSAMSUNG _NP1234567890: rvrFAB1: cvnSAMSUNGELECT RONICSCO. ,LTD.:ct9: cvr0.1: version: 0.1 /bugs.launchpad .net/plymouth/ +bug/1745406/ +subscriptions
>
> 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:/
> >
> > Title:
> > plymouthd crashed with SIGSEGV in script_
> >
> > 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-
> > ApportVersion: 2.20.8-0ubuntu6
> > Architecture: amd64
> > Date: Thu Jan 25 09:05:56 2018
> > DefaultPlymouth:
> > /usr/share/
> > ExecutablePath: /sbin/plymouthd
> > ExecutableTimes
> > 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=
> > root=UUID=
> quiet
> > splash vt.handoff=7
> > ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
> > --attach-to-session
> > ProcCwd: /
> > ProcEnviron:
> > LANG=es_CL.UTF-8
> > LANGUAGE=es_CL:es
> > PATH=(custom, no user)
> > ProcFB: 0 inteldrmfb
> > ProcKernelCmdLine: BOOT_IMAGE=
> > root=UUID=
> quiet
> > splash vt.handoff=7
> > SegvAnalysis:
> > Segfault happened at: 0x7faef226f480 <script_
> > 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_
> > /usr/lib/
> > script_
> /usr/lib/
> > script_
> /usr/lib/
> > script_
> > /usr/lib/
> > () at /usr/lib/
> > TextPlymouth:
> /usr/share/
> > Title: plymouthd crashed with SIGSEGV in script_
> > 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.
> > dmi.board.name: SAMSUNG_
> > dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> > dmi.board.version: FAB1
> > dmi.chassis.
> > dmi.chassis.type: 9
> > dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
> > dmi.chassis.
> > dmi.modalias:
> >
> dmi:bvnPhoenixT
> > dmi.product.family: ChiefRiver System
> > dmi.product.name: 530U3C/530U4C
> > dmi.product.
> > dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >
> > To manage notifications about this bug go to:
> > https:/
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1762146).
> https:/
>
> Title:
> plymouthd crashed with SIGSEGV in script_
>
> 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-
> ApportVersion: 2.20.8-0ubuntu6
> Architecture: amd64
> Date: Thu Jan 25 09:05:56 2018
> DefaultPlymouth:
> /usr/share/
> ExecutablePath: /sbin/plymouthd
> ExecutableTimes
> 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=
> root=UUID=
> splash vt.handoff=7
> ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
> --attach-to-session
> ProcCwd: /
> ProcEnviron:
> LANG=es_CL.UTF-8
> LANGUAGE=es_CL:es
> PATH=(custom, no user)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> splash vt.handoff=7
> SegvAnalysis:
> Segfault happened at: 0x7faef226f480 <script_
> 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_
> /usr/lib/
> script_
> script_
> script_
> /usr/lib/
> () at /usr/lib/
> TextPlymouth: /usr/share/
> Title: plymouthd crashed with SIGSEGV in script_
> 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.
> dmi.board.name: SAMSUNG_
> dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.board.version: FAB1
> dmi.chassis.
> dmi.chassis.type: 9
> dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
> dmi.chassis.
> dmi.modalias:
> dmi:bvnPhoenixT
> dmi.product.family: ChiefRiver System
> dmi.product.name: 530U3C/530U4C
> dmi.product.
> dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>
> To manage notifications about this bug go to:
> https:/
>