Bug 616610 - Reopen of Bug 590742 - corrupted double-linked list
Summary: Reopen of Bug 590742 - corrupted double-linked list
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-20 23:18 UTC by Hermann Huebler
Modified: 2011-06-29 13:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-29 13:12:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmsg output at at the time of the failure. (44.78 KB, application/octet-stream)
2010-07-20 23:18 UTC, Hermann Huebler
no flags Details

Description Hermann Huebler 2010-07-20 23:18:17 UTC
Created attachment 433279 [details]
dmsg output at at the time of the failure.

Description of problem:
When booting FC13 on my Lenovo T410 quite frequently I'm getting stuck with the following error message: 

*** glibc detected *** /bin/plymouthd: corrupted double-linked list: 0x0891ed48


Version-Release number of selected component (if applicable):
[root@hhuelinux ~]# rpm -qf `which plymouthd` 
plymouth-0.8.2-3.fc13.i686
glibc-2.12-3.i686
kernel-2.6.33.6-147.fc13.i686

The problem sounds pretty much like: 'https://bugzilla.redhat.com/show_bug.cgi?id=596791 - corrupted double-linked list at the end of boot' what was opened for RHEL 6.


How reproducible:
Starting up the system intermittently causes this problem however running a "reboot" gives a pretty good change to recreate. The error occurs before gnome gets started. At this point I can open a second session and work on the shell there. Collected the dmesg outout I'm attaching here.



Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 colin 2010-11-24 09:02:13 UTC
I have been having this problem for many months now, and reported it to Bugzilla back on 2010-07-20 in 'https://bugzilla.redhat.com/show_bug.cgi?id=590742'

Is there anything that I can do to help diagnose this disruptive long-running problem?

Comment 2 Vadim Lipovetsky 2010-12-13 10:41:03 UTC
I can reproduce this problem while booting Fedora 14 x86_64 (ASUS 1201n netbook).
Plymouth rpm is plymouth-0.8.4-0.20100823.6.fc14.x86_64.

Steps to reproduce.
1. Start the system.
2. Change continously between text and graphics modes.
3. The system get stuck with the following message: *** glibc detected *** /bin/plymouthd: corrupted double-linked list:....

Comment 3 Eddie Lania 2011-02-12 12:22:11 UTC
I am also seeing "file /bin/plymouthd seems to be deleted
" during startup, see my bug 662217 and I also am unable to solve it.
[root@hestia ~]# rpm -qa *plymouth*
plymouth-theme-solar-0.8.2-3.fc13.i686
plymouth-plugin-two-step-0.8.2-3.fc13.i686
plymouth-system-theme-0.8.2-3.fc13.i686
plymouth-plugin-label-0.8.2-3.fc13.i686
plymouth-scripts-0.8.2-3.fc13.i686
plymouth-theme-charge-0.8.2-3.fc13.i686
plymouth-utils-0.8.2-3.fc13.i686
plymouth-plugin-space-flares-0.8.2-3.fc13.i686
plymouth-core-libs-0.8.2-3.fc13.i686
plymouth-graphics-libs-0.8.2-3.fc13.i686
plymouth-0.8.2-3.fc13.i686
plymouth-gdm-hooks-0.8.2-3.fc13.i686

Comment 4 Bug Zapper 2011-06-01 13:19:27 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 5 Bug Zapper 2011-06-29 13:12:31 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.