plymouthd crashed with SIGSEGV in ply_buffer_get_size()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
plymouthd crashed with SIGSEGV in ply_buffer_
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2
ProcVersionSign
Uname: Linux 2.6.32-15-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 18 17:25:49 2010
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VGA16 VGA
SegvAnalysis:
Segfault happened at: 0x7fb749249f30 <ply_buffer_
PC (0x7fb749249f30) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_buffer_
?? () from /lib/plymouth/
ply_boot_
?? ()
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_buffer_
UserGroups:
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #559763, 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.