plymouthd crashed with SIGSEGV in ply_renderer_get_buffer_for_head()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ubuntu 15.04 on macbook air 11 inch early 2014 model
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
Date: Tue Mar 3 01:20:17 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-02-22 (11 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150222)
MachineType: Apple Inc. MacBookAir6,1
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: 0x7f91a8734b89 <ply_renderer_
PC (0x7f91a8734b89) ok
source "0x10(%rdi)" (0x401400000000
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_renderer_
ply_pixel_
script_
?? () from /lib/x86_
?? () from /lib/x86_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_renderer_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/07/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.
dmi.board.
dmi.board.name: Mac-35C1E88140C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookAir6,1
dmi.product.
dmi.sys.vendor: Apple Inc.
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 #1378284, 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.