VirtualBox

Opened 5 years ago

Last modified 5 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.

Change History (1)

comment:1 by Karlo Dipetrio, 5 years ago

update. this problem is present in VirtualBox 5.2 builds too

Last edited 5 years ago by Karlo Dipetrio (previous) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use