Bug 104718

Summary: redhat-config-date should call "timeconfig" if ${DISPLAY} isn't set.
Product: [Retired] Red Hat Linux Reporter: Jesse Keating <jkeating>
Component: redhat-config-dateAssignee: Brent Fox <bfox>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: aleksey
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-19 19:05:29 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 Jesse Keating 2003-09-19 17:45:08 UTC
Description of problem:
redhat-config-date is an X11 application, but the package itself doesn't depend
on X11, mostly because it also includes "timeconfig" which is an ncurses app. 
This can confuse uses trying to use redhat-config-date w/out X11 installed,
especially since it seems that redhat-config-date doesn't have a "--help"
option.  To counter this, can't redhat-config-time call "timeconfig" if
${DISPLAY} isn't set?

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


How reproducible:
Always

Steps to Reproduce:
1. Install redhat-config-date, w/out X11 installed
2. Try to run redhat-config-date, get error about no X
3. Try to run redhat-config-date --help, still get error message.
    

Actual Results:  Error messages about no X

Expected Results:  Fall back to timeconfig.

Additional info:

Comment 1 Jesse Keating 2003-09-19 17:46:56 UTC
Another option would be to split "timeconfig" out of the package, and making
r-c-date depend on say pygtk2.

Comment 2 Brent Fox 2003-09-19 19:05:29 UTC
I've changed it to just call 'timeconfig' if the GUI can't be started up. 
Should be fixed in redhat-config-users-1.5.22-1.  Thanks for your report.

Comment 3 Brent Fox 2003-10-15 21:43:14 UTC
*** Bug 98516 has been marked as a duplicate of this bug. ***