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) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
toto@pc5:~$ lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
toto@pc5:~$ apt-cache policy plymouth
plymouth:
Installé : 0.8.8-0ubuntu8
Candidat : 0.8.8-0ubuntu8
Table de version :
*** 0.8.8-0ubuntu8 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: plymouth 0.8.8-0ubuntu8
ProcVersionSign
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12-0ubuntu2
Architecture: amd64
AssertionMessage: plymouthd: ply-event-
CrashCounter: 1
Date: Mon Aug 5 16:30:26 2013
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
ExecutableTimes
InstallationDate: Installed on 2013-05-24 (73 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130421)
MachineType: Gigabyte Technology Co., Ltd. EP31-DS3L
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcCwd: /
ProcEnviron:
TERM=linux
PATH=(custom, no user)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: plymouth
StacktraceTop:
__assert_fail_base (fmt=0x7f84367193b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__GI___assert_fail (assertion=
ply_event_
?? () from /lib/x86_
ply_event_
TextPlymouth: /lib/plymouth/
Title: plymouthd assert failure: plymouthd: ply-event-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/22/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FDc
dmi.board.name: EP31-DS3L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: EP31-DS3L
dmi.sys.vendor: Gigabyte Technology 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.