plymouthd crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
after upgrading ubuntu 13.10...its unable to start..only 'ubuntu13.10' logo has came...then i have again reinstall ubuntu-desktop then my probem has solved ...but after login system says to report bug.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu7
ProcVersionSign
Uname: Linux 3.10.0-4-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Tue Jul 23 08:49:27 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
MachineType: SAMSUNG ELECTRONICS CO., LTD. R528/R728
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
__assert_fail () from /lib/i386-
ply_event_
TextPlymouth: /lib/plymouth/
Title: plymouthd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/18/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 03JL.M011.
dmi.board.name: R528/R728
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: R528/R728
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 #1009238, 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.