Bug 139921 - Libreoffice apps open on wayland session with generic LO icon
Summary: Libreoffice apps open on wayland session with generic LO icon
Status: RESOLVED DUPLICATE of bug 125934
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-26 10:37 UTC by Paul Webb
Modified: 2022-04-28 12:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Webb 2021-01-26 10:37:06 UTC
Description:
When selecting writer (for example)from a dock or panel on a wayland session, LO opens using the generic gray LO icon, not the blue writer icon.If you the open, say, calc it opens a second occurrence or grouping on the gray icon, not a green calc icon. This happens on both plasma panels and gnome docks. 
     

Steps to Reproduce:
1. Open LO writer from pinned icon on panel or dock
2. Open LO calc from pinned icon on dock
3.

Actual Results:
1. Opens with a new non-pinned gray LO icon.
2. Opens with both writer and calc grouped under gray LO icon 

Expected Results:
writer should open under its own pinned icon as should calc. 
works properly under X11. Has been broken on wayland for years. 


Reproducible: Always


User Profile Reset: No



Additional Info:
According to KDE --- Comment #2 from Vlad Zahorodnii <vlad.zahorodnii@kde.org> ---
> [2031352.323]  -> xdg_toplevel@36.set_app_id("libreoffice-startcenter")

libreoffice doesn't update the app id. Please report this bug to libreoffice
developers.
Comment 1 Jeff Fortin Tam 2021-06-09 12:44:36 UTC
I think the predecessor to this was bug #100158, which also came from https://bugzilla.gnome.org/show_bug.cgi?id=779143 and https://bugzilla.redhat.com/show_bug.cgi?id=1334915
Comment 2 Buovjaga 2022-04-28 12:31:50 UTC

*** This bug has been marked as a duplicate of bug 125934 ***