Bug 403331 - Application icon is not changing after the notification indicator width change
Summary: Application icon is not changing after the notification indicator width change
Status: RESOLVED FIXED
Alias: None
Product: lattedock
Classification: Unmaintained
Component: application (other bugs)
Version First Reported In: git (master)
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-17 23:44 UTC by Viorel-Cătălin Răpițeanu
Modified: 2019-01-19 20:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
The Kontact icon is cropped for a smalled notification indicator. (146.50 KB, image/png)
2019-01-17 23:44 UTC, Viorel-Cătălin Răpițeanu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Viorel-Cătălin Răpițeanu 2019-01-17 23:44:08 UTC
Created attachment 117522 [details]
The Kontact icon is cropped for a smalled notification indicator.

SUMMARY


STEPS TO REPRODUCE
1. Start an application that receive at least 1 notification indicator (like Kontact). When you receive an item, the application icon will be cropped to around the notification indicator.
2. Wait until the application receive more than notifications so that indicator width changes.

OBSERVED RESULT
The icon is not modified anymore around the new indicator size. (see attached image)

EXPECTED RESULT
The icon should be modified around the new notification indicator width.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3
Comment 1 Michail Vourlakos 2019-01-18 12:20:23 UTC
I can not reproduce this...

please show me steps to reproduce with following.
You can send notifications through command prompt:
"qdbus org.kde.lattedock /Latte updateDockItemBadge"

for example:

"qdbus org.kde.lattedock /Latte updateDockItemBadge dolphin 2"

sends for dolphin in Latte 2 notifications... etc.
Comment 2 Viorel-Cătălin Răpițeanu 2019-01-18 19:30:02 UTC
I have a feeling that this is probably related to the behavior seen in ticket 403353. Can we let this a bit open until the root cause of the previously mentioned ticket is found?
Comment 3 Michail Vourlakos 2019-01-19 20:22:50 UTC
I think this should be fixed by: https://bugs.kde.org/show_bug.cgi?id=403353
Comment 4 Viorel-Cătălin Răpițeanu 2019-01-19 20:31:33 UTC
Based on the 403353 fix, I think that this ticket can be closed. Doesn't look like this issue is reproducible anymore.