Bug 365714 - Akregator tray icon is very low resolution on high DPI displays
Summary: Akregator tray icon is very low resolution on high DPI displays
Status: RESOLVED FIXED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL: https://fratti.ch/bugdemos/akregator/...
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-15 14:24 UTC by Nicolas F.
Modified: 2020-11-09 10:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas F. 2016-07-15 14:24:17 UTC
On high DPI displays, the tray icon Akregator shows appears to be an upscaled low-resolution one. Both the icon and the number drawn on top of it look very blocky.


Reproducible: Always




✓ fratti@archbook ~ $ akregator --version
akregator 5.2.3
✓ fratti@archbook ~ $ xrandr                                                                 
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767                          
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 290mm x 170mm
   1920x1080     60.00*+  40.00  
   1400x1050     59.98  
   1600x900      60.00  
   1280x1024     60.02  
   1280x960      60.00  
   1368x768      60.00  
   1280x720      60.00  
   1024x768      60.00  
   1024x576      60.00  
   960x540       60.00  
   800x600       60.32    56.25  
   864x486       60.00  
   640x480       59.94  
   720x405       60.00  
   640x360       60.00  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Comment 1 Justin Zobel 2020-11-09 04:05:22 UTC
Thanks for the report Nicolas.

I've just tested this on Akregator from git master and I cannot reproduce the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
Comment 2 Nicolas F. 2020-11-09 10:27:38 UTC
Hi Justin,

this has indeed resolved itself over the past 4 years.

Thanks!