Comment 7 for bug 1608726

There appears to be some history behind this issue. I have submitted a patch to fix the error message but I am also double checking that this is not a variation of the original issue from before.