Bug 373706 - Not correct icon of chrome's apps in taskbar
Summary: Not correct icon of chrome's apps in taskbar
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Icons-only Task Manager (show other bugs)
Version: 5.8.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-15 20:22 UTC by Ihor
Modified: 2016-12-15 21:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of alt+tab block and icons-only taskbar (310.95 KB, image/png)
2016-12-15 20:22 UTC, Ihor
Details
screenshot from desktop (1.21 MB, image/png)
2016-12-15 21:29 UTC, Ihor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ihor 2016-12-15 20:22:10 UTC
Created attachment 102801 [details]
screenshot of alt+tab block and icons-only taskbar

Here is attached screenshot with my problem.
My prefer in this case to have real application's icon over the chromium.
I found some discussion about it in https://bugs.kde.org/show_bug.cgi?id=356609 this thread

Can you make it switchable? Add some option to have ability to change behavior displaying of icons as user want. My prefer to see real chrome's app's icon in taskbar too instead chromium's icon (icon of basic process)
Comment 1 Eike Hein 2016-12-15 20:25:35 UTC
Kai, this is fixed right?
Comment 2 Ihor 2016-12-15 20:30:02 UTC
(In reply to Eike Hein from comment #1)
> Kai, this is fixed right?
Comment 3 Ihor 2016-12-15 20:31:10 UTC
I have added information about my distro
(Archlinux)
Comment 4 Kai Uwe Broulik 2016-12-15 20:50:16 UTC
Yeah, chromium should be fixed in 5.8.5 whereas Chrome was fixed for 5.8.4 already.
Comment 5 Ihor 2016-12-15 21:29:57 UTC
Created attachment 102807 [details]
screenshot from desktop

I have installed from aur google-chrome ( Version 55.0.2883.87 (64-bit) ) and ran Todoist and Postman (which are chrome's applications) but still have on taskbar chrome icons instead real on both apps.

Does it really fixed on 5.8.5?
Comment 6 Kai Uwe Broulik 2016-12-15 21:35:26 UTC
Yes, recently Chromium changed its window id which caused our mapping to fail. In 5.8.5 the mapping was adjusted for those changes. There's a chance that your particular distribution opted for yet another window id but it should be fixed.