plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #555402 reported by Mark Cariaga
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

apport still reports bug. The "could not write bytes: broken pipe" notice still appears at boot. Boot time looks too fast too even see splash...lol:)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: wl
Architecture: i386
CrashCounter: 1
CurrentDmesg:
 [ 6.137527] ppdev: user-space parallel port driver
 [ 15.920074] eth1: no IPv6 routers present
Date: Sun Apr 4 15:52:52 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Hewlett-Packard HP Mini
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=380aaa69-2260-4cfd-9ba7-135314eddc35 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0xb51fe1 <ply_event_loop_process_pending_events+513>: test %eax,0x4(%esi)
 PC (0x00b51fe1) 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_loop_process_pending_events ()
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UserGroups:

dmi.bios.date: 08/21/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 361A0 Ver. F.15
dmi.board.name: 361A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.12
dmi.chassis.asset.tag: CNU9142WGK
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr361A0Ver.F.15:bd08/21/2009:svnHewlett-Packard:pnHPMini:pvrF.10:rvnHewlett-Packard:rn361A:rvrKBCVersion02.12:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Mini
dmi.product.version: F.10
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Mark Cariaga (mzc) wrote :
visibility: private → public
Peter Watts (watto-one)
Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Waiting for the retracer.

Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.