Bug 112231 – up2date stack trace: empty sequence

Bug 112231 - up2date stack trace: empty sequence

Summary:	up2date stack trace: empty sequence

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	9
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:	Fanny Augustin
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-12-16 09:38 EST by Gavin C. Flower
Modified:	2007-04-18 13:00 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-08-24 17:48:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
shows progress dialog (215.86 KB, image/png) 2003-12-16 09:42 EST, Gavin C. Flower	no flags	Details
stacktrace (2.64 KB, text/plain) 2003-12-16 09:43 EST, Gavin C. Flower	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gavin C. Flower 2003-12-16 09:38:45 EST

Description of problem:
Ran up2date and got stacktreace.  See attachment png for the progress
dialog being displayed, and up2date20031216.txt for the stacktrace.


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

How reproducible:
Don't know.  This is the first time it has happened, did happen when I
reran it, but meantime I had maually downloaded 

Steps to Reproduce:
1. N/A
2.
3.
  
Actual results:
stacktrace

Expected results:
N/A

Additional info:
N/A

Comment 1 Gavin C. Flower 2003-12-16 09:42:46 EST

Created attachment 96556 [details]
shows progress dialog

Comment 2 Gavin C. Flower 2003-12-16 09:43:20 EST

Created attachment 96557 [details]
stacktrace

Comment 3 Gavin C. Flower 2003-12-16 09:45:39 EST

Arghh!  The stacktrace happened just the once, it DIDN'T happen when I
reran it!

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