You are not logged in.
I had a config which was working before the previous update which used to open browser silently on workspace 2 but from last week it started opening on workspace 1 after the hyprland update
here the config:
exec-once = [workspace 2 silent] vivaldi
i have tried to read the update manual but it was not that helpful. Saw the same question on reddit which had no answers here is the reddit link: https://www.reddit.com/r/hyprland/comme … workspace/
Any help much appreciated!!!
Last edited by mia (Today 07:02:40)
Offline
yes as the reddit user said, try using a window rule instead of the dispatcher.
windowrulev2 = workspace 2 silent, class:^(Vivaldi-stable)$
exec-once = vivaldi
before that confirm Vivaldi or your desired browser's class name with "hyprctl clients"
edit: this rules are outdated.
Last edited by 5hridhyan (Yesterday 16:35:44)
We don’t finish life. We just learn to love the unfinished lines. — Grok
Offline
I tried this but still its not working
This is hyprctl client result:
Window 557ee38d6630 -> Hyprland Startup workspace problem / Newbie Corner / Arch Linux Forums - Vivaldi:
class: vivaldi-stable
title: Hyprland Startup workspace problem / Newbie Corner / Arch Linux Forums - Vivaldi
initialClass: vivaldi-stable
initialTitle: Vivaldi - Vivaldi
this is not working:
windowrulev2 = workspace 2 silent, class:^(vivaldi-stable)$
exec-once = vivaldi
I had tried this before and it was doing the same thing as before.
Offline
Is the problem limited to the browser? Can you control the behavior of eg. a foot terminal this way?
Is vivaldi running as native wayland client or via xwayland?
Offline
I suppose this is a vivaldi problem, other application like firefox or kitty seems to be opening on their respective workspace when "exec-once = [workspace $ silent] $app" is used, when using window rule it opens all the application on workspace 1.
Vivaldi is running as native wayland client
well here is the full hyprctl response:
Window 55a4e09d4c80 -> Hyprland Startup workspace problem / Newbie Corner / Arch Linux Forums - Vivaldi:
mapped: 1
hidden: 0
at: 6,48
size: 1908,1026
workspace: 1 (1)
floating: 0
pseudo: 0
monitor: 0
class: vivaldi-stable
title: Hyprland Startup workspace problem / Newbie Corner / Arch Linux Forums - Vivaldi
initialClass: vivaldi-stable
initialTitle: Vivaldi - Vivaldi
pid: 1476
xwayland: 0
pinned: 0
fullscreen: 0
fullscreenClient: 0
grouped: 0
tags:
swallowing: 0
focusHistoryID: 2
inhibitingIdle: 0
xdgTag:
xdgDescription:
contentType: none
Offline
this is not working:
windowrulev2 = workspace 2 silent, class:^(vivaldi-stable)$
exec-once = vivaldi
my bad
this shows the Vivaldi's startup model, I guess Vivaldi maps an initial dummy surface on the current workspace (1) very early, then replaces it with the real topleveltry this as a workaround
windowrule = move 2 silent, class:^(vivaldi-stable)$
exec-once = vivaldi
You can add a small delay if needed, but that’s just a timing hack:
exec-once = sleep 1 && vivaldi
EDIT:
thanks @system72 for pointing it out i'm really outdated
@OP try this
windowrule {
name = vivaldi-startup
match:initial_class = vivaldi-stable
workspace = 2 silent
}
exec-once = vivaldiLast edited by 5hridhyan (Today 06:41:19)
We don’t finish life. We just learn to love the unfinished lines. — Grok
Offline
try this as a workaround
windowrulev2 = move 2 silent, class:^(vivaldi-stable)$
exec-once = vivaldi
Offline
windowrule {
name = vivaldi-startup
match:initial_class = vivaldi-stable
workspace = 2 silent
}
exec-once = vivaldi
This Works!! I tried it before but was executing vivaldi first and not the other way around.
Thank you guys for all you help!!!
Offline