As Frank suggested, you can always get the error diagnostics with errorString(). See our examples for details.
I cannot reproduce the problem, but based on your comment, your serial port was already used by another process, so this means it is not a QtSerialPort issue. Any other software would have had an issue with this, e.g. a new minicom session.
Glad that it works now. :)