trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: August 2017

Re: [trinity-users] tiny fonts problem revisited

From: Felmon Davis <davisf@...>
Date: Sat, 5 Aug 2017 02:42:49 -0400 (EDT)
On Sat, 5 Aug 2017, Felix Miata wrote:

> Felmon Davis composed on 2017-08-05 00:37 (UTC-0400):
>
>> Felix Miata wrote:
>
>>>>> Save http://fm.no-ip.com/Share/Linux/xorg.conf-minimal-EDID-workaround to use as
>>>>> an /etc/X11/xorg.conf template. Create in it an uncommented DisplaySize line.
>>>>> Using half the values reported above that produce 96x96 /should/ produce 192x192
>>>>> as a place to start your experiments:
>
>>>>> 	DisplaySize	423 213 # 192 DPI @ 3200x1800
>
>>>> I tried this value and the fonts were grotesquely large on the login
>
>>> Not a surprise to me.
>
>>>> page but once logged in I saw no difference.
>
>>> Shock. :-( What did/do "xrdb --query | grep dpi" and "xdpyinfo | egrep
>>> 'dimen|ution'" report? Do they match what is reported if you load
>>> http://fm.no-ip.com/Auth/dpi-screen-window.html
>>> in a Gecko browser (Firefox, SeaMonkey, others) or Konqueror w/ KHTML, but not
>>> Chrom* or Opera.
>
>> I've made a little progress but let me give you some results:
>
>> xrdb yields dpi = 120
>
> That's the expected result of using TDE Control Center to force 120 DPI (through
> Xft.dpi).
>
>> xdpyinfo yields:
>> 3200x1800 pixels (270x216 millimeters)
> Peculiar. 270x216 is a 1.25/1 ratio, 5/4, normally only seen with 1280x1024
> resolution displays. 216 is a tad taller than that of a 1920x1080 17" screen.
>
>> resolution 301x212 dots per inch
>
> A bizarre ratio: 1.42:1.
>
>> however:
>
>> your website yields what seem to me correct values except for dpi. it
>
> DPI and default font px size reporting require you let the scripts run.

sorry, I missed this - where are the scripts?

I won't comment on the rest of your email until later today or 
tomorrow but I wanted to comment on my set-up, which is probably 
somewhat messed up.

I can log into Mint and into Debian Desktop Environment and also into 
KDE4 Plasma. I'm looking at the latter now and stuff like Pan and 
Firefox are tiny and have some kind of theme problem.

Windows 10 looks and behaves ok; it is hard for me to find the display 
information beyond the elementary stuff.

frankly, what I think I should do is start over again. I have too much 
playing in the config backyard. I have two partitions to play with. my 
unease about re-installing is due solely to my unfamiliarity with the 
mysteries of UEFI. (I need to keep Windows 10 for now; I'm researching 
the possibility of installing Windows 7 instead though.)

I'll make decisions later today - either try to solve problems or 
scratch and re-do.

I shouldn't forget to thank you for the very good advice!

f.

>
>> seems not to capture the dpi values at all but maybe I misinterpret:
>> <https://drive.google.com/file/d/0B--R0Wp8z2MkaTVtNmZ0TnRPNjg/view?usp=sharing>
>
> Interesting. Screen totals are correctly reported. Available and Viewport show
> exactly the values expected for a somewhat common screen size of 2560x1440. I
> have to wonder how you managed to get a Konq window to open at that size on a
> 3200x1800 screen. Odds must be astronomical that it happened by accident.
>
>> I've commented out HorizSync and VertRefresh though I did run
>
>>> 	hwinfo --monitor | grep -A6 'river Inf'
>>
>> and it says "Size: 293x165 mm"
>
>
> That's about as close as Xorg ever gets to accurate. My calculator says a 13.3"
> screen should measure 294.44 by 165.62. Is that the result of using DisplaySize
> in xorg.conf set to manufacturer's screen size specifications?
>
>> so there's some data (or there're some data) and a couple of
>> incongruities.
>
>> I'll stop here and talk about the progress I alluded to earlier.
>
>> I think I have kde apps in ok shape by fooling with fonts and
>> setting fonts to
>
>> System Settings
>> 120 dpi
>
>> what doesn't work is management of LibreOffice, Firefox, the intro
>> display for Trinity Control Center and various apps which I think are
>> GTK (and then there's that grotesquely large login page).
>
>
> I don't see exegnu on DistroWatch, so without it installed, or more information
> on its web site than I've seen, I don't know if GTK3 is installed or what
> toolkit your LO or FF packages are built using. It looks like GTK apps are just
> not capable of reasonably responding to a display of such high DPI on exegnu, or
> maybe without being run in Gnome or Mate or other GTK DE or absent some unusual
> manual gtk configuration or additional package support. Your inability to find
> any gtk*3* packages installed is somewhat puzzling. A distro released only late
> last year ought to be providing at least basic GTK3 support.
>
>> I'll be installing Apache Office which I prefer but suspect it will
>> have the same problem as LO.
>
>> it seems to me I have to fuss with GTK.
>
> Maybe searching in OO or LO forums for HiDPI discussions would prove fruitful.
>
> Maybe we need to have a look at your xorg.conf if you're still using it.
>
> At least let's see Xorg.0.log generated by the best configuration you've come up
> with so far, with or without an xorg.conf.
>
>> or I may follow your advice below and alter the display mode. that's > for tomorrow or the next day.
>
> ...
>
>> I may return the laptop.
>
> Assuming running at lower than native resolution won't be acceptable to you,
> that sounds like a good idea, unless you have really really good young eyes and
> better tolerance for things tiny than the existence of this thread suggests. It
> seems something in some software component, or maybe more than one, is just too
> broken for working on a 276 physical DPI screen.
>
> Is Windows still on it? What are its display/screen and font settings?
>

-- 
Felmon Davis

We are what we pretend to be.
                 -- Kurt Vonnegut, Jr.