Actually, this helps a lot.
What this tells us is that this is actually a bug in glib2.0 function
g_app_info_launch_uris().
The bug occurs when this is launched with a context including a screen
with gdk_screen_make_display_name(screen)=":0.1" but the parent process
has DISPLAY=":0.0"
Here is a snippet of the relevent code sequence in gnome-panel:
...
gdk_app_launch_context_set_screen (context, screen);
gdk_app_launch_context_set_timestamp (context, timestamp);
local_error = NULL;
retval = g_app_info_launch_uris (appinfo, uris,
(GAppLaunchContext *) context,
...
--
menu items selected from screen 1 open on screen 0
https://bugs.launchpad.net/bugs/346964
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
