[Bug 1751084] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Apport retracing service 1751084 at bugs.launchpad.net
Thu Feb 22 15:42:46 UTC 2018


*** This bug is a duplicate of bug 927636 ***
    https://bugs.launchpad.net/bugs/927636

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 #927636, 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/1751084/+attachment/5060410/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060413/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060421/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060423/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060424/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060425/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   https://bugs.launchpad.net/bugs/1751084/+attachment/5060426/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 927636
   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/1751084

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Status in plymouth package in Ubuntu:
  New

Bug description:
  log in to desktop and got this crash

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: plymouth 0.9.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb 22 07:26:46 2018
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  InstallationDate: Installed on 2017-12-15 (69 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171214)
  MachineType: Gigabyte Technology Co., Ltd. AB350M-HD3
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=ad3dc06d-0c94-48ef-8e11-c5f450301a2c ro quiet splash
  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.13.0-32-generic.efi.signed root=UUID=ad3dc06d-0c94-48ef-8e11-c5f450301a2c ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7f572555f480 <script_obj_deref_direct>:	cmpl   $0x1,(%rdi)
   PC (0x7f572555f480) 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 () 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_update_status () 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: 04/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-HD3-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350M-HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1751084/+subscriptions



More information about the foundations-bugs mailing list