- 
    
Bug
 - 
    Resolution: Done
 - 
    
P1: Critical
 - 
    5.12.5, 5.13.1
 - 
    Windows 10 for Workstations x64 (10.0.18362.329)
VS2019, Compiler 19.22.27905 for x64 
The signal readyRead is never emitted, even if data is sent to the serial port from a connected device.
The member bytesAvailable returns 0 even if data has been sent to the serial port from a connected device.
The only way to have the signal readyRead emitted is receiving some data while waitForReadyRead is waiting.
In Qt 5.13.0 all worked as intended: readyRead was emitted as soon as the new data was sent to the serial port from a connected device.
The "Simple Terminal" example can be used to reproduce this bug. 
 I've tried the one from Qt 5.13.0 and works fine with a test device (38400 | 8n1 | no flow control).
 The one from Qt 5.13.1 simply outputs nothing.
- is duplicated by
 - 
                    
QTBUG-78113 QSerialPort not working
-         
     - Closed
 
 -         
 - 
                    
QTBUG-78149 QSerialPort::bytesWritten() never called on Windows 10
-         
     - Closed
 
 -         
 - 
                    
QTBUG-78475 QSerialPort readyRead signal isn`t emitted
-         
     - Closed
 
 -         
 - 
                    
QTBUG-78720 QSerialPort does not receive any data
-         
     - Closed
 
 -         
 
- resulted from
 - 
                    
QTBUG-74961 While reading and writing continously via a QSerialPort it is leaking memory
-         
 - Closed
 
 -         
 
| For Gerrit Dashboard: QTBUG-78086 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V | 
| 273106,4 | Revert "Emit _q_notify only if there's no notification pending" | 5.13 | qt/qtserialport | Status: MERGED | +2 | 0 | 
| 273883,4 | Revert "Emit _q_notify only if there's no notification pending" | 5.12 | qt/qtserialport | Status: MERGED | +2 | 0 |