Description of problem:
The virtual ffgtk-fax printer fails to listen on port localhost:9901. After printing a document to the ffgtk-fax printer another dialogue should (but fails to) pop up and allow entering the destination fax number. Using telnet or nmap confirms that port 9901 is closed, however, CUPS states that ffgtk-fax is attached to socket://localhost:9901. With the port closed clearly no data can ever reach the ffgtk-fax printer and CUPS simply queues its print jobs and reports it as busy.

Version-Release number of selected component (if applicable):
0.8.3

How reproducible:
Likely requires a supported multi function router (e.g. AVM FritzBox or similar) for properly configuring the ffgtk package. Either upgrade from previous version or install from scratch (rename ~/.config/ffgtk) and configure router access and fax functionality. Print data to ffgtk-fax device (e.g. from LO or gedit), wait indefinitely for dialogue requesting target fax number.

Steps to Reproduce:
1. Attach supported multi function router (e.g. AVM FritzBox)
2. Install and configure ffgtk package, start ffgtk
3. Attempt to fax from LO or gedit, check port 9901
  
Actual results:
Second print dialogue (the one for the fax destination number) never appears. Port 9901 is actually closed, although CUPS reports the ffgtk-fax printer as attached to Connection:	socket://localhost:9901

Expected results:
The second print dialogue (the one for the destination fax number) should appear a short while after committing a print job to ffgtk-fax. Consistent with CUPS config of ffgtk-fax printer Connection:	socket://localhost:9901 the port shoul actually be verifiably open (use nmap or telnet to check this). 

Additional info:
Affects both F16 and F17. In either version downgrading to previous ffgtk package solves the issue (working versions are F16 - 0.7.94 and I believe for F17 - 0.8.1). On a working setup telnet'ing to port 9901 and closing the telnet session triggers the popup for entering the destination fax number. Probably netcat could be used for this as well (have not tried it, though).