Bug 760228 - run Yum Update or software updater fails
Summary: run Yum Update or software updater fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sqlite
Version: 5.3
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 16:48 UTC by Les Piech
Modified: 2013-03-26 09:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-26 09:56:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
crash dump from updater failer (2.58 KB, application/octet-stream)
2011-12-05 16:48 UTC, Les Piech 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Les Piech 2011-12-05 16:48:21 UTC 
Created attachment 541012 [details]
crash dump from updater failer

Description of problem:
trying to run software updater on ES 5..
crashes after a few seconds after clicking apply updates, while resolving dependencies.

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


How reproducible:
Run Yum Update or run softare updater from gnome desktop

Steps to Reproduce:
1. run updater
2. apply update
3. fails after a few seconds
  
Actual results:
error dialog with prompt to save crash dump (attached)

Expected results:
successful update of OS

Additional info:
tried to uncheck sqllite / python updates and rerun updater but this did not work.
Comment 1 Jan Zeleny 2013-03-26 09:56:23 UTC 
Even though we acknowledge this issue, RHEL5 is at very late stage of its development cycle.

Taking that into consideration, I'm closing the bug as WONTFIX. The fix for this bug would take quite some time and it would have a potential to break things, which is not acceptable at this late stage of development cycle.

If you experience the same problem in later versions of RHEL, feel free to clone this bug for them.
Note You need to log in before you can comment on or make changes to this bug.