plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #558645 reported by Michael on 2010-04-08
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

Symptoms:

1. plymouthd crash reports (and sometimes xorg crash reports) show up in the system taskbar.

2. Also, auto eth0 is disabled every boot.

The computer appears to work properly (once auto eth0 is manually activated).

Workaround:

Both problems disappear when the "splash" kernel parameter is removed from /etc/default/grub.

Software:

Ubuntu 10.04 beta 1, with 500+ updates including...

$ apt-cache policy plymouth
plymouth:
  Installed: 0.8.1-4ubuntu1
  Candidate: 0.8.1-4ubuntu1
  Version table:
 *** 0.8.1-4ubuntu1 0
        500 http://mirror.umoss.org/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

$ apt-cache policy xorg
xorg:
  Installed: 1:7.5+3ubuntu1
  Candidate: 1:7.5+3ubuntu1
  Version table:
 *** 1:7.5+3ubuntu1 0
        500 http://mirror.umoss.org/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Hardware:

Virtual Box 3.1.6 (guest: Lucid Lynx AMD64, host: Windows 7 x64)
Guest Additions 3.1.6 compiled and installed properly
Intel C2D E8400 (SMP, VT-X, PAE, and NX enabled)

BTW:

Using Software Center to remove plymouth also removes kernels and this of course kills grub. With one-click, no warning. Should this be filed as a separate bug under the Software Center package, or...?

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 x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 8 13:58:20 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=7c0d217d-8b89-4228-8beb-173e89f751f8 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 VGA16 VGA
SegvAnalysis:
 Segfault happened at: 0x7faf3e61c09c <ply_event_loop_process_pending_events+508>: test %r12d,0x8(%r13)
 PC (0x7faf3e61c09c) 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 ()
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/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: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Michael (null-pointer-us) wrote :
visibility: private → public

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-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers