Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Fix StartupWMClass for .desktop file on Linux #9313

Closed
BachoSeven opened this issue Apr 18, 2020 · 1 comment
Closed

Feature Request: Fix StartupWMClass for .desktop file on Linux #9313

BachoSeven opened this issue Apr 18, 2020 · 1 comment
Labels
closed/duplicate Issue has already been reported

Comments

@BachoSeven
Copy link

BachoSeven commented Apr 18, 2020

Description

On the latest nightly build, when using the provided brave-browser-nightly.desktop file, the StartupWMClass string (from xprop) is ' "WM_CLASS(STRING) = "brave-browser", "Brave-browser" '; however, when adding the .desktop file to a dock or similar interfaces and starting Brave from there, a different icon is created and shown as the launched app on the launcher.

I found an easy workaround (see below) that I have to apply on every update of the app, however it would be easy to implement it. This issue is not limited to Ubuntu, as WMClass is a property of X.

Steps to Reproduce

  1. Install Brave Nightly on Ubuntu (18.04 or later)
  2. Add the .desktop file as a favourite application on the dock
  3. Launch the application from the dock

Actual result:

Creates a different icon in the dock:

image

Expected result:

Respect WMClass of the launcher's icon in the dock (obtained using the workaround described below):

image

Reproduces how often:

N/A

Brave version (brave://version info)

Brave: 1.9.32 Chromium: 81.0.4044.113 (Official Build) nightly (64-bit)
Revision: cf9d66371ea608e227eed56ccba3abc2701bd23d-refs/branch-heads/4044@{#936}
OS: Linux

Version/Channel Information:

  • Can you reproduce this issue with the nightly channel? YES

Miscellaneous Information:

An easy workaround for this is just to add the line StartupWMClass="Brave-browser" under the [Desktop Entry] section of brave-browser-nightly.desktop.

I also checked it out the other channels releases, and the issue seems to be independent of the channel.

@fmarier
Copy link
Member

fmarier commented Apr 29, 2020

Let's discuss that fix on #1746.

@fmarier fmarier closed this as completed Apr 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/duplicate Issue has already been reported
Projects
None yet
Development

No branches or pull requests

2 participants