plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu Precise 12.04 32 Bit without (!) the following updates: accountsservice libaccountsservice0 linux-headers-
linux-
onboard python-apt python-apt-common update-manager update-manager-core
Happend directly after login - but happens after every login. Sometimes plymouth needs roughly 5 minutes to SIGSEV but always does.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-20-
NonfreeKernelMo
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Tue Mar 27 19:21:23 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120302)
MachineType: FUJITSU SIEMENS AMILO Xi 1526
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=
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGSEGV in ply_event_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 03/03/2007
dmi.bios.vendor: FUJITSU SIEMENS
dmi.bios.version: 1.22
dmi.board.name: AMILO Xi 1526
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnFUJITSUS
dmi.product.name: AMILO Xi 1526
dmi.product.
dmi.sys.vendor: FUJITSU SIEMENS
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.