plymouthd assert failure: plymouthd: ply-event-loop.c:742: ply_event_loop_watch_fd: Assertion `fd >= 0' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
error random ocure
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSign
Uname: Linux 3.18.0-13-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
AssertionMessage: plymouthd: ply-event-
BootLog:
Date: Wed Feb 18 12:46:45 2015
DefaultPlymouth: Error: command ['readlink', '/etc/alternati
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-12-10 (69 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141209)
MachineType: LENOVO 20023
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__assert_fail_base (fmt=0xb7632054 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__GI___assert_fail (assertion=
ply_event_
?? () from /lib/i386-
?? () from /lib/i386-
TextPlymouth: Error: command ['readlink', '/etc/alternati
Title: plymouthd assert failure: plymouthd: ply-event-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/21/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 18CN33WW(V2.06)
dmi.board.name: NITU1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 20023
dmi.product.
dmi.sys.vendor: LENOVO
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.