Bug 492054 - kernel pacakge link /lib/libparted-1.8.so.8 to /usr/lib/libparted-1.8.so.8 which cause kernel panic upon boot
kernel pacakge link /lib/libparted-1.8.so.8 to /usr/lib/libparted-1.8.so.8 w...
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2009-03-25 02:45 EDT by Knut J BJuland
Modified: 2009-12-18 04:06 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 04:06:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Knut J BJuland 2009-03-25 02:45:01 EDT
Description of problem:
Kernel package link lib/libparted-1.8.so.8  to /usr/lib/libparted-1.8.so.8, which cause the kernel to panic upon boot since initrd can not find /lib/libparted-1.8.so.8

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1.rpm -Uvh kernel
Actual results:
fail to boot

Expected results:
should not make link for  /lib/libparted-1.8.so.8  to /usr/lib/libparted-1.8.so.8

Additional info:
Comment 1 Chuck Ebbert 2009-03-25 23:39:10 EDT
Can you post the output of 'ls -l /lib/libparted*' and 'rpm -ql parted' commands?
Comment 2 Knut J BJuland 2009-03-28 09:29:49 EDT
ls -l /lib/libparted*
/lib/libparted-1.8.so.8  /lib/libparted-1.8.so.8.0.0

rpm -ql parted
Comment 3 Onno Hommes 2009-05-20 22:52:19 EDT
libparted is missing from the initrd. I have the same problem and ever since I cant run a yum update anymore because it creates the kernel panic with the missing libparted message. How can I make sure mkinitrd builds a proper initrd with libparted. I too have the latest libparted installed. Even though mkinitrd has a dependency on parted it must for some reason look in the wrong place when building the initrd.

This problem is quite annoying and started showing up in the time frame of the kernel 2.6.27...-159 release. How can mkinitrd be fixed to add libparted in the initrd?
Comment 4 Bug Zapper 2009-11-18 04:57:14 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 
Comment 5 Bug Zapper 2009-12-18 04:06:39 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.