Bug 169022

Summary: System freezes at every rpm install or rpm -verify!
Product: [Fedora] Fedora Reporter: Petr Danecek <danecek>
Component: rpmAssignee: Paul Nasrat <pnasrat>
Status: CLOSED WONTFIX QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-25 21:30:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Petr Danecek 2005-09-22 09:22:42 UTC
Hello,
My Fedora 2 (with all updates applied) freezes totally and must be restarted by
pushing the power-off button, every time when doing a RPM installation and also
when running 'rpm -verify'.

The behaviour is rather strange: It freezes only when the root privileges were
obtained by issuing 'su' command; when logged in as root, rpm runs ok.

When comparing finished and unfinished outputs of rpm verify, it seems that the
system crashes repeatedly at the same place.

I'd be very grateful for tips how to debug and solve this problem,
Petr Danecek

Comment 1 Petr Danecek 2005-09-22 10:02:20 UTC
----------

Additional information: I have identified the offending package. To freeze my
system, I can login as a normal user and then type:
   su 
   rpm -q xorg-x11-libs --verify

I only wonder, how an userspace program can freeze the machine totally, so that
even pinging on it from some other machine does not work???


Comment 2 Jeff Johnson 2005-09-29 19:46:24 UTC
Check for I/O errors in your logs for one of the blocks in the files contained within the xorg-x11-libs 
package.

Comment 3 Petr Danecek 2005-10-06 07:35:56 UTC
I haven't found any such error. In fact, all of the xorg-x11-libs files can be
copied to another place with no problem.
:-(

Comment 4 Paul Nasrat 2005-10-25 21:30:40 UTC
Fedora Core 2 is no longer supported, please test your issue against the latest
release Fedora Core 4 and reopen if still occuring.