[Bug 1756434] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Apport retracing service
1756434 at bugs.launchpad.net
Fri Mar 16 20:24:50 UTC 2018
*** This bug is a duplicate of bug 1745406 ***
https://bugs.launchpad.net/bugs/1745406
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1745406, so is being marked as such. Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081724/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081727/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081735/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081737/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081738/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081739/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1756434/+attachment/5081740/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1745406
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1756434
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Status in plymouth package in Ubuntu:
New
Bug description:
i do not know
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Wed Mar 14 22:12:55 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-03-03 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
JournalErrors:
-- Logs begin at Sat 2018-03-03 21:27:19 EET, end at Fri 2018-03-16 22:11:21 EET. --
Μάρ 16 21:46:38 hostname kernel: nouveau 0000:01:00.0: fifo: read fault at 000021d000 engine 05 [BAR2] client 07 [HOST_CPU] reason 02 [PTE] on channel -1 [007fd76000 unknown]
Μάρ 16 21:46:42 hostname spice-vdagent[1190]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Μάρ 16 21:47:05 hostname pulseaudio[1060]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
MachineType: Gigabyte Technology Co., Ltd. EP45-DS4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=db9e1b88-162d-48b0-930c-daaeda7a7438 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=db9e1b88-162d-48b0-930c-daaeda7a7438 ro quiet splash vt.handoff=1
SegvAnalysis:
Segfault happened at: 0x7f37b4da9480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
PC (0x7f37b4da9480) 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: 09/30/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd09/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1756434/+subscriptions
More information about the foundations-bugs
mailing list