Settings icons look blurry (1366x768 resolution)

[wesinator]

Prerequisites

• [x] Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Settings icons appear blurry / fuzzy

Fonts in general also seem blurry - https://github.com/atom/atom/issues/17502

Steps to Reproduce

Windows 8.1 1366x768 display

1. Open Settings

Expected behavior: Crisp and clear icons

Actual behavior: Icons appear fuzzy / blurry

Reproduces how often: always

Versions

Windows 8.1 x64

Atom    : 1.34.0
Electron: 2.0.16
Chrome  : 61.0.3163.100
Node    : 8.9.3

[rsese]

Thanks for the report - can you confirm what debugging steps you've tried? E.g. have you tried some of the GPU related debugging steps mentioned in that other issue?

Also, is the blurriness new for you as of 1.34.0 or has it always been this way for you?

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[wesinator]

Thanks for the report - can you confirm what debugging steps you've tried? E.g. have you tried some of the GPU related debugging steps mentioned in that other issue?

Also, is the blurriness new for you as of 1.34.0 or has it always been this way for you?

The GPU debugging steps did not fix it. This is on basic Intel HD graphics so that probably wouldn't make much difference anyway.

It's always been this way, still an issue on 1.36.1