Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Run xdpyinfo | grep resolution to find out what resolution your X server actually has, and use that instead of 96. Commented Jun 5, 2015 at 17:40
  • @lcd047 Doesn't that just return the resolution it's running with? What extra information does it provide? I don't think that actually implies anything about what the "correct" resolution should be. Commented Jun 5, 2015 at 18:09
  • 1
    You're supposed to run xdpyinfo in a terminal, not in vnc. If your X server thinks it's running at, say, 115 DPI, and you're forcing vnc to run at 96 DPI, you'll have fuzzy fonts. This is especially visible on LCD screens. Commented Jun 5, 2015 at 18:17
  • @lcd047 It appears that xdpyinfo tries to use the DISPLAY variable unless you specify -display in the command. My local display, :0, is at 96 dpi, but I expect that's because that's the connected-monitor's native res. (It's not a great monitor.) The vnc server display is also at 96 dpi--is this not determined by the command used to start the server, though? Commented Jun 5, 2015 at 18:33