plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Bug #1751030 reported by sokin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

cannot see folders of Nas4free server

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
Uname: Linux 4.13.0-33-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 16 18:30:22 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-01-30 (23 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Gigabyte Technology Co., Ltd. 965P-DS4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-33-generic root=UUID=36c9b4f3-91a4-4292-a6b7-fba826d5c4cf 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.13.0-33-generic root=UUID=36c9b4f3-91a4-4292-a6b7-fba826d5c4cf ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x7f8454ecf480 <script_obj_deref_direct>: cmpl $0x1,(%rdi)
 PC (0x7f8454ecf480) ok
 source "$0x1" ok
 destination "(%rdi)" (0x500000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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_boot_progress () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
 () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
UpgradeStatus: Upgraded to bionic on 2018-02-08 (14 days ago)
UserGroups:

dmi.bios.date: 06/25/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: 965P-DS4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 965P-DS4
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
sokin (sirogil) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1580078, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.