Bug 580571 - [abrt] crash in plymouth-0.8.1-3.fc13: Process /sbin/plymouthd was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in plymouth-0.8.1-3.fc13: Process /sbin/plymouthd was killed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:50b6971eee1d453654a1cdc9c62...
: 580057 583366 585132 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 14:36 UTC by James Laska
Modified: 2013-09-02 06:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:29:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (9.43 KB, text/plain)
2010-04-08 14:36 UTC, James Laska
no flags Details

Description James Laska 2010-04-08 14:36:30 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /sbin/plymouthd --mode=shutdown
comment: I don't recall doing anything different, other than booting.  Perhaps pressing <Esc> multiple times triggered the failure?
component: plymouth
executable: /sbin/plymouthd
global_uuid: 50b6971eee1d453654a1cdc9c62b53bbb2d6de15
kernel: 2.6.33.1-19.fc13.x86_64
package: plymouth-0.8.1-3.fc13
rating: 4
reason: Process /sbin/plymouthd was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Install F-13-Beta, with updates-testing enabled
2. Boot F-13 with encrypted devices
3. Enter passphrase as graphical boot prompt
4. Press <Esc> during boot-up to show text-boot
5. Attempt to press <Esc> again to return to graphical-boot

Comment 1 James Laska 2010-04-08 14:36:32 UTC
Created attachment 405321 [details]
File: backtrace

Comment 2 Charlie Brej 2010-04-08 15:10:12 UTC
This is still the:
"plymouthd: ply-event-loop.c:707: ply_event_loop_watch_fd: Assertion"
problem of Bug 578633. I think there is a problem of the sequence in which plymouth and the kernel are installed so the initrd is crearted with the old plymouth.
Does rebuilding initrd fix it?

Comment 3 Karel Klíč 2010-05-25 09:49:16 UTC
*** Bug 580057 has been marked as a duplicate of this bug. ***

Comment 4 Karel Klíč 2010-05-25 09:49:20 UTC
*** Bug 583366 has been marked as a duplicate of this bug. ***

Comment 5 Karel Klíč 2010-11-09 15:45:48 UTC
*** Bug 585132 has been marked as a duplicate of this bug. ***

Comment 6 Bug Zapper 2011-06-02 15:33:24 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2011-06-27 15:29:30 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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


Note You need to log in before you can comment on or make changes to this bug.