printerdrake often runs lpstat to check the config : If there is a problem with the network config or the cups config, lpstat never returns, and printerdrake never finishes to tell me to wait. So I must kill it, and I cannot configure any printer with it.
I've got the problem with the following procedure : - fresh 8.2 install with a printer using PDQ - configure the network with dhcp (cable modem) - change the printer manager to CUPS ...hangs... : lpstat doesnt return. I have run into this problem just by using mdk config tools, without manually editing any config file. I had to disable the dhcp, configure a static IP, configure the printer, reconfigure the dhcp. I think a GUI for a config tool should never be blocked by a single command launched in background, and should not suppose it will return in short delays.
