Bug 1069132 - yum seems to freeze at the end of update
Summary: yum seems to freeze at the end of update
Keywords:
Status: CLOSED DUPLICATE of bug 1063957
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-24 09:57 UTC by cornel panceac
Modified: 2014-02-24 15:57 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-24 15:57:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description cornel panceac 2014-02-24 09:57:00 UTC
Description of problem:
at the end of upgrading 1137 packages, after last "Cleanup" line, yum seems to freeze for more than 5 minutes. (still waiting for it to do something visible.)

Version-Release number of selected component (if applicable):
# rpm -q yum
yum-3.4.3-132.fc20.noarch


How reproducible:
upgrade a big number of packages (> 1000)

Steps to Reproduce:
1.
2.
3.

Actual results:
 long timeout without any visible info from yum.

Expected results:
yum should say something like "Updating some databases in prograss, please wait" or similar, and show a life sign.

Additional info:
in this particular upgrade, these two lines showed up:

chown: cannot access ‘/var/tmp/abrt/ccpp-2013-01-28-15:45:27-17802.new/*’: No such file or directory
chown: cannot access ‘/var/tmp/abrt/oops-2013-01-28-14:47:32-11707-1/*’: No such file or directory

After ~ 5 minutes, "Verifying" phase started.

Comment 1 Valentina Mukhamedzhanova 2014-02-24 15:57:55 UTC
The description of this problem is very similar to the description of bug 1063957.

The chown lines should probably be reported against abrt.

*** This bug has been marked as a duplicate of bug 1063957 ***


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