You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tdesktop uses dbus for its IPC. Whenever it needs to create a webview, it spawns a child process that initializes webkit2gtk (Qt initializes gtk as well, so if they initialize different gtk versions (qt may initialize gtk2 while tdesktop initializes gtk3), the process will crash, so it's going on in a separate process), then main process calls methods and subscribes to signals on service of the child process. Child process checks for connection ID to be equal to parent process connection ID when it gets a request to a method, signals have parent connection ID as destination as well. The check in method calls works just fine, but signals don't go to the destination in flatpak for some reason :(. I think xdg-dbus-proxy is the cause of this weird behavior, IPC works just fine if I run the package with --socket=session-bus.
The text was updated successfully, but these errors were encountered:
tdesktop uses dbus for its IPC. Whenever it needs to create a webview, it spawns a child process that initializes webkit2gtk (Qt initializes gtk as well, so if they initialize different gtk versions (qt may initialize gtk2 while tdesktop initializes gtk3), the process will crash, so it's going on in a separate process), then main process calls methods and subscribes to signals on service of the child process. Child process checks for connection ID to be equal to parent process connection ID when it gets a request to a method, signals have parent connection ID as destination as well. The check in method calls works just fine, but signals don't go to the destination in flatpak for some reason :(. I think xdg-dbus-proxy is the cause of this weird behavior, IPC works just fine if I run the package with
--socket=session-bus
.The text was updated successfully, but these errors were encountered: