I am using Arch Linux mate and I accidentally made my DPI settings really really large and now I can't change them back to a smaller setting because it's so large that it's not visible on my screen to fix it. Is there a way to correct DPI settings in the Command Line or any other solution...

I am trying Kubuntu 18.10 and I have a nvidia GTX 1060 (driver 418), a LG 27" 4k monitor (27UD58-B ) and an older HP 22" 1680x1050 monitor (HPw2207) with a VGA cord and a VGA-> DP converter. My issues are as follow: 1) I can't get my vga screen with converter to use a resolution above 1280*1024 2) I'd like to use screen scaling because everything is so damn small on the 4k display. I'd want the scaling to only be done on the high-dpi display if possible. **Current setup:** I am using Nvidia drivers 418.56. $ nvidia-smi Mon Apr 15 15:07:47 2019 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 106... Off | 00000000:23:00.0 On | N/A | | 10% 64C P0 25W / 120W | 739MiB / 6076MiB | 3% Default | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| | 0 958 G /usr/lib/xorg/Xorg 386MiB | | 0 1413 G /usr/bin/kwin_x11 192MiB | | 0 1432 G /usr/bin/krunner 1MiB | | 0 1434 G /usr/bin/plasmashell 111MiB | | 0 1509 G /usr/bin/latte-dock 29MiB | | 0 9387 G /usr/lib/firefox/firefox 1MiB | +-----------------------------------------------------------------------------+ and normal higher resolutions are not available: $ xrandr Screen 0: minimum 8 x 8, current 4864 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 2560x1440 59.95 1920x1080 60.00 59.94 1600x900 60.00 1280x1024 60.02 1280x800 59.81 1280x720 60.00 59.94 1152x864 59.96 1024x768 60.00 800x600 60.32 720x480 59.94 640x480 59.94 59.93 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1024x1280+3840+832 left (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.02*+ 1280x960 60.00 1152x864 75.00 1024x768 85.00 75.03 70.07 60.00 800x600 85.06 75.00 72.19 640x480 85.01 59.94 DP-5 disconnected (normal left inverted right x axis y axis) **First issue: fixing resolution** I have tried to "addmode" using xrandr, but I get a BadMatch error. This is apparently normal with nvidia video cards. $ cvt 1680 1050 60 # 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync $ xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync $ xrandr --addmode DP-4 1680x1050_60.00 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 18 (RRAddOutputMode) Serial number of failed request: 45 Current serial number in output stream: 46 My /etc/X11/xorg.conf file has been generated by nvidia usind sudo nvidia-xconfig : $ sudo nvidia-xconfig Using X configuration file: "/etc/X11/xorg.conf". Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup' New X configuration file written to '/etc/X11/xorg.conf' The xorg.conf only contains one monitor, is this normal. I have tried to add a "Modeline" line under the Monitor0, but it didnt change anything. # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 418.56 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection **Second issue : scaling** I have taken two steps to allow the HiDPI screen to display text and GUI in a more readable size: 1) System settings - fonts - Force Font DPI 144 (instead of 96) 2) system settings- display and monitors - scale display 1.5 (instead of 1). I would lke these settings to only apply to the 4k monitor, is this possible at all?

I've just got brand new Lenovo P1 gen7 with 16" with decent 3840x2400 resolution. Fedora 42 handles it pretty well: it let me set up scaling to whatever suits me, and that's all. However KVM guest does not seem to read the screen size properly. Vm's icons and texts are extremely tiny. It's just annoyng to set it up internally for every VM I'm runnig and change it every time I start it on other display. Is it possible to make qemu/KVM/libvirt somehow report the accual size of the window/screen in DPI or mm, so VM could decide if it should run on 1:1 or in scaling mode in more-less automatic manner?

I have a high DPI display. On X11, I scaled the display to 125% by forcing the font DPI to 120 (which is 96*1.25) as a workaround since Plasma's display scaling always caused slight blurriness of icons. Since the upgrade to Plasma 6, this trick no longer worked and I got back the same problem of blurry icons, especially annoying in the taskbar.

**The problem**: X-server serves fonts at a fixed resolution of **100dpi**, rather than the current window system resolution (xdpyinfo | grep -F resolution). **A bit of theory**. There are legacy server-side fonts which are sent to X clients over the network (via TCP or UNIX socket) either by the X server itself, or by a separate _X Font Server_ (single or multiple). Unlike the usual client-side fonts (Xft, GTK 2+, Qt 2+), the "server" backend (also called the _core X font_ backend) does not support anti-aliasing, but supports network transparency (that is, bitmaps, without any alpha channel, are sent over the network). At the application level, server-side fonts are specified not as an [XftFontStruct](https://keithp.com/~keithp/talks/xtc2001/paper/) (which most often translates into the familiar DejaVu Sans Mono:size=12:antialias=true), but as an [_XLFD_](https://wiki.archlinux.org/index.php/X_Logical_Font_Description) . If we are talking about a local machine, then the same font file can be registered in both font backends at once and be available to both modern GTK and Qt-based applications, and legacy ones (Xt, Athena, Motif, GTK 1.2, Qt 1.x). Historically, there were raster server-side fonts (*.pcf), and a raster has a resolution of its own (not necessarily the same as the window system resolution). Therefore, XLFD has fields such as RESOLUTION_X and RESOLUTION_Y. For a raster font not to look ugly when rendered onto the screen and still have the requested rasterized glyph size (PIXEL_SIZE), the raster resolution must be close to the screen resolution, therefore raster fonts were usually shipped with native resolutions of **75dpi** and **100dpi** (that's why we still have directories such as /usr/share/fonts/X11/75dpi and /usr/share/fonts/X11/100dpi). So, the below lines represent the same 12 pt font

-bitstream-charter-bold-r-normal--12-120-75-75-p-75-iso8859-1
-bitstream-charter-bold-r-normal--17-120-100-100-p-107-iso8859-1

with a rasterized glyph size of * **12px** at **75dpi**, and * **17px** at **100dpi**, respectively. But, in addition to raster fonts, there are vector, or outline fonts (_TrueType_, _OpenType_, _Adobe Type 1_), which can be scaled by any factor and still look good when rendered onto the screen. Some X-server implementations (notably, _XSun_) also supported the _Adobe Type 3_ format, where glyphs were described using the Turing-complete _PostScript_ language. Of course, the concept of raster resolution does not apply to vector fonts, so I can request zeroes (0) or even asterisks (*) in the RESOLUTION_X and RESOLUTION_Y fields, and, in theory, my X server should give me exactly the font requested. This is directly stated in the _Arch Linux Wiki_ article at the link above: > Scalable fonts were designed to be resized. A scalable font name, as shown in the example below, has zeroes in the pixel and point size fields, the two resolution fields, and the average width field. > > ... > > To specify a scalable font at a particular size you only need to provide a value for the POINT_SIZE field, the other size related values ​​can remain at zero. The POINT_SIZE value is in tenths of a point, so the entered value must be the desired point size multiplied by ten. So, either of the following two queries should return a **12pt** Courier New font at the window system resolution:

-monotype-courier new-medium-r-normal--*-120-*-*-m-*-iso10646-1
-monotype-courier new-medium-r-normal--0-120-0-0-m-0-iso10646-1

**Or so I thought**. The thing is, after migration from 96...115dpi monitors to a **162dpi** 4k monitor, I noticed that my carefully selected vector fonts suddenly became too small. And it turned out that unless you explicitly set RESOLUTION_X and RESOLUTION_Y fields to **162** (and no one in his right mind would do so -- it would require rewriting dozens of Xresources lines every time one changes his monitor), then X server defaults to rendering the font at **100dpi** instead of **162**. The difference between **17** and **27** pixels (the factor of 1.62 = 162 / 100) is quite noticeable. Here's an example for a modern _Debian 10_ box: I thought this regression was a consequence of people gradually cutting out obsolete subsystems from X11, but in _Debian Woody_, released in 2002 and having a 2.2 kernel, I saw exactly the same thing: The only difference is that _Debian Woody_ renders fonts in a "cleaner" manner, apparently, applying hinting on the server side, before sending bitmaps over the network. So this is not a regression. The problem has always been there and equally affects all vector font types (_TrueType_, _OpenType_, _Type 1_). **Now, the question**. Is there a way, without hard-coding window system resolution into user settings for each individual resource, to get by with less pain than recommended by the author of the [_Sharing Xresources between systems_](https://jnrowe.github.io/articles/tips/Sharing_Xresources_between_systems.html) article? Is it possible to solve the problem by changing the global configuration of the X server itself or the libraries it relies on (libfreetype, libxfont)?

happy XFCE4 user here, I (unluckily) switched to a notebook with 4k display. I managed to adapt most of the aspects, still when hovering on Chrome or Xfce Terminal **the cursor is tiny**. I found that running xrdb -merge ~/.Xresources where ~/.Xresources contains: Xcursor.size: 48 fixes the problem — still have to check the result on an external monitor. **Now the problem is how do I run the command when the computer starts!** I put this in ~/.xprofile: [[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources which seems to be executed, nevertheless the cursor problem remains. I suppose some command is resetting it because if I open a terminal and I manually give the xrdb -merge ~/.Xresources command again it gets sorted at last

I have installed dual OS Win10/Ubuntu, but I have some boot problems. My computer has a Nvidia GPU with a high refresh rate (144Hz) monitor. The monitor has DP 1.4/HDMI 2.1/Type-C interfaces. I first used DP cable, but when I boot the grub does not appear and it enters Ubuntu directly. Then I also connected the monitor's HDMI to the VGA interface on the motherboard (via an adaptor). Now two cables are connected to the monitor and I can switch between DP and HDMI. When I reboot and switch the input to HDMI, the grub can appear in general, if I choose Windows the monitor does not show the graphical interface, but I believe it has entered the Windows OS since the keyboard light is on and the monitor is not really black but with a luminance background. When I reboot and switch the input to DP, the grub does not appear and it enters Ubuntu again. My questions are: 1. Why is GRUB not displayed when I use the DP interface, and Ubuntu starts automatically? 2. Why does GRUB show up when I use the HDMI interface, but the monitor does not show a graphical interface if I choose Windows? 3. What should I do to make the grub displayed if I use the DP interface (because it supports a high refresh rate) to allow me to choose which OS to start? Someone else told me this problem has something to do with the high refresh rate (144Hz) monitor. Thank you for any suggestions!

Which Linux distros have good multi-monitor support for differing DPI, scaling and resolutions? I have 4 27" monitors with 3 resolutions between them: 1080p, 1440p and 4k. Windows handles per monitor scaling correctly (UI elements appear the same size on each monitor). Looking for a Linux distro which can do the same. - Linux Mint 20 Cinnamon supports per monitor scaling, but at such a large performance cost that the system is barely usable. - I haven't found any other distros which claim to support this - My understanding is that Wayland may handle this better than X11, but is not stable and works poorly with many applications, particularly WINE games. - Please don't suggest I buy new monitors :-)

I have a high DPI monitor, and every time I create a Wine prefix the default 96 dpi is minuscule. Is there some kind of console command or script I can run to just set the dpi without having to squint at the winecfg window? I've gathered that the Software/System/CurrentControlSet/Hardware Profiles/Current/Software/Fonts/LogPixels key indicates the DPI. The problem is that every resource I find says to edit the registry with regedit, the GUI program. That is even more of a pain than winecfg! As I recall, in Windows you could write .reg files that can set a registry key. Is it possible to do that and somehow load the key from the command line only? Failing that, is it possible to somehow bypass winecfg and edit the registry file directly?

As far as I understand, all fonts, like SVG, are vector representation, so they scale infinitely well. But here are two magnified "S" characters of the same size, from LibreOffice Writer. This one is 12 point, with Display scaling of 175%, making it a 21 point visible size: Whereas this one is 21 point at Display scaling of 100%: Both have been rendered on the same high-dpi display (2560x1600) but the 175% scaled version is visibly more blurry. What looks like is happening is, the 175% (top) version is simply raster-interpolating up a lower resolution image, effectively treating my display as a lower resolution device than it actually is. IE: why isn't Wayland *_vector_* scaling a vector image format, and what can I do about it? Surely the correct situation is that rendering should happen at the full capability of the display, independently of the scaling factor? Note that both "S"s visibly take exactly the same space on the screen, since I've counteracted the scaling factor by the font size. I've done the same thing on Windows 11 and it doesn't seem to have this unfortunate downside. I should note that I have another monitor attached which has lower DPI and is scaled at 100%. I don't know if that affects things. Note using Ubuntu 22.04 with default Gnome desktop.

After a recent update of Skype it developed these symptoms: - I could see its entry in the task bar, but could not show its window by trying to maximize it - task bar window preview did show the window's thumbnail - when the window was theoretically maximized, I accidentally hovered over its area on the desktop. Mouse pointer was changing and tooltips of familiar Skype UI elements were shown. The window was there, but it was invisible. Online research suggested the window is displayed off the screen. After moving all Skype windows to 0,0 with

xdotool search --class skype windowmove %@ 0 0

Skype window was visible again. I had to use *xdotool* after every Skype start. Updating Skype from *stable* to *unstable* didn't help. My setup is Debian testing with KDE, single HiDPI monitor, nVidia GTX 980.

I am running i3 window manager on Arch Linux, and am trying to use xrandr to use both my laptop screen and desktop monitor together. I intend the screens to have separate workspaces but to be able to move workspaces between monitors as needed. The laptop screen is 4K (3840x2160) but the monitor is only 1920x1080. From research on i3 with multiple monitors, and people with my same situation, I put together the following xrandr command:

$ xrandr --output eDP-1 --mode 3840x2160 --pos 0x0 --auto \\
--output HDMI-1-0 --mode 1920x1080 --pos 3840x0 --auto \\
--panning 3840x2610+3840+0 --scale 2.0x2.0 --fb 7680x2160

Upon running this command, the laptop monitor works as normal (running at 4k with full coverage) but the desktop monitor only display my background image (through feh) and i3 windows on the top left portion (which appears to be a 1920x1080 chunk of the scaled screen). The other three quarters of the display are black. However, I am able to move my cursor between the two displays without issue. The cursor transitions seamlessly between screens and even displays over the black portion of the desktop monitor (on which i3 windows do not show). Is my xrandr command not doing what I intend, or is there some kind of external factor (maybe I have conflicting DPI settings) which is causing this? **Edit**: In case it is relevant, the laptop is running a newer NVIDIA graphics card (RTX 2070) along with Intel integrated graphics. I have the packages nvidia and nvidia-utils installed as graphical drivers and OpenGL support respectively.

I have just switched over to KDE because of my new 4k monitors. I turned on fractional scaling and everything looked great. Only one thing stood out. This: As you can see the text in the desktop effects menu is just messed up. Also the field in the top right corner is off center. I know it has something to do with fractional scaling as if I set the scaling to 2 it doesn't happen. Any other text looks fine even the rest of the text in system settings. It is only in desktop effects and in a few other sub-menus. Anybody got any ideas how to fix this and maybe an idea why this is happening?

This notebook has a 185 dpi display, but I have followed the guidelines for [High DPI](https://en.opensuse.org/High_DPI) and everything was, more or less, fine. Today I updated the system (sudo zypper update) and after a reboot the characters in every XTerm are way too small, while the characters in all the other applications I have opened are OK with respect to character size. I've found something suspicious in the output of xdpyinfo 21:41 boffi@localhost:~ $ xdpyinfo | grep inch resolution: 96x96 dots per inch 21:41 boffi@localhost:~ $ but I'm not sure that before the reboot the resolution was correct. Any suggestion? --- Post Scriptum 21:43 boffi@localhost:~ $ xrandr --dpi 185 fixes the issue, but there is a way to have Xorg started with the correct resolution? --- PPost Scriptum 22:05 boffi@localhost:~ $ xrdb -q | grep -i dpi Xft.dpi: 175 22:06 boffi@localhost:~ $ On the other hand, XTerm _should_ also depend on this value.

I have a problem with QT applications *(i.e. picard or masterpdfeditor )* under GNOME: their interface looks tiny. Instead, GTK application looks good. I would like a global solution which will work across all applications, not a per-application fix. I don't know exactly where the issue begin (is it a QT5 issue or a GNOME issue?) but I'd like to have a **bigger** interface. ***How can I do it?*** I have already tried with a trick explained here but it works partially: - if I launch the apps directly from the terminal, by appending the right variable e.g. QT_SCALE_FACTOR=1.35 picard, the trick works! - while if I launch them from the menu (gnome-shell), the exported variable is completely ignored . ***Is there a way to fix it?*** I have a laptop connected with an external FullHD 24" monitor. I'm on Arch Linux x86_64 and Gnome 3.28/3.30.

I have a 4K display, and the correct scaling would be 3x. I have put Xft.dpi: 300 in .Xresources and GDK_SCALE=3 GDK_DPI_SCALE=-1 in /etc/environment. This can scale most applications, but the C++ applications that use gtkmm do not scale. Some apps are Nitrogen and GParted. Using this method, the text scales but not the icons. How do I scale the icons for gtkmm applications?

I asked a similar question about hiDPI scaling here . This question regards fixing scaling on a specific application, the other question is about a universal hiDPI mode. I am running ubuntu derivative Pop!_OS 19.04 in Gnome. Edit: I have found this issue arises in CentOS, Fedora, and Debian as well. I built a .deb package for DaVinci Resolve 16 with MakeResolveDeb and it seems to work fine, but it does not scale properly. Scaling looks similar to this This is a known (unfixed) issue, as seen here The solution runscaled doesn't seem to work. Is there a known way to solve the scaling issue for this specific application?

I'm having issues with scaling on Wayland with Fedora 33 (Radeon 6900 XT, kernel 5.10.15-200). I've got double 4k 27" monitors. Scaling changes the size of UI components correctly, so setting it to 200% in gnome settings makes everything appear twice as big, but most of the programs I'm using detects scaled resolution (UHD/2 = FHD) but not the scaling factor (2x). Effect of this is that a program is rendered in FHD instead of UHD and it makes it blurry to display on UHD monitor. I've run through the ArchWiki for HiDPI but nothing seems to work. Below is a screenshot that compares font rendering of Firefox and Visual Studio. Most of the programs I'm using are blurry with wayland scaling (e.g. Visual Studio, Android Studio, Slack, Mailspring) Any known way to solve it or people using wayland with HiDPI are not bothered with blurrines?

I asked a similar question about hiDPI scaling here . This question regards a universal hiDPI mode, the other question is about fixing scaling on a specific application. I am using a 4k monitor in Pop!_OS 19.04 running Gnome. The OS automatically detects this and changes into hiDPI mode, but only after I log in after boot. This means the log in screen when I boot is far too small. Additionally, when I log in, the screen flickers and I get a notification Displays Set to HiDPI mode every time. The problem does not arise when suspending the computer. The command to change to hidpi mode manually is gsettings set com.system76.hidpi enable true but this does not seem to permanently change to hidpi mode. Running this command in Startup Applications does not work either. Is there a way to permanently change to hiDPI mode so the OS doesn't have to change it every time I boot? Or change the default setting to hiDPI somehow?

I just got a 4k monitor to supplement my two 1080p monitors. However, I am having trouble getting the scaling working to everything looks good. The monitors are physically set up like this: ____ ____ | DP1|____________| DP2| |1080| 4k |1080| | |_____DP3____| | |____| |____| Looking online, it seems like using xrandr along with --scale and --panning to get everything scaled and lined up correctly. However, I am trying to follow what I've seen and can't get it working. The command I am trying is: xrandr --dpi 163 --fb 11520x6480 --output DP-1 --scale 1.5x1.5 --pos 0x240 \ --rotate right --panning 2880x1620 --output DP-2 --scale 1.5x1.5 --pos 4920x260 \ --rotate left --panning 2880x1620+6720+0 --output DP-3 --mode 3840x2160` When I execute the command, my 4k monitor looks fine, but the 2 1080p monitors seem to kind of mirror an area around the mouse cursor. With everything messed up like this, I am unable to open a terminal with the keyboard shortcut, so I have to reboot the system to get to a stable state. I really appreciate any help with this.