Results 1 to 9 of 9

Thread: Big scaling problems

  1. #1

    Default Big scaling problems

    Hello there !

    I've bought a QHD monitor (2560x1440, 27 inches) and I'm having big scaling issues when applying a 125% global scale factor.

    Some fonts in some programs are so small it's unreadable (java program):

    https://ibb.co/bRL9brf


    Some fonts in other programs are so big that it's unusable (teamviewer):

    https://ibb.co/Lh2RSqd

    I don't know where to start to fixe those issues...

    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,091
    Blog Entries
    1

    Default Re: Big scaling problems

    Just in case this is of interest....
    https://wiki.archlinux.org/index.php...a_applications
    openSUSE Leap 15.2; KDE Plasma 5

  3. #3

    Default Re: Big scaling problems

    Hello,

    Thanks for your answer, I tried to add the parameters but it doesn't change anything unfortunately

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,370

    Default Re: Big scaling problems

    Quote Originally Posted by iranoe86 View Post
    I've bought a QHD monitor (2560x1440, 27 inches) and I'm having big scaling issues when applying a 125% global scale factor.
    Assuming that, you're using the KDE Plasma GUI – I have absolutely no idea regarding the case that, you're using another GUI – with the user “root” and from a CLI, execute:
    Code:
     # inxi -a -G
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 08:00.0 
               chip ID: 1002:15d8 
               Display: server: X.Org 1.20.3 compositor: kwin_x11 driver: amdgpu display ID: :0 screens: 1 
               Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5") s-diag: 1165mm (45.9") 
               Monitor-1: HDMI-A-0 res: 3840x2160 hz: 60 dpi: 140 size: 698x393mm (27.5x15.5") diag: 801mm (31.5") 
               OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.18-lp152.41-default LLVM 9.0.1) v: 4.5 Mesa 19.3.4 direct render: Yes 
     #
    Take note of the “dpi:” value being reported for the Monitor.
    • Using the KDE Plasma System Settings, section “Fonts”, force the DPI setting used by fonts to use the value reported by “inxi” for your monitor.
    • Job done.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,091
    Blog Entries
    1

    Default Re: Big scaling problems

    Quote Originally Posted by dcurtisfra View Post
    Assuming that, you're using the KDE Plasma GUI – I have absolutely no idea regarding the case that, you're using another GUI – with the user “root” and from a CLI, execute:
    Code:
    inxi -a -G
    There is no reason to run this as root. Run it as regular user from a terminal.
    openSUSE Leap 15.2; KDE Plasma 5

  6. #6

    Default Re: Big scaling problems

    Thanks for your answer, but it didn't change anything for Java programs or Teamviewer. On top of that, it made KDE fonts look worse. They're distorted and there are random artifacts (random white lines when I open Konsole)


    Monitor-1: DP-0 res: 2560x1440 hz: 144 dpi: 109
    size: 597x336mm (23.5x13.2") diag: 685mm (27")
    OpenGL:renderer: GeForce GTX 1070 Ti/PC
    Ie/SSE2

    v: 4.6.0 NVIDIA 450.66
    direct render: Yes






  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,091
    Blog Entries
    1

    Default Re: Big scaling problems

    Quote Originally Posted by iranoe86 View Post
    Thanks for your answer, but it didn't change anything for Java programs or Teamviewer.
    Yes, that suggestion was only related to the KDE environment (inc KDE apps), so not applicable to your Java application issue. (Not sure about Teamviewer.)
    Last edited by deano_ferrari; 25-Sep-2020 at 17:40.
    openSUSE Leap 15.2; KDE Plasma 5

  8. #8

    Default Re: Big scaling problems

    Hi,

    This is something that I struggled with for a long time and only recently understood how to solve the problems that I experienced.
    Currently I am running a 4K screen as my main display and a QHD at my secondary. Things now look acceptable but not perfect,
    particularly since my lower resolution screen is much larger than the 4K one.

    The most important realization is that if you are seeing different problems with different applications, then they are likely
    different issues.
    Although they are running on the same environment, apps can be built with different toolkit and even different
    versions of the same toolkit, each with their own behavior.

    When debugging a scaling issue, it helps to find out which toolkit version the application is using. You can go to Yast2 Software
    Management and look for the particular application. Under the Dependencies tab, you will see the libraries it is using which will
    tell you the toolkit. Watch for the version because correcting for gtk2 is very different than gtk5.

    The easiest to fix so far is Qt5 which has settings to control scaling. You can use dconf to change those or set then using env
    variables. There are three:

    QT_AUTO_SCREEN_SCALE_FACTOR - Set to 0 to control scaling.
    QT_SCALE_FACTOR - The actual scale factor applied to everything Qt5.
    QT_SCREEN_SCALE_FACTORS - The actual scale factor applied to pixels but not font sizes.

    For X directly, there is a file /etc/X11/xorg.conf.d/50-monitor.conf which lets you set the resolution in DPI. I found that I need to
    reduce it significantly compared to reality, so it is mostly a trial and error process. On a 100dpi screen, having it at 144dpi gives
    me usable output. On the 200dpi screen, it is set to 240dpi. Unfortunately, it is trial and error as using the real values produces
    extremely large output.

    Most problems were solved by searching online for scaling issues reported with each specific application and discarding most
    advice older than 2 years because those tend to no longer work. On LEAP 15.1 for example, there was some chrome:/flags to
    set but they are not needed on LEAP 15.2

    VLC was particularly painful to fix and still has oddly scaled elements but I could never fix the one from the OpenSUSE repo
    and switched it to Packman and VLC's own repo, both with usable (but not perfect) results.

    Hope this helps!

    - Itai
    - Itai
    http://www.cybernium.net

  9. #9

    Default Re: Big scaling problems

    I'm going to give it a try thanks

    It's a shame that it's not working out of the box. QHD and 4K monitors are becoming more and more common.

    Quote Originally Posted by idanan View Post
    Hi,

    This is something that I struggled with for a long time and only recently understood how to solve the problems that I experienced.
    Currently I am running a 4K screen as my main display and a QHD at my secondary. Things now look acceptable but not perfect,
    particularly since my lower resolution screen is much larger than the 4K one.

    The most important realization is that if you are seeing different problems with different applications, then they are likely
    different issues.
    Although they are running on the same environment, apps can be built with different toolkit and even different
    versions of the same toolkit, each with their own behavior.

    When debugging a scaling issue, it helps to find out which toolkit version the application is using. You can go to Yast2 Software
    Management and look for the particular application. Under the Dependencies tab, you will see the libraries it is using which will
    tell you the toolkit. Watch for the version because correcting for gtk2 is very different than gtk5.

    The easiest to fix so far is Qt5 which has settings to control scaling. You can use dconf to change those or set then using env
    variables. There are three:

    QT_AUTO_SCREEN_SCALE_FACTOR - Set to 0 to control scaling.
    QT_SCALE_FACTOR - The actual scale factor applied to everything Qt5.
    QT_SCREEN_SCALE_FACTORS - The actual scale factor applied to pixels but not font sizes.

    For X directly, there is a file /etc/X11/xorg.conf.d/50-monitor.conf which lets you set the resolution in DPI. I found that I need to
    reduce it significantly compared to reality, so it is mostly a trial and error process. On a 100dpi screen, having it at 144dpi gives
    me usable output. On the 200dpi screen, it is set to 240dpi. Unfortunately, it is trial and error as using the real values produces
    extremely large output.

    Most problems were solved by searching online for scaling issues reported with each specific application and discarding most
    advice older than 2 years because those tend to no longer work. On LEAP 15.1 for example, there was some chrome:/flags to
    set but they are not needed on LEAP 15.2

    VLC was particularly painful to fix and still has oddly scaled elements but I could never fix the one from the OpenSUSE repo
    and switched it to Packman and VLC's own repo, both with usable (but not perfect) results.

    Hope this helps!

    - Itai

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •