After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 156413 - Handle startup notification forwarding
Handle startup notification forwarding
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
git master
Other Linux
: High normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 157234 (view as bug list)
Depends on:
Blocks: 149028
 
 
Reported: 2004-10-25 17:58 UTC by Elijah Newren
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: 2.10.0
GNOME version: 2.9/2.10


Attachments
Handle timestamp forwarding (1.21 KB, patch)
2004-10-25 18:01 UTC, Elijah Newren
none Details | Review

Description Elijah Newren 2004-10-25 17:58:43 UTC
focus stealing prevention has been re-enabled in CVS HEAD for metacity.  This
means that applications need to set their _NET_WM_USER_TIME for any windows that
are to be mapped.  startup-notification launchers combined with gtk+ handle
almost all cases, but it can't handle cases like a gnome-terminal instance that
asks a previously running instance to open a window instead of opening one
itself.  To handle that, gnome-terminal must have the new instance forward the
DESKTOP_STARTUP_ID to the already running instance (which it already does), and
have the already running instance parse the timestamp from the startup id and
set the _NET_WM_USER_TIME of the window it opens to that value.

I will attach a patch momentarily that does this.  The patch won't actually
work, however, until the startup-notification module is patched to provide the
new functions used in this patch (see bug 151245).
Comment 1 Elijah Newren 2004-10-25 18:00:21 UTC
Oops!  I meant to file this against gnome-terminal.  Reassigning...
Comment 2 Elijah Newren 2004-10-25 18:01:16 UTC
Created attachment 33034 [details] [review]
Handle timestamp forwarding
Comment 3 Elijah Newren 2004-11-03 14:48:08 UTC
*** Bug 157234 has been marked as a duplicate of this bug. ***
Comment 4 Mariano Suárez-Alvarez 2004-11-05 05:03:37 UTC
This is in HEAD as of now.

Thanks!