Description of problem: The transaction stops being processed until a key is pressed or until the mouse is moved. The Output View screen is normally displayed during the processing of the transaction. But as processing occurs the disk activity and progress bars stop until a key (the down-arrow) is pressed or until the mouse is moved. Once the key is pressed or the mouse is moved, processing resumes. Note also that when things are working the bottom portion (the border of the Output View text area, plus progress bars to the window bottom) jitter vertically. These symptoms happen only when the transaction is actually run, and do not appear during the transaction test. Version-Release number of selected component (if applicable): Yumex 2.0.2 under 2.6.23.1-10.fc7 installed with Gnome Desktop 2.18.3 How reproducible: This is readily reproduceable when a number of packages are being updated, but is less likely to occur when only 1-2 pkges are being updated. Steps to Reproduce: 1. Select a number of packages to be removed, updated or added 2. Click on "Process Queue" 3. Watch OutputView screen. Actual results: Processing halts until a key is pressed or the mouse is moved. No specific key is needed. Expected results: Processing should go on without halting and being triggered by keys or mouse. Additional info:
yumex-2.0.4-1.fc8 has been submitted as an update for Fedora 8
yumex-2.0.4-1.fc7 has been submitted as an update for Fedora 7
yumex-2.0.4-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update yumex'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-1940
yumex-2.0.4-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
yumex-2.0.4-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.