From: kostadinsh <kostadinsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: firefox: Generic Wayland icon appears in the KDE alt-tab menu.
Date: Sat, 06 Jan 2024 22:18:42 +0100 [thread overview]
Message-ID: <20240106211842.1oQE9wAY05AAPTqcEMrKzQrfMOibvzwCfy0if5xAqmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48052@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
New comment by kostadinsh on void-packages repository
https://github.com/void-linux/void-packages/issues/48052#issuecomment-1879831144
Comment:
> [Try this?](https://www.linuxquestions.org/questions/slackware-14/firefox-shows-generic-wayland-icon-on-kde-plasma-4175714169/#post6365253)
Setting the desktop file name in the special application settings to `firefox` like this fixes the issue, but that's just a workaround:
Other distros don't have this issue. Also noticed that "Window class (application)" appears as "firefox Firefox", which I think should be just "firefox". Which is probably caused by https://github.com/void-linux/void-packages/blob/1129a5bdb274aa93d2b8a6dcf9513cd49b9c22b7/srcpkgs/firefox/template#L216 and https://github.com/void-linux/void-packages/blob/1129a5bdb274aa93d2b8a6dcf9513cd49b9c22b7/srcpkgs/firefox/patches/fix-firefox-desktop.patch#L13
See also: https://www.linuxquestions.org/questions/slackware-14/firefox-slackbuild-needs-moz_app_remotingname%3D-firefox-for-working-taskbar-icons-on-wayland-4175731039/
Edit: I am going to build firefox locally with `MOZ_APP_REMOTINGNAME="firefox"`, and report back.
next prev parent reply other threads:[~2024-01-06 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 19:44 [ISSUE] " kostadinsh
2024-01-05 16:27 ` Clos3y
2024-01-06 21:14 ` kostadinsh
2024-01-06 21:18 ` kostadinsh [this message]
2024-01-06 22:09 ` kostadinsh
2024-02-20 5:58 ` bmp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240106211842.1oQE9wAY05AAPTqcEMrKzQrfMOibvzwCfy0if5xAqmY@z \
--to=kostadinsh@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).