start wezterm on specific workspace in i3wm fails

[qrockz]

#!/usr/bin/bash
i3-msg workspace 1
i3-msg exec thunderbird
i3-msg workspace 4
i3-msg exec firefox
i3-msg workspace 8
i3-msg exec flatpak run org.wezfurlong.wezterm
i3-msg workspace 2
i3-msg exec nemo

All apps get started BUT wezterm launches on ws 2 but instead it should launch on ws 8.
I've launched this script manually after my i3 desktop was completely loaded and ready.

According to a i3 maintainer it's a startup-notification protocol issue.

i3log

12.03.2024 13:28:01 - _NET_WM_NAME changed to "wezterm"
12.03.2024 13:28:01 - ../src/window.c:window_update_icon:551 - Found _NET_WM_ICON of size: (128,128)
12.03.2024 13:28:01 - ../src/window.c:window_update_icon:588 - Using icon of size (128,128) (preferred size: 25)
12.03.2024 13:28:01 - ../src/window.c:window_update_leader:144 - CLIENT_LEADER not set on window 0x0160007e.
12.03.2024 13:28:01 - ../src/window.c:window_update_transient_for:169 - TRANSIENT_FOR not set on window 0x0160007e.
12.03.2024 13:28:01 - ../src/window.c:window_update_strut_partial:194 - _NET_WM_STRUT_PARTIAL not set.
12.03.2024 13:28:01 - ../src/window.c:window_update_role:219 - WM_WINDOW_ROLE not set.
12.03.2024 13:28:01 - ../src/window.c:window_update_hints:382 - WM_HINTS not set.
12.03.2024 13:28:01 - ../src/window.c:window_update_normal_hints:268 - Could not get WM_NORMAL_HINTS
12.03.2024 13:28:01 - ../src/window.c:window_update_machine:505 - WM_CLIENT_MACHINE not set.
12.03.2024 13:28:01 - ../src/startup.c:startup_sequence_get:277 - No _NET_STARTUP_ID set on window 0x0160007e

quote:

we don't get a startup sequence for wezterm

i3/i3#5947 (comment)