firefox first launch opens on wrong workspace

[gulafaran]

have not properly bisected it yet but firefox opens on wrong workspace on first launch.

1. start hl on workspace 1 and open a terminal.
2. go to workspace 2 and open another terminal.
3. go to workspace 3 and open firefox and it opens on workspace 1.

this only happends with initial_workspace_tracking

HL_INITIAL_WORKSPACE_TOKEN d0c3a458-bd4e-4d77-9184-bf1b2ec11f3d -> 1

question is how its able to end up with a token for workspace 1 on first launch when im on workspace 3.
any subsequent launches works. or disabling initial_workspace_tracking makes it also work.

[falkkyburz]

Yes I noticed something similar as well.
Are you opening the terminals with the keybind or hyprlauncher?

Probably because it inherits the token from hyprlauncher.

Can you try if the issue goes away if you strip the token from the child process by adding this to hyprlauncher.conf

finders {
    desktop_launch_prefix = env -u HL_INITIAL_WORKSPACE_TOKEN
}

[vaxerski]

thats not a hyprlauncher token thats you having enabled initial workspace tracking in hyprland

[gulafaran]

thats not a hyprlauncher token thats you having enabled initial workspace tracking in hyprland

i havent changed initial workspace setting, its by default 1 so the tokens should expire after first map from what i can tell, so hyprlauncher should consume it?. the odd thing is its like its both persistent and then firefox also inherits it atleast once.

just have initial workspace tracking set to 1, start hl. switch to worskpace 3. open hyprlauncher, wait 2 seconds, open firefox and it will go to workspace 1 with the hyprland log showing HL_INITIAL_WORKSPACE_TOKEN d0c3a458-bd4e-4d77-9184-bf1b2ec11f3d -> 1 for firefox oddly enough

any later launches it works as normal again

[gulafaran]

and what make things 1000x more annoying is i cant reproduce it in nested, -_- tried various things.

[falkkyburz]

I think it makes sense to be enabled by default, then for the config we can do:

hl.on('hyprland.start', function()
    -- System
    hl.config({misc = {initial_workspace_tracking = 0}})
    hl.exec_cmd('hypridle')
    hl.exec_cmd('hyprpaper')
    hl.exec_cmd('hyprsunset')
    hl.exec_cmd("hyprlauncher -d")
    hl.config({misc = {initial_workspace_tracking = 1}})
    -- Apps
    hl.exec_cmd('firefox')
    hl.exec_cmd('kitty', {workspace = '2 silent'})
end)

[tannerellen]

I think it makes sense to be enabled by default, then for the config we can do:

hl.on('hyprland.start', function()
    -- System
    hl.config({misc = {initial_workspace_tracking = 0}})
    hl.exec_cmd('hypridle')
    hl.exec_cmd('hyprpaper')
    hl.exec_cmd('hyprsunset')
    hl.exec_cmd("hyprlauncher -d")
    hl.config({misc = {initial_workspace_tracking = 1}})
    -- Apps
    hl.exec_cmd('firefox')
    hl.exec_cmd('kitty', {workspace = '2 silent'})
end)

The problem is this affects more than just launching Firefox for example. It also affects password prompts from polkit and file choosers. So that may work for an initial launch but it won't work for the annoying behavior of trying to open a file on workspace 3 and the file chooser pops up on workspace 1 and you have no idea why your app on workspace 3 is not responding.

[me-tiny]

i seem to be having the same issue, but with thunar, hyprpolkitagent, and any file picker popup

just to add some more context. i autostart discord in workspace 7, which is on my second monitor via: hl.exec_cmd("[workspace 7 silent] discord"). then if i click the upload a file option, the file picker opens in whichever workspace i'm currently in on my main monitor. a restart of discord fixes this.

for thunar, i run hl.exec_cmd("thunar --daemon") on startup, and the first spawn of a thunar window always spawns on workspace 1. same thing with hyprpolkitagent.

this behavior only started with 0.55, i had never changed initial_workspace_tracking in my config, so it was always the default.

[Lorenz5024]

I also noticed this behavior with thunar since switching to 0.55.
Did you happen to find a solution for it?

[ashley-paul-12345]

i can confirm having the same behavior with thunar

[me-tiny]

hl.config({
    misc = {
        initial_workspace_tracking = 0,
    }
})

seems to be the solution for now

[vaxerski]

disable initial workspace tracking. It sucks and is broken

[tannerellen]

disable initial workspace tracking. It sucks and is broken

I'm having the issue referenced above with my polkit windows opening on the first workspace and file choosers opening on the first workspace. For me it happens the first time it runs after boot but once it's run once it behaves appropriately after that.

I have not set initial workspace tracking so it's just the default (so I guess enabled for 1 shot, but that's the default). This problem did not used to happen so this is a regression for sure.

[me-tiny]

unfortunately turning off initial workspace tracking doesn't fix file pickers popping up in the wrong workspace (with the wrong scaling), but i don't seem to have a problem with polkit