Bug 89450 – sre.py:137:search:TypeError

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 89450 - sre.py:137:search:TypeError

Summary:	sre.py:137:search:TypeError

Status:	CLOSED DUPLICATE of bug 88147

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	redhat-config-network (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Harald Hoyer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-04-22 19:51 EDT by Darryl Caldwell
Modified:	2007-04-18 12:53 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:52:47 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Traceback from gui (1.41 KB, text/plain) 2003-04-22 19:52 EDT, Darryl Caldwell	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Darryl Caldwell 2003-04-22 19:51:24 EDT

Description of problem:

redhat-config-network-gui will not run

Version-Release number of selected component (if applicable):
redhat-config-network-1.2.0-2

How reproducible:
Every time

Steps to Reproduce:
1. Try to run 
2.
3./usr/sbin/redhat-config-network-gui
    
Actual results:

crashes with traceback

Expected results:

Run gui
Additional info:

Comment 1 Darryl Caldwell 2003-04-22 19:52:46 EDT

Created attachment 91237 [details]
Traceback from gui

Comment 2 Harald Hoyer 2003-04-23 05:48:36 EDT

please update to the version on:
http://people.redhat.com/harald/redhat-config-network

Comment 3 Harald Hoyer 2003-05-19 07:41:52 EDT


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

Comment 4 Red Hat Bugzilla 2006-02-21 13:52:47 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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