GNOME Bugzilla – Bug 72822
gdict hangs when a word not in the dictionary was given for look up
Last modified: 2009-08-15 18:40:50 UTC
I have downloaded the latest code gdict(version 1.99.2) from the gnome -2.0 beta release. Reproducibility : Always Steps to reproduce : 1) Right click on the panel and select the option 'Add to the panel --> Utility --> dictionary'. gdict starts up successfully. 2) Specify the word that is not in the dictionary in the 'Word' text entry box and press the 'Enter' key. 3) Expected result should be it will display a message like it is not in the dictionary. But it is hanging.
Yeah, still duplicable in today's CVS. Still responsive, but no return.
Hmm, I don't get this. Does this still happen?
Well, lemme take that back. It hangs for me doing any lookup or search etc.
I can't test this in the panel (for reasons unrelated to gnome-dictionary), but in the application it works fine for me. Looking up a real word get a definition, and a non-word I get the "no matches found" message and the "spell checker" dialogue.
*** Bug 74148 has been marked as a duplicate of this bug. ***
Okay, I just tracked this down for me. The port had somehow been switched to 2 instead of 2628, which caused the infinited looping. I put in a fix that prevents the hanging so at least the user can check the server settings. So, Venkat or Louie, can you test this fix. See if your port number is incorrect as mine was. I would very much like to close this bug.
I'll test as soon as I get a build with the fix, Kevin; hopefully tomorrow morning.
Kevin: still appears to happen here. Is there a useful way to debug this?
Louie, it is still infinite looping? Is an error dialog being popped up? Can you verify that your port and sever settings are correct? Finally are you sure that you have the changes I made recently - they went in 3/10
Oh, weird... rebooted over lunch and now it appears to work. When I restarted the panel after upgrading this morning, I guess it just picked up the old dict somehow? Anyway, it works. Closing.
Closing , as the problem is not present in the latest build