plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #640853 reported by Lutz on 2010-09-16
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

Description: Ubuntu maverick (development branch)
Release: 10.10
package is not to locate after crash - plymouthd
i386
Samsung N130 with rtl8192e
when I login at the router the system ask for the password and then for a keyring which is strange for my mind;
if I enter the wrong keyring then is unable to connect to the Internet via router.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic i686
Architecture: i386
Date: Wed Sep 15 21:36:11 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N130
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-21-generic root=UUID=61e5fffa-cc53-4ad7-bd95-80d088676c25 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0x7fe4af <ply_event_loop_process_pending_events+495>: test %ecx,0x4(%esi)
 PC (0x007fe4af) ok
 source "%ecx" 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/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: 01/08/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 06CM.M021.20100108.JIP
dmi.board.name: N130
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06CM.M021.20100108.JIP:bd01/08/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN130:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN130:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N130
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Lutz (lutz-goad) wrote :

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

Other bug subscribers