The FDT manages to load properly but dies miserably after displaying the "FDT start page". It's possible to actually keep it alive if you manage to close the start page before it loads the content...

(FDT 5:18974): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed

• • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
  • (FDT 5:18974): DEBUG: NP_Initialize
  • (FDT 5:18974): DEBUG: NP_Initialize succeeded
    The program 'FDT 5' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadValue (integer parameter out of range for operation)'.
    (Details: serial 17688 error_code 2 request_code 53 minor_code 0)
    (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)