plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

Bug #904509 reported by Adrián
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

I do not know what happened! Just start Ubuntu.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Dec 14 23:53:30 2011
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTek Computer Inc. K8N
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic root=UUID=b8105523-53ef-407a-9b59-14b579025d38 ro quiet splash 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-4-generic root=UUID=b8105523-53ef-407a-9b59-14b579025d38 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fd1bc757504 <ply_event_loop_process_pending_events+468>: test %r12d,0x8(%r13)
 PC (0x7fd1bc757504) ok
 source "%r12d" ok
 destination "0x8(%r13)" (0x402f562ef399a674) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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: /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 2011-12-10 (4 days ago)
UserGroups:

dmi.bios.date: 02/16/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1011.005
dmi.board.name: 'K8N'
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1011.005:bd02/16/2006:svnASUSTekComputerInc.:pnK8N:pvrSystemVersion:rvnASUSTeKComputerINC.:rn'K8N':rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: K8N
dmi.product.version: System Version
dmi.sys.vendor: ASUSTek Computer Inc.

Revision history for this message
Adrián (jaksi) wrote :
visibility: private → public
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.

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.