Opened 6 years ago
Last modified 6 years ago
#18300 new defect
VNC connect callback problem
| Reported by: | Karlo Dipetrio | Owned by: | |
|---|---|---|---|
| Component: | RDP | Version: | VirtualBox 6.0.0 |
| Keywords: | vnc | Cc: | |
| Guest type: | other | Host type: | Linux |
Description
Hello.
This is code fragment of new vnc connect. VirtualBox-6.0.0\src\VBox\ExtPacks\VNC\VBoxVNC.cpp:
enum rfbNewClientAction VNCServerImpl::rfbNewClientEvent(rfbClientPtr cl)
{
VNCServerImpl *instance = static_cast<VNCServerImpl *>(cl->screen->screenData);
/// @todo we need auth user here
instance->mCallbacks->VRDECallbackClientConnect(instance->mCallback, (int)cl->sock);
instance->uClients++;
cl->clientGoneHook = clientGoneHook;
return RFB_CLIENT_ACCEPT;
}
We can see that numbers of clients (part of IVRDEServerInfo) increase. Why dont call VRDECallbackProperty to fire VRDEServerInfoChangedEvent? I need to callback vnc connect situation by pyvbox:VBoxEventType.on_vrde_server_info_changed, but i cant, because IVRDEServerInfoChangedEvent not triggered.
Note:
See TracTickets
for help on using tickets.


update. this problem is present in VirtualBox 5.2 builds too