| 2020-08-14 13:21:08 |
Aljoscha Vollmerhaus |
description |
I've created a custom chromium launcher for an internal website, starting chromium in --app mode.
The launcher should get it's own Gnome dash icon.
To match the created windows to the dash icon, I've taken the following measures:
- include "StartupWMClass=myfoo" in the myfoo.desktop file
- gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to myfoo
I've verified the WM_CLASS to be properly set to myfoo using xprop.
However, this does not work when chromium is launched via snap.
All windows get attributed to the chromium dash icon no matter what their WM_CLASS is.
Bypassing snap and launching chromium via /snap/chromium/current/usr/lib/chromium-browser/chrome fixes the problem.
Here are the full chromium exec lines:
Broken:
Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
Working:
Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo --no-first-run --app=https://internal.example.com/ |
I've created a custom chromium launcher for an internal website, starting chromium in --app mode.
The launcher should get it's own Gnome dash icon.
To match the created windows to the dash icon, I've taken the following measures:
- include "StartupWMClass=myfoo" in the myfoo.desktop file
- gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to myfoo
I've verified the WM_CLASS to be properly set to myfoo using xprop.
However, this does not work when chromium is launched via snap.
All windows get attributed to the chromium dash icon no matter what their WM_CLASS is.
Bypassing snap and launching chromium via /snap/chromium/current/usr/lib/chromium-browser/chrome fixes the problem.
Here are the full chromium exec lines:
Broken:
Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/
Working:
Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo --no-first-run --app=https://internal.example.com/
This is on a fully patched 20.04 system. |
|
