[Bug 1202128] Re: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: plymouth (Ubuntu)
       Status: New => Confirmed

-- 
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/1202128

Title:
  plymouthd crashed with SIGSEGV in ply_trigger_add_handler()

Status in Mir:
  New
Status in The Plymouth splash screen:
  New
Status in XMir:
  New
Status in “plymouth” package in Ubuntu:
  Confirmed

Bug description:
  Using MIR, Plymouth crashes at login.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: plymouth 0.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  Date: Wed Jul 17 09:53:45 2013
  DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  InstallationDate: Installed on 2013-07-16 (0 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130714)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  MarkForUpload: True
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=f20264e8-56dc-4aa1-89ae-5b015f036b8b ro quiet splash vt.handoff=7
  ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=f20264e8-56dc-4aa1-89ae-5b015f036b8b ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0xb76f3618 <ply_trigger_add_handler+56>:	mov    (%eax),%eax
   PC (0xb76f3618) ok
   source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   ply_trigger_add_handler () from /lib/i386-linux-gnu/libply.so.2
   ?? ()
   ?? ()
   ply_event_loop_process_pending_events () from /lib/i386-linux-gnu/libply.so.2
   ply_event_loop_run () from /lib/i386-linux-gnu/libply.so.2
  TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1202128/+subscriptions