From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
Just installed Phoebe II.
nis client (with incorrect NIS domain name, by accident, but might be related).
when firstboot ran, immediately I get an error box complaining
"An error has occured in the Date and Time module"
The first callback is:
/usr/share/firstbootWindow.py line 153
TypeError: gethostbyaddr() arguement must be String not None
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install new system.
2. boot first time
Actual Results: No date/time setup in first boot
Expected Results: no error box.
p[ossibly relavant, possibly not. the nis domainname was wrong.
Do you mean NIS or NTP?
Also, did firstboot crash immediately or did you enter a server into the NTP
entry and then click Forward?
actually, i DID mean "NIS" (not NTP)
firstboot (as a whole) didn't seem to crash. but the date/time thingie of
firstboot did crash. I never saw the date/time screen (I am assuming that that
is where you enter the "NTP entry", yes ?
Ah, ok. I don't think that NIS has anything to do with this problem then. Did
the traceback you saw look anything like:
File "/usr/share/redhat-config-date/redhat-config-date.py", line 48, in ?
File "/usr/share/redhat-config-date/mainWindow.py", line 180, in __init__
self.datePage = date_gui.datePage(self.dateBackend)
File "/usr/share/redhat-config-date/date_gui.py", line 171, in __init__
ntpServer = socket.gethostbyaddr(ntpServerIP)
TypeError: gethostbyaddr() argument 1 must be string, not None
It probably appeared in a window just as firstboot was starting up, right? If
so, then this is a duplicate of bug #82061.
yes, looks like a dup of 82061. by the way, I _did_ do a bugzilla search (on
firstboot as I recall) before entering the bug, and nothing showed up.
That may be because the date/time screen in firstboot is actually the code from
redhat-config-date, so most of the bugs may have been filed against that
component. This would explain why your Bugzilla query turned up nothing.
Resolving as a duplicate. Thanks for your report.
*** This bug has been marked as a duplicate of 82061 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.