[Bug 943814] Re: plymouthd crashed on a new insalation of Ubuntu 12.04 on Eee Pc 701

Thu Mar 1 07:03:42 UTC 2012

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

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.

** Attachment removed: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796390/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796392/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796398/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796400/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796401/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796402/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   https://bugs.launchpad.net/bugs/943814/+attachment/2796403/+files/ThreadStacktrace.txt

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

** Tags removed: need-i386-retrace

-- 
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/943814

Title:
  plymouthd crashed on a new insalation of Ubuntu 12.04 on Eee Pc 701

Status in “plymouth” package in Ubuntu:
  New

Bug description:
  After a system starts up, I get a dialog saying something has gone
  wrong, and that's pretty much it. Pressing the report button has
  presented me with a new dialog saying plymouth has crashed.

  The system was installed from a mini.iso, because the desktop iso
  can't seem to be on non-PAE CPU's.

  Description:	Ubuntu precise (development branch)
  Release:	12.04

  plymouth:
    Installed: 0.8.2-2ubuntu28
    Candidate: 0.8.2-2ubuntu28
    Version table:
   *** 0.8.2-2ubuntu28 0
          500 http://ro.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
          100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: plymouth 0.8.2-2ubuntu28
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  CurrentDmesg:
   [   22.428079] type=1400 audit(1330583919.982:22): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=897 comm="apparmor_parser"
   [   22.431690] type=1400 audit(1330583919.986:23): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=897 comm="apparmor_parser"
   [   31.632054] eth0: no IPv6 routers present
  Date: Wed Feb 29 22:16:43 2012
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  MachineType: ASUSTeK Computer INC. 701
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=20c34dcd-3752-460f-821f-f97afd694f3f ro quiet splash vt.handoff=7
  ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=20c34dcd-3752-460f-821f-f97afd694f3f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x1f55b7 <ply_event_loop_process_pending_events+455>:	test   %ecx,0x4(%esi)
   PC (0x001f55b7) 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: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 10/17/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 701
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x00000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd10/17/2007:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 701
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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