plymouthd crashed with SIGSEGV in ply_pixel_display_draw_area()
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-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 7 16:23:44 2015
DefaultPlymouth: /lib/plymouth/
Disassembly: => 0x21: Cannot access memory at address 0x21
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2015-03-31 (7 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Dell Inc. XPS 8500
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: 0x21: Cannot access memory at address 0x21
PC (0x00000021) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
?? ()
ply_pixel_
script_
?? () from /lib/x86_
?? () from /lib/x86_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_pixel_
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0NW73C
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS 8500
dmi.sys.vendor: Dell 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.