Close Menu
    X (Twitter)
    Hectic GeekHectic Geek
    • Apps
      • Apps for Mac
      • Apps for PCs
      • Best Apps
    • Concepts
      • Comparison
      • For Geeks
      • IT Careers
    • Gadgets
      • Accessories
      • Best Work Laptops
      • Budget Laptops
    • GNU/Linux
      • Ubuntu
    • How To
      • Virtualization
      • Windows
      • Windows How-To
    Hectic GeekHectic Geek
    Home » Kubuntu 17.10[fix]: Fonts Looks Too Big After Enabling Nvidia’s Proprietary Driver?
    GNU/Linux

    Kubuntu 17.10[fix]: Fonts Looks Too Big After Enabling Nvidia’s Proprietary Driver?

    GayanBy GayanJanuary 2, 2018Updated:January 23, 20195 Comments4 Mins Read
    Twitter Reddit Telegram WhatsApp Email
    Share
    Twitter Reddit Telegram WhatsApp Email

    These days my main operating system is Kubuntu 17.10 because I’ve switched to KDE as my desktop environment. However, since my Asus laptop comes with a hybrid GPU setup, I decided to enable the more capable Nvidia GPU by installing its proprietary driver. Once I enabled it on Kubuntu 17.10, then after rebooting, I noticed that the fonts looks slightly (unnecessarily) bigger on the desktop and on the application windows. Luckily I was able to fix it quite easily. So if you’re having the same issue, this post will help you out for fixing it.

    To be honest, I rarely use the Nvidia GPU. And the only reason why I installed and enabled the proprietary driver was to see if it would break the user auto-login feature. This was purely out of my curiosity because that’s what happened in GNOME, while I reviewed Ubuntu 17.10.

    Interestingly however, while it broke the user auto-login feature in Ubuntu 17.10, it did not change the font sizes. But in Kubuntu 17.10, it made the fonts look bigger without breaking the user auto-login function (as shown in the below screenshot).

    So anyway, the easiest way to fix this is through the font configuration settings window of KDE. To open it, search for fonts in the start-menu or from the start-menu navigate to ‘Settings‘ –> ‘System Settings‘ –> ‘Fonts‘. Once you’ve opened it, at the bottom of the configuration window you’ll see a disabled setting called ‘Force fonts DPI’.

    Now simply enable it (by clicking on the small square button) and make sure the value is set to 96, then click on the ‘Apply‘ button.  KDE will notify you that the newly entered DPI (dots or pixels, per inch) settings will only be applied to newly opened applications. So to get a sense of how things look, you can open an application such as the file manager. If you have already opened up the file manager then fonts on it won’t receive the changes you just made. In that case re-open a new window of your file manager and it should display the changes that you just made (below screenshot features the same desktop after changing the DPI to 96):

    If you’re satisfied with the results, then you can either reboot (my preferred option) or logout and re-login so that the changes are applied to the entire desktop.

    That said, 96 may not always work for everyone. Depending on the size of your screen and its native resolution (or the Pixel Density, to be precise) you may have to experiment a little to get the proper value. For instance, in my case the fonts started to look bigger after enabling the proprietary Nvidia driver. That happens when the DPI is too high. Nvidia had set it to 102. So I actually had to reduce it to 96. But if your fonts started to look too small after enabling it, then that’s an indication your DPI is set too low, so to fix it, you have to increase it. In such instances, the general advice is to start off with 96 and then use one quarter of 96 (=24) & use that as the increment, until you reach the optimal setting. So for instance, if 96 doesn’t fix your issue, then try entering 120 (96 + 24) as the DPI value (again, only newly opened application windows will display the changes you’ve just made). If you’re still not happy with the results, try 144 (120 + 24) etc … I guess you get the general idea.

    That said, you should’t fear to experiment a little. And you don’t always have to follow the textbook recommendations. For instance, that one quarter of 96 increment is generally advised to keep the scaling artifacts at minimum. But, these days, pixel density varies a lot from one manufacture to the other. So you can either increase or decrease the DPI freely, and experiment a little, till you arrive at the desired result. Good luck.

    Share. Twitter Reddit Telegram WhatsApp Email
    Gayan

    An RHCE, 'Linux' user with 14+ years of experience. Extreme lover of Linux and FOSS. He is passionate to test every Linux distribution & compare with the previous release to write in-depth articles to help the FOSS community.

    Related Posts

    How to Check Linux CPU Usage?

    February 5, 2024

    Linux export Command: A Comprehensive Tutorial

    February 3, 2024

    AlmaLinux vs Ubuntu – How to Select the Best One?

    October 22, 2023

    AlmaLinux vs Rocky Linux: What you need to know

    August 24, 2023

    Pop!_OS VS Linux Mint, Which One to Select in 2023

    July 27, 2023

    Debian vs Ubuntu Server: A Brief Comparison for Beginners

    July 2, 2023

    5 Comments

    1. Anonymous on January 3, 2018 2:54 am

      Sometimes X.server doesn’t recognize the screen correctly. In my case my 18.4″ display was set to 570 x 320 mm, but has actually only 407 x 229 mm. This resulted in Nvidia setting resolution to 75 dpi. The fonts were looking too small. Then I set the DPI to 105.

      But the correct way is to change the display data. I suggest following explanation and instructions: wiki.manjaro.org/index.php?title=Did_X.server_recognise_your_monitor_correctly%3F

      Reply
      • Gayan on January 3, 2018 6:38 am

        Thank you.

        Reply
    2. lascapi on April 20, 2020 4:33 pm

      Thank you ^^’ I didn’t understand why the user interface was normal and fonts tiny !! 

      Reply
      • Gayan on May 14, 2020 9:03 pm

        You’re welcome.

        Reply
    3. hikaruelio on February 16, 2021 7:20 am

      This fixed the issue for me in 2021. ThinkPad T430 with the NVS 5400 dGPU, on Fedora 33. Thank you!

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Latest Posts

    Transforming Geek Culture with Advanced Software Development

    April 8, 2024

    The Role of Technology in Enhancing Digital Signage Solutions

    February 21, 2024

    How to Check Linux CPU Usage?

    February 5, 2024

    Linux export Command: A Comprehensive Tutorial

    February 3, 2024

    [Fixed] HDMI No Signal to TV or Monitor on Windows 10/11

    November 7, 2023

    AlmaLinux vs Ubuntu – How to Select the Best One?

    October 22, 2023

    Subscribe to Updates

    Get the latest news and updates from Hectic Geek. We won't overload you or sell your data!

    Contact
    • About Us
    • Contact Us
    • Privacy Policy
    • Write for Us
    X (Twitter)
    © 2026 Hectic Geek.

    Type above and press Enter to search. Press Esc to cancel.