Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 103025

Summary:	'faxrm' and 'faxq -r' don't function
Product:	[Retired] Red Hat Linux	Reporter:	Jablonovsky Alexander <sasha>
Component:	mgetty	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 18:58:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jablonovsky Alexander 2003-08-25 16:56:17 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020823
Netscape/7.0

Description of problem:
/usr/bin/faxrm and /usr/bin/faxq don't function properly because
contain incorrect path for faxq-helper:
FAXQ_HELPER=/usr/local/lib/mgetty+sendfax/faxq-helper
instead of
FAXQ_HELPER=/usr/lib/mgetty+sendfax/faxq-helper


Version-Release number of selected component (if applicable):
mgetty-sendfax-1.1.30-2

How reproducible:
Always

Steps to Reproduce:
1. Try to send a fax to "bad" phone number to suspend it.
2. Try to resume this fax with 'faxq -r' or delete with 'faxrm' as normal user
(not root)

Actual Results:  Error message:
/usr/bin/faxrm: line 61: /usr/local/lib/mgetty+sendfax/faxq-helper: No such file
or directory


Expected Results:  The resumed or deleted fax

Additional info:

Comment 1 Jablonovsky Alexander 2003-08-25 17:33:39 UTC


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

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:13 UTC

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