plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
Description: Ubuntu lucid (development branch)
Release: 10.04
plymouth:
Installato: 0.8.1-4
Candidato: 0.8.1-4
Tabella versione:
*** 0.8.1-4 0
500 http://
100 /var/lib/
At restart after daily regular dist-upgrade.
Thank you
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Fri Apr 2 22:21:39 2010
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
MachineType: ACER Veriton M460
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
Segfault happened at: 0xef8fe1 <ply_event_
PC (0x00ef8fe1) ok
source "%eax" ok
destination "0x4(%esi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
ply_event_
ply_event_loop_run () from /lib/libply.so.2
?? ()
__libc_start_main () from /lib/tls/
?? ()
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_event_
UserGroups:
dmi.bios.date: 01/16/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-B1
dmi.board.
dmi.board.name: EG31M
dmi.board.vendor: ACER
dmi.board.version: R01-B1
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: Veriton M460
dmi.product.
dmi.sys.vendor: ACER
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 #553745, 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.