plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #854742 reported by Anthony Harrington on 2011-09-20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

This started happening today after logging in. Nothing peculiar visually on boot up or login - i'm just warned that an error occurred with plymouthd.

I think this is related to the fact that i removed plymouth-label; plymouth-theme-ubuntu-logo and plymouth-theme-ubuntu-text yesterday evening, to see if it had any effect on bootup time - if it does, it's not all that noticeable. But it's one less thing to load at startup and i read that only the plymouth package itself is essential.

If it's not related to these above changes i made yesterday, it'll be something to do with the updates pushed yesterday i.e.

libplymouth2 (0.8.2-2ubuntu25) to 0.8.2-2ubuntu26
plymouth (0.8.2-2ubuntu25) to 0.8.2-2ubuntu26
plymouth-label (0.8.2-2ubuntu25) to 0.8.2-2ubuntu26
plymouth-theme-ubuntu-logo (0.8.2-2ubuntu25) to 0.8.2-2ubuntu26
plymouth-theme-ubuntu-text (0.8.2-2ubuntu25) to 0.8.2-2ubuntu26

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu26
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 20 15:06:01 2011
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
MachineType: ASUSTeK Computer Inc. K51AE
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=1445dc4d-5ac1-46d2-a795-7560f8f987ec ro quiet pcie_aspm=force
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=1445dc4d-5ac1-46d2-a795-7560f8f987ec ro quiet pcie_aspm=force
SegvAnalysis:
 Segfault happened at: 0x7f05e8f97504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7f05e8f97504) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x00000008) 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 () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
TextPlymouth: Error: command ['readlink', '/etc/alternatives/text.plymouth'] failed with exit code 1:
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K51AE
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd12/09/2009:svnASUSTeKComputerInc.:pnK51AE:pvr1.0:rvnASUSTeKComputerInc.:rnK51AE:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K51AE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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 #849414, 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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers