Message said - plymouthd crashed for unknown reason.

[Don Daniels]

Binary package hint: plymouth

Message said Plymouthd crashed for unknown reason. Also I had lost advanced video options (eye candy like splash buttons and giggly windows) and was only able to run basic video functions. Lost the ability to move windows around the desktop (Click and drag) and the quit, minimize and maximize buttons on the top left corner of windows had disappeared. Was still able to quit Ubuntu with the button at top right of screen IF no other window was covering it up, otherwise had to use Ctrl-Alt-Del to get the window to shut down. Just installed todays updates, and will see if that fixes everything.

Can not get to the exact version number as Firefox is covering the toolbar for system information, but it was 10.04 updated as of sometime yesterday, Monday, April 12th.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Tue Apr 13 11:11:43 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TOSHIBA Satellite M45
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=604628ec-f2cb-4507-8ea2-babe1fbf51a3 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 inteldrmfb
SegvAnalysis:
 Segfault happened at: 0xa8c107 <ply_buffer_get_size+7>: mov 0x4(%eax),%eax
 PC (0x00a8c107) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_buffer_get_size () from /lib/libply.so.2
 ply_boot_splash_show () from /lib/libply-splash-core.so.2
 ?? ()
 ?? ()
 ?? ()
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_buffer_get_size()
UserGroups:

dmi.bios.date: 02/07/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.20
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 8
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.20:bd02/07/2006:svnTOSHIBA:pnSatelliteM45:pvrPSM42U-017006:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct8:cvrVersion1.0:
dmi.product.name: Satellite M45
dmi.product.version: PSM42U-017006
dmi.sys.vendor: TOSHIBA

[Don Daniels (dondaniels)]

Also, at boot up and shut down would get a series of 8 or 10 Broken Pipe messages flowing by.

[Don Daniels (dondaniels)]

Just installed current updates and can now move SOME windows around the desktop, but Firefox still will not move or resize, and it covers up all of my applications and system options when open. Also, while typing in this window I can not enter another window to enter my master password for Firefox. Something is still messed up as I can not move between windows when more than one are open. Can't even scroll this page down to enter this message until I closed the Master Password window.

[Apport retracing service (apport)]

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 #555247, 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.