Comment # 20 on bug 1199020 from Sorin Fatu

(In reply to Steffen Winterfeldt from comment #19)
> Thanks!
> 
> Then we definitely need to rethink the logic in that patch mentioned
> in comment 16.

Just going based on my monitor, the DPI should be around 141 putting it under
the threshhold for scaling.
But line 82 in Yast2.call ends in a result of 144. This seems to be due to a
division by 48, rounding followed by multiplication by 48

(($MON_WIDTH_PX/($MON_WIDTH_MM*0.0393701)/48).round)*48

In my case as an example:
$MON_WIDTH_PX = 1920
$MON_WIDTH_MM = 344

($MON_WIDTH_PX/($MON_WIDTH_MM*0.0393701) = 141.7673653

Should this be rounded and used as a value it would fall under the 144 cut-off
point. 

Probably adding a $DPIR as $MON_WIDTH_PX/($MON_WIDTH_MM*0.0393701)).round and
using that in the if statement at line 119  while still using $DPI for
set_xft_dpi would correct the issue.

I am not a developer so i might be totally wrong here, I'm just trying to help.