[Bug 940778] Re: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

James Hunt 940778 at bugs.launchpad.net
Fri Mar 30 16:36:18 UTC 2012


*** This bug is a duplicate of bug 553745 ***
    https://bugs.launchpad.net/bugs/553745

** This bug is no longer a duplicate of bug 849414
   plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
   plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/940778

Title:
  plymouthd crashed with SIGSEGV in
  ply_event_loop_process_pending_events()

Status in “plymouth” package in Ubuntu:
  New

Bug description:
  Crashed when i updated Ubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: plymouth 0.8.2-2ubuntu28
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  Date: Fri Feb 24 23:47:07 2012
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
  MachineType: Gigabyte Technology Co., Ltd. 965P-DS3
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic-pae root=UUID=a8503c42-9a08-41f7-9e01-8efc1790ed21 ro quiet splash vt.handoff=7
  ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic-pae root=UUID=a8503c42-9a08-41f7-9e01-8efc1790ed21 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0xb76c15b7 <ply_event_loop_process_pending_events+455>:	test   %ecx,0x4(%esi)
   PC (0xb76c15b7) 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/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 precise on 2012-02-17 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 06/25/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: 965P-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 965P-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/940778/+subscriptions




More information about the foundations-bugs mailing list