plymouthd crashed with SIGSEGV in ply_renderer_get_buffer_for_head()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Sorry, cannot give appropriate details. System hangs up in a loop on screensaver (when requesting password) and cannot be unlocked. So a reboot was necessary.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Sat Feb 14 17:20:56 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-02-14 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150213)
MachineType: LENOVO 2847DFG
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f3a8fdd3b9b <ply_renderer_
PC (0x7f3a8fdd3b9b) ok
source "0x58(%rax)" (0x00000059) 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: 07/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6JET89WW (1.47 )
dmi.board.name: 2847DFG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2847DFG
dmi.product.
dmi.sys.vendor: LENOVO
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.