plymoth crashed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Don't know sorry
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CurrentDmesg:
Date: Fri Mar 9 05:01:51 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120308)
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 001 Device 003: ID 03f0:2a12 Hewlett-Packard
Bus 002 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 002 Device 003: ID 0461:0010 Primax Electronics, Ltd
MachineType: Compaq-Presario AY030AA-ABA CQ5320F
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.15
dmi.board.name: Narra6
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 6.01
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: AY030AA-ABA CQ5320F
dmi.sys.vendor: Compaq-Presario
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.