Bug 6812 – rp3 problems with account and modem listings

Bug 6812 - rp3 problems with account and modem listings

Summary:	rp3 problems with account and modem listings

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jonathan Blandford
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-07 22:14 EST by wizlord
Modified:	2013-04-02 00:13 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:	1999-12-01 10:43:48 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description wizlord 1999-11-07 22:14:45 EST

In tinkering around with rp3 I have created and removed both
accounts and modems.

When I removed an account and tried to recreate it with the
same name I got a message saying that the account already
existed, though it was not in the list.

Also, I now have four modems listed, when I remove the ones
that I don't need and then close and reopen rp3 the modems
reapear.

Comment 1 Michael K. Johnson 1999-11-08 11:23:59 EST

What version of rp3 do you have?  That is to say, have you downloaded
the 1.0.1 errata release?

Comment 2 wizlord 1999-11-09 11:59:59 EST

[dave@homesrv dave]$ rpm -q rp3
rp3-1.0.1-1
As listed on the errata site.

Comment 3 Michael K. Johnson 1999-11-19 16:19:59 EST

OK, I know what's happening now, thanks.

Jonathan: when rp3-config deletes an account, you need to remove
the wvdial section as well as the ifcfg file.

Comment 4 Jonathan Blandford 1999-12-01 10:43:59 EST

This is now fixed, and available in the latest release.  Thanks, for the bug.

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