Bug 6611 – GNORPM crashes when changing filter in the install window

Bug 6611 - GNORPM crashes when changing filter in the install window

Summary:	GNORPM crashes when changing filter in the install window

Status:	CLOSED DUPLICATE of bug 6657

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gnorpm (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	6612 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-01 16:01 EST by fzaidi
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-05 14:38:11 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description fzaidi 1999-11-01 16:01:22 EST

I have just recently purchased and registered Red Hat
Linux 6.1 Deluxe edition. Every time I go to the Install
window in GNORPM and try to change the filter it crashes
with a segmentation fault. The default filter is "All but
Installed Packages".
Whenever I try to scroll down and pick any of the other
three filters, RPM crashes. I am thus unable to install or
find out any info about the packages by using RPM.

Note: I am a new to the world of Linux.

Comment 1 culliton 1999-11-01 16:16:59 EST

This happens when there are no packages for it to filter, see Bugzilla
#6612, which is was apparently entering at the same time.  Sigh... Yet
another duplicate...

Comment 2 culliton 1999-11-12 02:02:59 EST

*** Bug 6612 has been marked as a duplicate of this bug. ***

Comment 3 Bill Nottingham 2000-02-05 14:38:59 EST

*** This bug has been marked as a duplicate of 6657 ***

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