Bug 508955 - Blurred Tray Icons
Summary: Blurred Tray Icons
Status: RESOLVED DUPLICATE of bug 506244
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.4.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2025-08-31 04:31 UTC by Bruce Wayne
Modified: 2025-09-03 20:11 UTC (History)
1 user (show)

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


Attachments
check wifi,sound compared to battery (without the %) and sun (19.25 KB, image/png)
2025-08-31 04:31 UTC, Bruce Wayne
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruce Wayne 2025-08-31 04:31:06 UTC
Created attachment 184594 [details]
check wifi,sound compared to battery (without the %) and sun

SUMMARY

some tray icons and their indicators are blurred  when using fractional scaling.

STEPS TO REPRODUCE
1. set display to fractional scaling 125%
2. 
3. 

OBSERVED RESULT

upon close inspection (from screenshot) i see that the notification bell, volume, wifi, and battery percentage are blurred and not as sharp as compared to the telegram, battery icon, and sun icon(the brightness) 

EXPECTED RESULT

having as consistent sharp tray icons 

SOFTWARE/OS VERSIONS

Operating System: CachyOS Linux 
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i3-1220P
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Vivobook_ASUSLaptop X1502ZA_X1502ZA
System Version: 1.0

ADDITIONAL INFORMATION

display specification are 15.5 inch 1920x1080
Comment 1 TraceyC 2025-09-03 20:11:52 UTC
Thanks for the bug report. This is the same problem as in bug 506244. I'm going to merge this report in with the other one, please follow that one for updates.

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