15.04 Vivid GNOME startup plymouthd SIGSEGV in ply_renderer_get_buffer_for_head()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
$ lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
$ apt-cache policy plymouth
plymouth:
Installed: 0.9.0-0ubuntu9
Candidate: 0.9.0-0ubuntu9
Version table:
*** 0.9.0-0ubuntu9 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.19.0-11-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
Date: Mon Apr 6 11:27:11 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-18 (18 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f8c59451b89 <ply_renderer_
PC (0x7f8c59451b89) ok
source "0x10(%rdi)" (0x00000011) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL 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: 03/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAmerican
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.