plymouthd crashed with SIGSEGV in __libc_start_main()
This bug report was converted into a question: question #192549: plymouthd crashed with SIGSEGV in __libc_start_main().
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This is an automatic report, but I did have problems with recent versions of Ubuntu: 12.04 and 11.10 starting with kernel 3.0.0-16
I'm not sure if it is plymouth package or the kernel.
The system hangs on startup with a blank screen or blinking cursor without anything else being displayed, but not on every startup.
Kernel 3.0.0-15 worked fine.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-20-
ApportVersion: 2.0-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Mar 30 21:19:48 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/12/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.
dmi.board.name: K8SLI-eSATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K8SLI-eSATA2
dmi.product.
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 #938971, 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.