Bug 241762 - up2date and software updater crash on centos 5
Summary: up2date and software updater crash on centos 5
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date   
(Show other bugs)
Version: 4.5
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Ken Reilly
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-30 13:34 UTC by Tia Haenni
Modified: 2012-06-20 13:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 13:25:19 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
crash dump of software updater/up2date (2.84 KB, text/plain)
2007-05-30 13:38 UTC, Tia Haenni
no flags Details

Description Tia Haenni 2007-05-30 13:34:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070309 Firefox/

Description of problem:
up2date suddenly crashes, has worked within the last few days, crash dump log attached

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

How reproducible:

Steps to Reproduce:
1.run up2date in terminal or software updater from applications>system tools menu
2.exception occurs while retrieving package data on startup

Actual Results:

Expected Results:

Additional info:

Comment 1 Tia Haenni 2007-05-30 13:38:52 UTC
Created attachment 155682 [details]
crash dump of software updater/up2date

Comment 3 Jiri Pallich 2012-06-20 13:25:19 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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