Bug 874380

Summary: [abrt] plymouth-0.8.8-1.fc18: Process /usr/sbin/plymouthd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dartagnan <dartagnanarchuleta>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: fedora, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:74b3635a45d4c2b259726ecdb0509cd9c697b4f0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 12:54:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: .xsession-errors
none
File: limits
none
File: smolt_data
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Dartagnan 2012-11-08 03:34:13 UTC 
Version-Release number of selected component:
plymouth-0.8.8-1.fc18

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.17
backtrace_rating: 4
cmdline:        @usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session
crash_function: ply_boot_splash_update_progress
kernel:         3.6.3-3.fc18.i686

truncated backtrace:
:Thread no. 1 (4 frames)
: #0 ply_boot_splash_update_progress at ply-boot-splash.c:540
: #1 ply_event_loop_handle_timeouts at ply-event-loop.c:1234
: #2 ply_event_loop_process_pending_events at ply-event-loop.c:1303
: #3 ply_event_loop_run at ply-event-loop.c:1368
Comment 1 Dartagnan 2012-11-08 03:34:16 UTC 
Created attachment 640531 [details]
File: core_backtrace
Comment 2 Dartagnan 2012-11-08 03:34:18 UTC 
Created attachment 640532 [details]
File: environ
Comment 3 Dartagnan 2012-11-08 03:34:20 UTC 
Created attachment 640533 [details]
File: backtrace
Comment 4 Dartagnan 2012-11-08 03:34:22 UTC 
Created attachment 640534 [details]
File: .xsession-errors
Comment 5 Dartagnan 2012-11-08 03:34:23 UTC 
Created attachment 640535 [details]
File: limits
Comment 6 Dartagnan 2012-11-08 03:34:28 UTC 
Created attachment 640536 [details]
File: smolt_data
Comment 7 Dartagnan 2012-11-08 03:34:31 UTC 
Created attachment 640537 [details]
File: cgroup
Comment 8 Dartagnan 2012-11-08 03:34:34 UTC 
Created attachment 640538 [details]
File: executable
Comment 9 Dartagnan 2012-11-08 03:34:35 UTC 
Created attachment 640539 [details]
File: maps
Comment 10 Dartagnan 2012-11-08 03:34:44 UTC 
Created attachment 640540 [details]
File: dso_list
Comment 11 Dartagnan 2012-11-08 03:35:22 UTC 
Created attachment 640541 [details]
File: proc_pid_status
Comment 12 Dartagnan 2012-11-08 03:35:34 UTC 
Created attachment 640542 [details]
File: var_log_messages
Comment 13 Dartagnan 2012-11-08 03:35:35 UTC 
Created attachment 640543 [details]
File: open_fds
Comment 14 Fedora End Of Life 2013-12-21 09:18:54 UTC 
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.
Comment 15 Fedora End Of Life 2014-02-05 12:54:25 UTC 
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.