If a machine does not have a working DNS able to resolve www.dict.org
then 'gdict' simply does not start and does not give any visible
indication why it is unhappy. Included documents are also of no help.
They indicate that running 'gdict -a' from a command line should
start an application. This immediately exits as confirmed by strace.
Fixed in the test tree