Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2
-
None
-
Linux/X11,
Windows
-
8
-
788c4980e6 (qt/qtconnectivity/dev) 9416e5473e (qt/qtconnectivity/6.3) 9416e5473e (qt/tqtc-qtconnectivity/6.3) 788c4980e6 (qt/tqtc-qtconnectivity/dev) 2eede8a018 (qt/tqtc-qtconnectivity/5.15) 1960fdc3a5 (qt/qtconnectivity/6.2)
-
Team One Foundation Sprint 51
Description
With the relevant bug fixes mentioned in QTBUG-99616 in place, the QtConnectivity "pingpong" example application yet doesn't work when ran between Linux (client) => Windows (server)
The issue seems different from others, a bluetooth socket protocol error, which needs investigation as to what happens.
Notably the "btchat" example application works in both directions.
Attachments
| For Gerrit Dashboard: QTBUG-100289 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 394508,3 | Avoid multiple client sockets in pingpong bluetooth example | dev | qt/qtconnectivity | Status: MERGED | +2 | 0 |
| 395610,2 | Avoid multiple client sockets in pingpong bluetooth example | 6.3 | qt/qtconnectivity | Status: MERGED | +2 | 0 |
| 395611,2 | Avoid multiple client sockets in pingpong bluetooth example | 6.2 | qt/qtconnectivity | Status: MERGED | +2 | 0 |
| 395616,2 | Avoid multiple client sockets in pingpong bluetooth example | tqtc/lts-5.15 | qt/tqtc-qtconnectivity | Status: MERGED | +2 | 0 |