Description of problem: Right clicked on the first NTP server pool 0 host name Version-Release number of selected component: anaconda-18.29.2 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.6-3.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.29.2 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1209, in __new__ : if len(path) == 0: : File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 798, in get_iter : path = TreePath(path) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/datetime_spoke.py", line 251, in on_server_edited : itr = self._serversStore.get_iter(path) :TypeError: object of type 'NoneType' has no len()
Created attachment 652423 [details] File: anaconda-tb
Created attachment 652424 [details] File: product
Created attachment 652425 [details] File: type
Created attachment 652426 [details] File: ifcfg.log
Created attachment 652427 [details] File: storage.log
Created attachment 652428 [details] File: version
Created attachment 652429 [details] File: environ
Created attachment 652430 [details] File: executable
Created attachment 652431 [details] File: anaconda.log
Created attachment 652432 [details] File: syslog
Created attachment 652433 [details] File: hashmarkername
Created attachment 652434 [details] File: packaging.log
Created attachment 652435 [details] File: cmdline_file
Created attachment 652436 [details] File: release
Created attachment 652437 [details] File: program.log
(In reply to comment #0) > Description of problem: > Right clicked on the first NTP server pool 0 host name You mean you've just opened the NTP servers configuration dialog and right-clicked on the "0.fedora.pool.ntp.org"? Because I cannot reproduce the traceback like this way.
Patch for testing path validity was sent to anaconda-patches.
(In reply to comment #16) > (In reply to comment #0) > > Description of problem: > > Right clicked on the first NTP server pool 0 host name > You mean you've just opened the NTP servers configuration dialog and > right-clicked on the "0.fedora.pool.ntp.org"? Because I cannot reproduce the > traceback like this way. Yes, in the dialog for the list of NTP servers, I clicked on the 0.fedora.pool.ntp.org to edit it. What must have happened is I started editing the host name as blanked and it was then when I hit the right mouse button and the crash occured. It seems the event that occured was a validation attempt on the string in that entry. Since I right clicked when it was empty, it was attempting to validate an empty field.
(In reply to comment #18) > (In reply to comment #16) > > (In reply to comment #0) > > > Description of problem: > > > Right clicked on the first NTP server pool 0 host name > > You mean you've just opened the NTP servers configuration dialog and > > right-clicked on the "0.fedora.pool.ntp.org"? Because I cannot reproduce the > > traceback like this way. > > Yes, in the dialog for the list of NTP servers, I clicked on the > 0.fedora.pool.ntp.org to edit it. What must have happened is I started > editing the host name as blanked and it was then when I hit the right mouse > button and the crash occured. It seems the event that occured was a > validation attempt on the string in that entry. Since I right clicked when > it was empty, it was attempting to validate an empty field. Right-click to the text entry shows me a context menu, but if one right-clicks on some other item, it stops editting and that might cause the traceback. However, the proposed (and now also pushed) patch seems to be fixing this issue. The other problem is that even an empty "hostname" is accepted, but that's another story. See bug #865869 for more information about that.
Going over old anaconda bugs. I fiddled around in the NTP screen for a while and couldn't produce anything like this, so it looks like the fix worked. Let's close this out.