plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #752215 reported by Daniel Molka on 2011-04-06
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

Crashes after login

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu21
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
Date: Mon Apr 4 09:18:59 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Latitude D830
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic-pae root=UUID=b9c670f4-60b4-41ac-b829-9f81bdd2609e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb77d55e9 <ply_event_loop_process_pending_events+505>: test %eax,0x4(%esi)
 PC (0xb77d55e9) 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 () from /lib/libply.so.2
 ply_event_loop_run () from /lib/libply.so.2
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: Upgraded to natty on 2011-04-01 (4 days ago)
UserGroups: root
dmi.bios.date: 12/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0HN341
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/11/2008:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D830
dmi.sys.vendor: Dell Inc.

Daniel Molka (dmolka) wrote :

It's hard to tell if this bug affects me but it seems to.
On Lucid, I get a different offset (line number):
Segfault happened at: 0x7f08b9e1109c <ply_event_loop_process_pending_events+508>: test %r12d,0x8(%r13)
 PC (0x7f08b9e1109c) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x00000008) not located in a known VMA region (needed writable region)!

 libplymouth2 0.8.2-2ubuntu2.2
 plymouth 0.8.2-2ubuntu2.2

I may also just be hitting the bug that apport takes me to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553745

I don't want to ignore this crash as it happens quite regularly after boot now wheras it didn't before.

Thanks,

     Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html

Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 553745, so it 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.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers