summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorMario Sanchez Prada <msanchez@gnome.org>2018-05-18 13:56:10 +0100
committerMario Sanchez Prada <msanchez@gnome.org>2018-05-18 14:03:53 +0100
commit9be0fc0868420369e9bb9acb00a457028b462b95 (patch)
tree81ab3b9172b0f0053821922b5759c00b40f92cdc /COPYING
parent84364a7ef4751fa74af0aa34686605dd76ae0a9d (diff)
downloadgtk+-issue1084.tar.gz
application: Complete the startup sequence before quitting remote instancesissue1084
When running a remote GtkApplication via the command line, such application will hand things over to the primary instance and quit, which can leave the launcher (e.g. Shell) waiting forever for the event that would complete the startup sequence if StartupNotification=true is present in the .desktop file. This can cause undesired effects in the launcher, which will likely end up terminating the sequence itself at some point after a timeout if such event is never issued. To fix it, simply check whether we're in that situation once the command line has been handled for remote instances and notify the completion at that moment, which will only issue the event that the launcher is expecting if an startup ID was set in the first place. https://gitlab.gnome.org/GNOME/gtk/issues/1084
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions