plymouthd crashed with SIGSEGV in ply_trigger_add_handler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed after login
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Wed Jul 10 18:35:40 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-07-10 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130710)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3Z/
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f89d0ef7a4c <ply_trigger_
PC (0x7f89d0ef7a4c) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_trigger_
?? ()
ply_event_
ply_event_loop_run () from /lib/x86_
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_trigger_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/25/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 05FU
dmi.board.
dmi.board.name: 300V3Z/
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: 300V3Z/
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 #864430, 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.