Public bug reported:
Crashes on startup. Maybe similar to #927636, but that's for 12.04,
while this was on 18.04
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 13 09:06:32 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-04-07 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=dd9ceeab-5f70-4159-8458-4d23eb73a2e4 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
--attach-to-session
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=dd9ceeab-5f70-4159-8458-4d23eb73a2e4 ro quiet splash vt.handoff=1
SegvAnalysis:
Segfault happened at: 0x7f779e6f9480 <script_obj_deref_direct>: cmpl
$0x1,(%rdi)
PC (0x7f779e6f9480) ok
source "$0x1" ok
destination "(%rdi)" (0x61632f6d72642f30) not located in a known VMA region
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_obj_deref_direct () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
script_obj_as_custom () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
script_execute_object () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
script_lib_plymouth_on_display_normal () from
/usr/lib/x86_64-linux-gnu/plymouth/script.so
?? () from /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: 07/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.00
dmi.board.name: X370 Gaming-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP3.00:bd07/19/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash bionic indeed need-amd64-retrace
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763729
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1763729/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
