plymouthd assert failure: plymouthd: ply-event-loop.c:707: ply_event_loop_watch_fd: Assertion `fd >= 0' failed.

Bug #556450 reported by teza
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: plymouth

Still buggy even after update.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4ubuntu1 [modified: bin/plymouth sbin/plymouthd]
ProcVersionSignature: Ubuntu 2.6.31-10.153-rt
Uname: Linux 2.6.31-10-rt i686
NonfreeKernelModules: nvidia
Architecture: i386
AssertionMessage: plymouthd: ply-event-loop.c:707: ply_event_loop_watch_fd: Assertion `fd >= 0' failed.
CrashCounter: 1
Date: Tue Apr 6 14:25:15 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu-Studio 10.04 "Lucid Lynx" - Beta i386 (20100317)
Lsusb:
 Bus 002 Device 002: ID 0763:2010 Midiman M-Audio Fast Track
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 005: ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
 Bus 001 Device 002: ID 059b:0370 Iomega Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-rt root=UUID=c60f2c47-036a-4385-824e-b3b925124fa4 ro splash quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB:

Signal: 6
SourcePackage: plymouth
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 ply_event_loop_watch_fd (loop=0x89b50a8, fd=-1,
TextPlymouth: Error: command ['readlink', '/etc/alternatives/text.plymouth'] failed with exit code 1:
Title: plymouthd assert failure: plymouthd: ply-event-loop.c:707: ply_event_loop_watch_fd: Assertion `fd >= 0' failed.
UserGroups:

dmi.bios.date: 05/01/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N-MX SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0201:bd05/01/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSE:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
teza (tsaliou75) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Daniel Hahler (blueyed)
visibility: private → public
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.