-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nxdialog keeps hanging around #1042
Comments
The user where this nxdialog was found from says he never saw that dialog and he thinks that has to do with him closing the VPN connection without disconnecting nx before. I also found crashing nxdialogs from this user. I think this has to do with the display becoming unusable and gtk not noticing it. The user has - for technical reasons - a suboptimal setup: Laptop(Windows, mobaxterm) -> VPN -> somehost (Linux, nxproxy) -> somehost2 (Linux, nxagent). The connection that is breaking is the VPN session. The nxproxy tries to display the dialog on mobaxterm's Xserver which cannot work once the VPN is down.
|
You can force a crash by running nxdialog with an invalid display:
gdb shows this backtrace:
which leads us to https://gitlab.gnome.org/GNOME/gtk/-/issues/994 So probably we need to work around this by checking the display beforehand. |
BTW: --display will be swallowed by gtk, so we can never check that option, it will always be empty |
I found a dangling nxdialog process 2 weeks after the corresponding connection had died. The nxdialog window was not visible anywhere. I am also wondering why the parent pid is 1. It also looks like this had been initiated by nxproxy. We need to clarify when this happens and maybe improve nxproxy to close automatically in certain situations.
The text was updated successfully, but these errors were encountered: