Bug 450971 - Black square on EasyEffects icon
Summary: Black square on EasyEffects icon
Status: RESOLVED DUPLICATE of bug 448234
Alias: None
Product: Breeze
Classification: Plasma
Component: Icons (show other bugs)
Version: 5.24.2
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: visual-design
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-28 16:47 UTC by naredra81
Modified: 2022-03-28 15:07 UTC (History)
5 users (show)

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

Attachments
EasyEffects icon (44.29 KB, image/png)
2022-02-28 16:47 UTC, naredra81 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description naredra81 2022-02-28 16:47:17 UTC 
Created attachment 147191 [details]
EasyEffects icon

SUMMARY
There's a black square behind EasyEffects icon. The square is aligned to right-bottom of the icon.

EXPECTED RESULT
There shouldn't be a black square behind it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User Edition
(available in About System)
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2022-02-28 20:31:50 UTC 
Apparently it's a Qt bug.
https://github.com/wwmm/easyeffects/issues/867
Comment 2 Nate Graham 2022-02-28 21:37:25 UTC 

*** This bug has been marked as a duplicate of bug 448234 ***
Comment 3 postix 2022-03-28 09:42:56 UTC 
Reopen as the other bug was closed since its scope was considered too broad.
Comment 4 postix 2022-03-28 09:43:24 UTC 
*** Bug 451598 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2022-03-28 13:53:04 UTC 
Don't do that; we need to continue the conversation there. There isn't anything we can to in Breeze to fix this.

*** This bug has been marked as a duplicate of bug 448234 ***
Comment 6 postix 2022-03-28 14:25:10 UTC 
(In reply to Nate Graham from comment #5)
> Don't do that; we need to continue the conversation there. There isn't
> anything we can to in Breeze to fix this.

Alright, but just closing the not specific enough considered bug and keeping the others as duplicate of this closed bug didn't make much sense to me. ;)
Comment 7 Nate Graham 2022-03-28 15:07:27 UTC 
Me neither; that's why I re-opened Bug 448234.