Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 159846 - up2date hangs with: warning: waiting for transaction lock
Summary: up2date hangs with: warning: waiting for transaction lock
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date
Version: 4.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-08 16:45 UTC by Jim Waldram
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-08 18:16:23 UTC


Attachments (Terms of Use)

Description Jim Waldram 2005-06-08 16:45:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-1.4.1

Description of problem:
up2date gui runs, fetches headers for channel. when packages are selected the dependencies check stalls/hangs with warning: waiting for transaction lock

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

How reproducible:
Always

Steps to Reproduce:
1.run up2date
2.select a package to update
3.
  

Actual Results:  launching Konsole shows the error message warning: waiting for transaction lock and the up2date session hangs.  You must <ctl>c or kill the process to get the Konsole prompt back.

Expected Results:  up2date should continue with package download and install.

Additional info:

Comment 1 Jim Waldram 2005-06-08 18:16:23 UTC
Problem solved.  A hpwebjet startup script was hung (on every reboot) trying to
install print filters.  killing the spawned rpm process and removing
/var/lock/rpm/transaction enabled running up2date.  The actual hang was with
rpm, not up2date.


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