The StartupWMClass set in the desktop file (python3) doesn't match that of the running application (com.borgbase.Vorta) and is also too broad.
As far as I can tell, the wmclass hasn't been python3 since 00fa34a, which sets it to com.borgbase.Vorta.
StartupWMClass=python3 also causes other python apps that implicitly get wmclass=python3 to behave on GNOME as if they were Vorta instead: when launched, they appear on GNOME's dock with Vorta's icon. If Vorta was already open, GNOME thinks the other app is just another window of Vorta.
This can be reproduced, for example, with Universal Radio Hacker on GNOME Wayland.
You can check the wmclass of an application on GNOME by opening Looking Glass (Alt+F2 -> lg) -> Windows.
I'd change StartingWMClass to com.borgbase.Vorta. Honestly that line is probably not even needed at this point but it's up to spec and can't hurt.
The StartupWMClass set in the desktop file (python3) doesn't match that of the running application (com.borgbase.Vorta) and is also too broad.
As far as I can tell, the wmclass hasn't been python3 since 00fa34a, which sets it to com.borgbase.Vorta.
StartupWMClass=python3 also causes other python apps that implicitly get wmclass=python3 to behave on GNOME as if they were Vorta instead: when launched, they appear on GNOME's dock with Vorta's icon. If Vorta was already open, GNOME thinks the other app is just another window of Vorta.
This can be reproduced, for example, with Universal Radio Hacker on GNOME Wayland.
You can check the wmclass of an application on GNOME by opening Looking Glass (Alt+F2 -> lg) -> Windows.
I'd change StartingWMClass to com.borgbase.Vorta. Honestly that line is probably not even needed at this point but it's up to spec and can't hurt.