plymouthd crashed with SIGABRT in __assert_fail_base()

Bug #1009238 reported by cecilpierce on 2012-06-05
262
This bug affects 39 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Undecided
Unassigned
plymouth (Ubuntu)
High
Unassigned

Bug Description

1. cecil@cecil-home:~$ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

Would not boot at all until I removed 'gfxmode $linux_gfx_mode' from menu

2. Dont know
3. Boot
4. Failed

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plymouth 0.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-4.10-generic 3.4.0
Uname: Linux 3.4.0-4-generic x86_64
ApportVersion: 2.1.1-0ubuntu2
Architecture: amd64
Date: Tue Jun 5 17:30:22 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120508)
Lsusb:
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Presario 061 EX318AA-ABA SR1920NX NA630
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-4-generic root=/dev/sda6 ro quiet splash
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-4-generic root=/dev/sda6 ro quiet splash
Signal: 6
SourcePackage: plymouth
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ply_event_loop_watch_fd () from /lib/libply.so.2
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/19/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.11
dmi.board.name: NAGAMI2L
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.11:bd09/19/2006:svnCompaqPresario061:pnEX318AA-ABASR1920NXNA630:pvr0nx1411RE101NAG2L00:rvnASUSTekComputerINC.:rnNAGAMI2L:rvr2.00:cvn:ct3:cvr1111:
dmi.product.name: EX318AA-ABA SR1920NX NA630
dmi.product.version: 0nx1411RE101NAG2L00
dmi.sys.vendor: Compaq Presario 061

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7f2336c36b86 "fd >= 0", file=0x7f2336c36aa0 "ply-event-loop.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0x7f2336c36b86 "fd >= 0", file=file@entry=0x7f2336c36aa0 "ply-event-loop.c", line=line@entry=742, function=function@entry=0x7f2336c37390 "ply_event_loop_watch_fd") at assert.c:103
 ply_event_loop_watch_fd (loop=0xfdb150, fd=-1, status=status@entry=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, status_met_handler=status_met_handler@entry=0x7f2334279a30 <on_key_event>, disconnected_handler=disconnected_handler@entry=0x7f233427a430 <on_input_source_disconnected>, user_data=user_data@entry=0xfe8870) at ply-event-loop.c:742
 open_input_source (backend=0xfe8850, input_source=0xfe8870) at ./plugin.c:700
 ply_renderer_open_input_source (renderer=0xfe2940, input_source=<optimized out>) at ply-renderer.c:377

Changed in plymouth (Ubuntu):
importance: Undecided → Medium
summary: - plymouthd crashed with SIGABRT in raise()
+ plymouthd crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in plymouth (Ubuntu):
status: New → Confirmed
visibility: private → public
Colin Watson (cjwatson) wrote :

Showing up a few times a day on errors.ubuntu.com, so bumping severity. It looks as though the frame-buffer plugin is trying to add a terminal watch when the terminal is closed.

Changed in plymouth (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged

I get this at every boot: plymouthd crashed with SIGABRT in raise()

tags: added: raring
tags: added: bugpattern-needed
tags: added: saucy
Brent Geers (bgeers) wrote :

Also occuring in 13.10

Christopher (soft-kristal) wrote :

System boots, but it takes several seconds before the mouse is usable.

vlotho (gdalmas) on 2014-02-08
tags: added: trusty
Changed in plymouth (Ubuntu):
status: Triaged → New
Steve Langasek (vorlon) on 2014-04-01
Changed in plymouth (Ubuntu):
status: New → Triaged
tags: added: utopic
miked (miked11) wrote :

root@ubuntu:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
Codename: vivid
root@ubuntu:~# uname -mrs
Linux 3.18.0-12-generic x86_64
root@ubuntu:~#
I $ sudo apt-get dist-upgrade my Wubi based Ubuntu installtion.

tags: added: vivid
Bruce Pieterse (octoquad) wrote :

Got this with vivid just now. A certain package when upgrading seemed to have triggered plymouth to start. tty1-6 were unresponsive and there was hard drive activity during this (packages finished installing), but a reboot was required in order to get back to desktop.

tags: added: wayland-session
removed: quantal raring saucy
tags: removed: utopic wayland-session
To post a comment you must log in.