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

Apport retracing service 1762663 at bugs.launchpad.net
Tue Apr 10 08:13:04 UTC 2018


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

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.

** Attachment removed: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/1762663/+attachment/5109021/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1580078

** 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/1762663

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Status in plymouth package in Ubuntu:
  New

Bug description:
  This bug happened during startup of Bionic Beaver beta 1 (all updates
  applied).

  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
  Date: Tue Apr 10 16:56:54 2018
  DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  InstallationDate: Installed on 2018-04-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=aecb2f1a-a2ec-4714-bc5f-6e1a8b22bb74 ro quiet splash
  ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
  ProcEnviron:
   LANG=ja_JP.UTF-8
   PATH=(custom, no user)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=aecb2f1a-a2ec-4714-bc5f-6e1a8b22bb74 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7f2017d08480 <script_obj_deref_direct>:	cmpl   $0x1,(%rdi)
   PC (0x7f2017d08480) ok
   source "$0x1" ok
   destination "(%rdi)" (0x00000020) 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_boot_progress () from /usr/lib/x86_64-linux-gnu/plymouth/script.so
   ?? () from /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: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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



More information about the foundations-bugs mailing list