plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #935888 reported by linux-man
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

After login.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Feb 19 00:45:58 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: SAMSUNG ELECTRONICS CO., LTD. R540/R580/R780/SA41/E452/E852
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=007a4494-627c-4e78-9e43-36ca89df023a ro quiet splash acpi_sleep=nonvs acpi_backlight=vendor acpi_osi=Linux pcie_aspm=force radeon.audio=1 vt.handoff=7
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=007a4494-627c-4e78-9e43-36ca89df023a ro quiet splash acpi_sleep=nonvs acpi_backlight=vendor acpi_osi=Linux pcie_aspm=force radeon.audio=1 vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fb8bb8b7504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7fb8bb8b7504) 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 (main=0x403830, argc=3, ubp_av=0x7fff97a19318, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff97a19308) at libc-start.c:226
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
UpgradeStatus: Upgraded to precise on 2012-02-07 (11 days ago)
UserGroups:

dmi.bios.date: 09/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 03KP.M008.20100927.LDG
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: R540/R580/R780/SA41/E452/E852
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 03KP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03KP.M008.20100927.LDG:bd09/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR540/R580/R780/SA41/E452/E852:pvr03KP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR540/R580/R780/SA41/E452/E852:rvr03KP:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R540/R580/R780/SA41/E452/E852
dmi.product.version: 03KP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
linux-man (caldas-lopes) wrote :
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 this software 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
visibility: private → public
tags: removed: need-amd64-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.