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
QtSingleApplication relies heavily on pids, this breaks if two client processes get the same pid.
This is for example the case in the flatpak sandbox. See: flathub/com.nextcloud.desktopclient.nextcloud#12
Yes, I'm totally for replacing QtSingleApplication which is a very old piece of a forked code we're carrying. How would you envision the transition though? I see they recommend git submodule but I'm not too hot on that, that said if it's unpackaged territory we might have no choice...
But a Git submodule is not any worse than the status quo, right? QtSingleApplication is fully vendored so a submodule would arguably an improvement. And having a vendored-but-working implementation would still be preferable to having a vendored-and-subtly-not-working implementation.
thank you for opening the request.
The client has improved a lot since the ticket was opened.
Can you support us and check if it is still relevant? In this case we appreciate a new ticket or a comment here.
Thank you for your support
QtSingleApplication relies heavily on pids, this breaks if two client processes get the same pid.
This is for example the case in the flatpak sandbox. See: flathub/com.nextcloud.desktopclient.nextcloud#12
This is why I propose to replace QtSingleApplication with something else.
One alternative would be for example: https://github.com/itay-grudev/SingleApplication
I have opened this issue to get feedback on this idea.
The text was updated successfully, but these errors were encountered: