Created attachment 682559 [details]
File: backtrace

Created attachment 682560 [details]
File: cgroup

Created attachment 682561 [details]
File: core_backtrace

Created attachment 682562 [details]
File: dso_list

Created attachment 682563 [details]
File: environ

Created attachment 682564 [details]
File: limits

Created attachment 682565 [details]
File: maps

Created attachment 682566 [details]
File: open_fds

Created attachment 682567 [details]
File: proc_pid_status

Created attachment 682568 [details]
File: smolt_data

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reopening due to duplicite: [bug 1051909] in F20.
Apparently the problem hasn't disappeared.

*** Bug 1051909 has been marked as a duplicate of this bug. ***

Just hit this issue too.  The central Fedora logo was kept at all white
mask during boot.  Only then ABRT showed there was a failure.

Full backtrace:

#0  __GI_raise
    (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
        resultvar = 0
        pid = 154
        selftid = 154

#1  __GI_abort
    at abort.c:89
        save_stage = 2
        act = {
        __sigaction_handler = {
        sa_handler = 0x7fffdcf45f51,
        sa_sigaction = 0x7fffdcf45f51
        },
        sa_mask = {
        __val = {246588870515, 266661325346, 793, 140736900385136,
            246587524339, 4, 140736900385040, 38654705666, 0, 24, 0,
            0, 0, 21474836480, 139790266605568,
        246588882312}
        },
        sa_flags = 373354200,
        sa_restorer = 0x3e1640ef70 <__PRETTY_FUNCTION__.7337>
        }
        sigs = {
        __val = {32, 0 <repeats 15 times>}
        }

#2  __assert_fail_base
        assertion=assertion@entry=0x3e1640eed8 "splash->idle_trigger
            == ((void *)0)", file=file@entry=0x3e1640ea22 "ply-boot-
            splash.c", line=line@entry=793,
        function=function@entry=0x3e1640ef70
            <__PRETTY_FUNCTION__.7337> "ply_boot_splash_become_idle")
            at assert.c:92
        str = 0xe54fb0 ""
        total = 4096

#3  __GI___assert_fail
        file=file@entry=0x3e1640ea22 "ply-boot-splash.c",
            line=line@entry=793, function=function@entry=0x3e1640ef70
            <__PRETTY_FUNCTION__.7337> "ply_boot_splash_become_idle")
        at assert.c:101
        No locals.

#4  ply_boot_splash_become_idle
    (splash=0xe53030, idle_handler=<optimized out>, user_data=<optimized
    out>)
    at ply-boot-splash.c:793
        __PRETTY_FUNCTION__ = "ply_boot_splash_become_idle"
        __func__ = "ply_boot_splash_become_idle"

#6  ply_event_loop_handle_met_status_for_source
    (status=PLY_EVENT_LOOP_FD_STATUS_HAS_DATA, source=0xe50480,
    loop=0xe41150)
    at ply-event-loop.c:1060
        next_node = 0x0
        destination = 0xe54af0
        node = <optimized out>

#5  ply_boot_connection_on_request
    (connection=0xe55d60)
    at ply-boot-server.c:504
        deactivate_trigger = 0xe55ea0
        server = 0xe43cf0
        command = 0x1001560 "D"
        argument = 0x0
        __PRETTY_FUNCTION__ = "ply_boot_connection_on_request"
        __func__ = "ply_boot_connection_on_request"

#7  ply_event_loop_process_pending_events
    (loop=loop@entry=0xe41150)
    at ply-event-loop.c:1336
        source = 0xe50480
        status = PLY_EVENT_LOOP_FD_STATUS_HAS_DATA
        is_disconnected = <optimized out>
        number_of_received_events = <optimized out>
        i = <optimized out>
        events = {{
        events = 1,
        data = {
        ptr = 0xe50480,
        fd = 15008896,
        u32 = 15008896,
        u64 = 15008896
        }
        }, {
        events = 4294967295,
        data = {
        ptr = 0xffffffffffffffff,
        fd = -1,
        u32 = 4294967295,
        u64 = 18446744073709551615
        }
        } <repeats 63 times>}
        __PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events"

#8  ply_event_loop_run
    (loop=0xe41150)
    at ply-event-loop.c:1368
        No locals.

#9  main
    (argc=<optimized out>, argv=<optimized out>)
    at main.c:2563
        state = {
        loop = 0xe41150,
        boot_server = 0xe43cf0,
        pixel_displays = 0xe43ac0,
        text_displays = 0xe43ae0,
        keyboard = 0xe490d0,
        boot_splash = 0xe53030,
        session = 0xe43c60,
        boot_buffer = 0xe43e70,
        progress = 0xe467c0,
        keystroke_triggers = 0xe42a50,
        entry_triggers = 0xe42a70,
        entry_buffer = 0xe42a90,
        messages = 0xe43b00,
        command_parser = 0xe41010,
        mode = PLY_MODE_BOOT,
        renderer = 0xe46dc0,
        ---Type <return> to continue, or q <return> to quit---
        local_console_terminal = 0xe46c50,
        deactivate_trigger = 0xe55ea0,
        quit_trigger = 0xe55bd0,
        kernel_command_line =
            "BOOT_IMAGE=/vmlinuz-3.13.10-200.fc20.x86_64
            root=UUID=c62dc90f-1398-4cfb-bdf5-3750961aa339 ro rd.md=0
            rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us
            video.use_native_backlight=1 rhgb quiet LANG=en_US.U"...,
        kernel_command_line_is_set = 1,
        no_boot_log = 0,
        showing_details = 0,
        system_initialized = 1,
        is_redirected = 1,
        is_attached = 1,
        should_be_attached = 1,
        should_retain_splash = 0,
        is_inactive = 0,
        is_shown = 1,
        should_force_details = 0,
        kernel_console_tty = 0x0,
        override_splash_path = 0x0,
        system_default_splash_path = 0xe4bb80
            "/usr/share/plymouth/themes/charge/charge.plymouth",
        distribution_default_splash_path = 0xe501f0
            "/usr/share/plymouth/themes/spinner/spinner.plymouth",
        default_tty = 0x40ee97 "/dev/tty1",
        number_of_errors = 0
        }
        exit_code = <optimized out>
        should_help = false
        no_daemon = false
        debug = false
        attach_to_session = true
        daemon_handle = 0xe41960
        mode_string = 0xe41960 "\360", <incomplete sequence \345>
        kernel_command_line = 0x0
        tty = 0x0
        __func__ = "main"


There seems to be something wrong with the assert at frame 4:

788 void
789 ply_boot_splash_become_idle (ply_boot_splash_t *splash,
790                              ply_boot_splash_on_idle_handler_t idle_handler,
791                              void *user_data)
792 {
793   assert (splash->idle_trigger == NULL);
794
795   if (splash->progress != NULL)
796     {
797       ply_progress_set_percentage (splash->progress, 1.0);

... with plymouth-0.8.9-3.2013.08.14.fc20.x86_64

*** Bug 1021154 has been marked as a duplicate of this bug. ***

I get a crash report about plymouth from time to time (after every 5th boot or so). Therefore I guess some sporadic timeout issue maybe.

plymouth-0.8.9-3.2013.08.14.fc20.x86_64
kernel-3.16.4-200.fc20.x86_64

Another user experienced a similar problem:

right after logged into xfce session

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session
crash_function: ply_boot_splash_become_idle
executable:     /usr/sbin/plymouthd
kernel:         3.16.6-203.fc20.x86_64
package:        plymouth-0.8.9-3.2013.08.14.fc20
reason:         plymouthd killed by SIGABRT
type:           CCpp
uid:            0

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Never seen this with Fedora 21. Not reproducible any more for me.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.