plymouthd crashed with SIGSEGV in ply_renderer_get_buffer_for_head()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
uptodate 15.04.
when booted it presented that apport dialog when logged in. didnt look at the boot screen though
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.19.0-8-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Thu Mar 12 10:35:08 2015
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2013-09-28 (529 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: LENOVO 23247PG
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: 0x7f9e1cda5b89 <ply_renderer_
PC (0x7f9e1cda5b89) ok
source "0x10(%rdi)" (0x3ff000000000
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_renderer_
ply_pixel_
script_
?? () from /lib/x86_
ply_event_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_renderer_
UpgradeStatus: Upgraded to vivid on 2015-02-16 (23 days ago)
UserGroups:
dmi.bios.date: 04/30/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET94WW (2.54 )
dmi.board.
dmi.board.name: 23247PG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 23247PG
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 #1377378, 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.