plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
New
|
Undecided
|
Unassigned | ||
Plymouth |
New
|
Undecided
|
Unassigned | ||
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Using MIR, Plymouth crashes at login.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSign
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/
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=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb76f3618 <ply_trigger_
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_
?? ()
?? ()
ply_event_
ply_event_loop_run () from /lib/i386-
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_trigger_
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:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
Status changed to 'Confirmed' because the bug affects multiple users.