greetings, folks,
through inadvertence I wiped out my Linux partition. I restored my files but I didn't have a backup of the system so I installed a new version of q40s (which runs a version of TDE). I use a prior version on another laptop I don't have access to right now.
then began the misadventures with font sizes in this HiDPI laptop; I got some help from the list (thanks!) last yr with such problems on a similar laptop.
I've wrestled them to the ground for the most part but the windows labelled as "TDE Control Module" have teensy font size. where do I find the file that regulates their appearance?
thanks for the advice.
fjd
Anno domini 13:45:54 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
greetings, folks,
through inadvertence I wiped out my Linux partition. I restored my files but I didn't have a backup of the system so I installed a new version of q40s (which runs a version of TDE). I use a prior version on another laptop I don't have access to right now.
then began the misadventures with font sizes in this HiDPI laptop; I got some help from the list (thanks!) last yr with such problems on a similar laptop.
I've wrestled them to the ground for the most part but the windows labelled as "TDE Control Module" have teensy font size. where do I find the file that regulates their appearance?
thanks for the advice.
fjd
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
Or change the global fonts in ~/.trinity/share/config/kdeglobals - but be prepared to go over the other config files in ~/.trinity/share/config/ , too, there are a lot of font configs to be found. Just do "fgrep -i font ~/.trinity/share/config/" :)
Nik
On Thu, 12 Dec 2019, Dr. Nikolaus Klepp wrote:
Anno domini 13:45:54 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
greetings, folks,
through inadvertence I wiped out my Linux partition. I restored my files but I didn't have a backup of the system so I installed a new version of q40s (which runs a version of TDE). I use a prior version on another laptop I don't have access to right now.
then began the misadventures with font sizes in this HiDPI laptop; I got some help from the list (thanks!) last yr with such problems on a similar laptop.
I've wrestled them to the ground for the most part but the windows labelled as "TDE Control Module" have teensy font size. where do I find the file that regulates their appearance?
thanks for the advice.
fjd
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Or change the global fonts in ~/.trinity/share/config/kdeglobals -
yeah, I have everything set in kdeglobals to what I consider reasonable values.
but be prepared to go over the other config files in ~/.trinity/share/config/ , too, there are a lot of font configs to be found. Just do "fgrep -i font ~/.trinity/share/config/" :)
alright, I see some values which might be pertinent. I've changed a couple and will re-start the session at the next convenient opportunity.
(note I have closed the session and I have re-booted several times since a couple of days for these and other reasons.)
fjd
Anno domini 14:35:02 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
On Thu, 12 Dec 2019, Dr. Nikolaus Klepp wrote:
Anno domini 13:45:54 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
greetings, folks,
through inadvertence I wiped out my Linux partition. I restored my files but I didn't have a backup of the system so I installed a new version of q40s (which runs a version of TDE). I use a prior version on another laptop I don't have access to right now.
then began the misadventures with font sizes in this HiDPI laptop; I got some help from the list (thanks!) last yr with such problems on a similar laptop.
I've wrestled them to the ground for the most part but the windows labelled as "TDE Control Module" have teensy font size. where do I find the file that regulates their appearance?
thanks for the advice.
fjd
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
Or change the global fonts in ~/.trinity/share/config/kdeglobals -
yeah, I have everything set in kdeglobals to what I consider reasonable values.
but be prepared to go over the other config files in ~/.trinity/share/config/ , too, there are a lot of font configs to be found. Just do "fgrep -i font ~/.trinity/share/config/" :)
alright, I see some values which might be pertinent. I've changed a couple and will re-start the session at the next convenient opportunity.
(note I have closed the session and I have re-booted several times since a couple of days for these and other reasons.)
fjd
On Thu, 12 Dec 2019, Dr. Nikolaus Klepp wrote:
Anno domini 14:35:02 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
On Thu, 12 Dec 2019, Dr. Nikolaus Klepp wrote:
Anno domini 13:45:54 Thu, 12 Dec 2019 +0100 (CET) Felmon Davis scripsit:
greetings, folks,
through inadvertence I wiped out my Linux partition. I restored my files but I didn't have a backup of the system so I installed a new version of q40s (which runs a version of TDE). I use a prior version on another laptop I don't have access to right now.
then began the misadventures with font sizes in this HiDPI laptop; I got some help from the list (thanks!) last yr with such problems on a similar laptop.
I've wrestled them to the ground for the most part but the windows labelled as "TDE Control Module" have teensy font size. where do I find the file that regulates their appearance?
thanks for the advice.
fjd
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I picked that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
fjd
Or change the global fonts in ~/.trinity/share/config/kdeglobals -
yeah, I have everything set in kdeglobals to what I consider reasonable values.
but be prepared to go over the other config files in ~/.trinity/share/config/ , too, there are a lot of font configs to be found. Just do "fgrep -i font ~/.trinity/share/config/" :)
alright, I see some values which might be pertinent. I've changed a couple and will re-start the session at the next convenient opportunity.
(note I have closed the session and I have re-booted several times since a couple of days for these and other reasons.)
fjd
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I picked that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's apestilence on it's own.
On Thursday 12 December 2019 09:43:14 Dr. Nikolaus Klepp wrote:
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I picked that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's a pestilence on it's own.
I am glad to see that someone else is hammering on gtk3 Nik. gtk2 was 1000% more usefull. gtk3 must be a committee design. lol.
Cheers, Gene Heskett
On Thu, 12 Dec 2019, Gene Heskett wrote:
On Thursday 12 December 2019 09:43:14 Dr. Nikolaus Klepp wrote:
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I
picked
that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's a pestilence on it's own.
I am glad to see that someone else is hammering on gtk3 Nik. gtk2 was 1000% more usefull. gtk3 must be a committee design. lol.
it's maddening.
the command "fgrep -iR font ~/.trinity/share/config/*" was very helpful. at one point it helped solve the issue I started with, viz. teensy fonts in "TDE Control Module" windows.
then, out of the blue, Firefox-bin (v. 71.0) looked ugly - huge fonts in the tabs - and pan newsreader equally grotesque. don't have careful enough notes to infer if I did something to trigger it.
not the most welcome reason for procratinating but it is too distracting for work (that's my excuse anyway) so I fooled around and upping DPI to 120 has fixed a lot of it though not sure it will stick the next time I boot out and up.
I still can't quite get Firefox to behave; I'm essentially running Firefox-esr. Firefor 71.0 just ignores userChrome.css and I cannot find the magic gtk spell for it.
but for a deadline I'm tempted to wipe q4os and just do a Debian (or Devuan) with TDE but that may be misplacing the blame.
fjd
Felmon Davis composed on 2019-12-13 03:08 (UTC+0100):
I still can't quite get Firefox to behave; I'm essentially running Firefox-esr. Firefor 71.0 just ignores userChrome.css and I cannot find the magic gtk spell for it.
Try tqtconfig to set qt font size for KControl applets. In Buster it comes from tqt3-qtconfig.
The real magic is to not use MozillaFirefox. Instead, use firefox-esr. Its annoying regressive changes occur less often than once per year instead of every 6-10 weeks. Another option is to use palemoon (newmoon in some distros), which is a fork of Firefox created back around FF28 or thereabouts.
If your distro doesn't offer esr even via a ppa, you can uninstall its package and use the version provided by mozilla.org: http://ftp.mozilla.org/pub/firefox/releases/68.3.0esr/ Using the mozilla.org version allows the possibility to more easily exercise control over when its updates occur.
If you use a fresh virgin profile, does the problem remain?
What does
xrdb -query | grep dpi
report? This is the mechanism Gnome/GTK observes for controlling DPI. Kcontrol uses it, but allows only the options 96 and 120. If you leave it at default (not controlled), then you can set it to anything you like via Xft.dpi in ~/.Xresources or ~/.Xdefaults. GTK3 since version 3.17 forces it to 96 instead of leaving it null unless something forces it to something else, or you are using openSUSE, which reverted upstream's abusive imposition. I haven't checked. There could be other distros that have also reverted it.
Instead of literally creating a new profile to test with if you find it too intimidating, you can back up the profile directory, then empty it before restarting Firefox. After the test, delete the content again, then restore from the backup. A read of ~/.mozilla/firefox/profiles.ini will tell you the name of the directory whose content to delete, the actual profilename. Don't delete the directory, only its (entire) content. Alternatively, create another directory, then substitute that directory for the directory name in profiles.ini for making the test.
Anno domini 2019 Fri, 13 Dec 07:43:23 +0100 deloptes scripsit:
Felix Miata wrote:
The real magic is to not use MozillaFirefox. Instead, use firefox-esr.
I definitely disagree with this - whenever I tried firefox-esr, there has been only troubles.
:) My latest trouble after an update some weeks ago is that firefox-esr has frozen all extension settings. This i quite anoying,as it includes per-website-zoomfactor, per-website noscript settings etc. Only way to fix it might be a new profile, but ...
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Dr. Nikolaus Klepp wrote:
:) My latest trouble after an update some weeks ago is that firefox-esr :has frozen all extension settings. This i quite anoying,as it includes :per-website-zoomfactor, per-website noscript settings etc. Only way to :fix it might be a new profile, but ...
I think another version of FF - same experience on one friends PC - removed ESR, installed FFv71 and all the old stuff was back again. Perhaps it will work for you as well
regards
On 12/12/2019 10:04 PM, Felix Miata wrote:
If your distro doesn't offer esr even via a ppa, you can uninstall its package and use the version provided by mozilla.org: http://ftp.mozilla.org/pub/firefox/releases/68.3.0esr/ Using the mozilla.org version allows the possibility to more easily exercise control over when its updates occur.
+2 for Felix here...
On Thu, 12 Dec 2019, Felix Miata wrote:
Felmon Davis composed on 2019-12-13 03:08 (UTC+0100):
I still can't quite get Firefox to behave; I'm essentially running Firefox-esr. Firefor 71.0 just ignores userChrome.css and I cannot find the magic gtk spell for it.
Try tqtconfig to set qt font size for KControl applets. In Buster it comes from tqt3-qtconfig.
first I have to note my earlier attempt did not succeed in enlarging the fonts on the "TDE Control Module" and similar windows - I was mistaken I think.
yesterday I downloaded tqtconfig but I didn't see any results. (ironically it itself is in a teensy font size. I may be missing something so I'll play with it again.
The real magic is to not use MozillaFirefox. Instead, use firefox-esr. Its annoying regressive changes occur less often than once per year instead of every 6-10 weeks. Another option is to use palemoon (newmoon in some distros), which is a fork of Firefox created back around FF28 or thereabouts.
I see subsequent discussion about this suggestion. I have both esr and 71.0 and esr plays fine with userChrome.css but 71.0 is not responsive.
*however* I have domesticated FF 71.0 somehow, we'll see if it lasts through the next session log-out or re-boot. I don't know how. I get the impression that setting DPI to 120 and then *back* to 96 may have brought it to its senses. this is speculative; I'll try to make more observations.
If your distro doesn't offer esr even via a ppa, you can uninstall its package and use the version provided by mozilla.org: http://ftp.mozilla.org/pub/firefox/releases/68.3.0esr/ Using the mozilla.org version allows the possibility to more easily exercise control over when its updates occur.
If you use a fresh virgin profile, does the problem remain?
What does
xrdb -query | grep dpi
right now DPI is 96. I'll try the profile experiment a bit later.
through foolin' around I now how several profiles. that's no problem, I'll sort it out.
strangely FF 71.0 will complain if I try to force certain profiles (esr ones) and refuse to start.
report? This is the mechanism Gnome/GTK observes for controlling DPI. Kcontrol uses it, but allows only the options 96 and 120. If you leave it at default (not controlled), then you can set it to anything you like via Xft.dpi in ~/.Xresources or ~/.Xdefaults. GTK3 since version 3.17 forces it to 96 instead of leaving it null unless something forces it to something else, or you are using openSUSE, which reverted upstream's abusive imposition. I haven't checked. There could be other distros that have also reverted it.
good information.
not openSUSE but something called q4os.
Instead of literally creating a new profile to test with if you find it too intimidating, you can back up the profile directory, then empty it before restarting Firefox. After the test, delete the content again, then restore from the backup. A read of ~/.mozilla/firefox/profiles.ini will tell you the name of the directory whose content to delete, the actual profilename. Don't delete the directory, only its (entire) content. Alternatively, create another directory, then substitute that directory for the directory name in profiles.ini for making the test.
yeah, like I said, I got plenty of profiles now!
so where I stand is:
(a) in general things are kind of satisfactory but I'm not sure how stable;
(b) the teensy font problem on the TDE Control windows is still there;
(c) I don't think tqtconfig worked but I should try again;
(d) the situation of Firefox-esr is fine; Firefox 71.0 is ok but not sure it will survive a reboot or re-start of the session.
thank you for pitching in; you helped me before with this kind of problem. I learned a bit.
fjd
Anno domini 03:08:19 Fri, 13 Dec 2019 +0100 (CET) Felmon Davis scripsit:
On Thu, 12 Dec 2019, Gene Heskett wrote:
On Thursday 12 December 2019 09:43:14 Dr. Nikolaus Klepp wrote:
> First try to increase the DPI settings. If it works, you are > done. (~/.trinity/share/config/startupconfig: > kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I
picked
that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's a pestilence on it's own.
I am glad to see that someone else is hammering on gtk3 Nik. gtk2 was 1000% more usefull. gtk3 must be a committee design. lol.
it's maddening.
the command "fgrep -iR font ~/.trinity/share/config/*" was very helpful. at one point it helped solve the issue I started with, viz. teensy fonts in "TDE Control Module" windows.
then, out of the blue, Firefox-bin (v. 71.0) looked ugly - huge fonts in the tabs - and pan newsreader equally grotesque. don't have careful enough notes to infer if I did something to trigger it.
not the most welcome reason for procratinating but it is too distracting for work (that's my excuse anyway) so I fooled around and upping DPI to 120 has fixed a lot of it though not sure it will stick the next time I boot out and up.
I still can't quite get Firefox to behave; I'm essentially running Firefox-esr. Firefor 71.0 just ignores userChrome.css and I cannot find the magic gtk spell for it.
but for a deadline I'm tempted to wipe q4os and just do a Debian (or Devuan) with TDE but that may be misplacing the blame.
fjd
My notes say this about high DPI mode & Firefox (it sets a kind of pixe-to pixel zoom factor): about:config --> layout.css.devPixelsPerPx=2
Nik
On Fri, 13 Dec 2019, Dr. Nikolaus Klepp wrote:
Anno domini 03:08:19 Fri, 13 Dec 2019 +0100 (CET) Felmon Davis scripsit:
I still can't quite get Firefox to behave; I'm essentially running Firefox-esr. Firefor 71.0 just ignores userChrome.css and I cannot find the magic gtk spell for it.
My notes say this about high DPI mode & Firefox (it sets a kind of pixe-to pixel zoom factor): about:config --> layout.css.devPixelsPerPx=2
thanks; I discovered this. very, very useful!
Anno domini 2019 Thu, 12 Dec 20:11:25 -0500 Gene Heskett scripsit:
On Thursday 12 December 2019 09:43:14 Dr. Nikolaus Klepp wrote:
First try to increase the DPI settings. If it works, you are done. (~/.trinity/share/config/startupconfig: kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I picked that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's a pestilence on it's own.
I am glad to see that someone else is hammering on gtk3 Nik. gtk2 was 1000% more usefull. gtk3 must be a committee design. lol.
Hi Gene! My 4 GTK applications left are "terminator" (it's 0.97, gtk2 version, on hold, as 1.xx is gtk3 and utterly broken), GIMP (can't do much about it) and DrRacket (which has a use-gtk2-switch). "Geany" was good, as long as it was GTK2, the GTK3 version is broken badly, and firefox (well ...). Guess some GNOMEs get good money for breaking things in a creative way.
Nik
Cheers, Gene Heskett
On Friday 13 December 2019 02:10:54 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Thu, 12 Dec 20:11:25 -0500
Gene Heskett scripsit:
On Thursday 12 December 2019 09:43:14 Dr. Nikolaus Klepp wrote:
> First try to increase the DPI settings. If it works, you are > done. (~/.trinity/share/config/startupconfig: > kcmfonts_general_forcefontdpi="96")
yeah, that's already set.
Out of couriosity: what value did you put there and did it change "something"?
it's been 96.
I have tried something else (I believe '120', not sure why I picked that) and it improved some things and made other things worse - had me jumping from config file to config file. somehow I've achieved equilibrium with 96.
and Firefox is a demon! ended up writing userChrome.css rules but strangely Firefox-esr (68.3.0esr) seems to honor them but Firefox 71.0 seems to ignore them. (I did the magic of trying to force it to read the file, etc.)
Firefox uses GTK3, and that's a pestilence on it's own.
I am glad to see that someone else is hammering on gtk3 Nik. gtk2 was 1000% more usefull. gtk3 must be a committee design. lol.
Hi Gene! My 4 GTK applications left are "terminator" (it's 0.97, gtk2 version, on hold, as 1.xx is gtk3 and utterly broken), GIMP (can't do much about it) and DrRacket (which has a use-gtk2-switch). "Geany" was good, as long as it was GTK2, the GTK3 version is broken badly, and firefox (well ...). Guess some GNOMEs get good money for breaking things in a creative way.
Nik
geany 1.29 doesn't say. But its working well here. Thanks $DEITY for a decent editor but this is still a stretch based linuxcnc install in amd64 flavor. Now running a 9nth gen i5 at 3.7 GHZ. Highest temp reported is 31C. Stay away from gedit, its a CF you WILL regret installing. It plays 52 pickup with your text files contents, bad dog, don't open the biscuits. And its working well on the rpi4, which is a raspbian 10.2 buster install in armhf flavor.
Cheers, Gene Heskett
Cheers, Gene Heskett
looks like OpenOffice is also affected which is bad news right now.
On Fri, 13 Dec 2019, Marvin Jones via trinity-users wrote:
On Fri, 13 Dec 2019, Felmon Davis wrote:
looks like OpenOffice is also affected which is bad news right now.
For sure!! .. with that deadline to get the Christmas letter done. :-)
or comments for an upcoming meeting....
Felmon Davis wrote:
looks like OpenOffice is also affected which is bad news right now.
Why would you install something without a need - just for the sake of the upgrade? I use Apache Open Office which is now 4.1.3 and works rock solid.
On Fri, 13 Dec 2019, deloptes wrote:
Felmon Davis wrote:
looks like OpenOffice is also affected which is bad news right now.
Why would you install something without a need - just for the sake of the upgrade? I use Apache Open Office which is now 4.1.3 and works rock solid.
there's a misunderstanding here somewhere.... I didn't install anything just for the sake of an upgrade; OpenOffice is one of the first bits of software I install since it's my main work tool and has been running here since before I accidentally wiped the partition. in fact, I copy over my old templates whenever I have to reinstall it.
sorry for causing confusion.
f.
-
David C. Rankin -
deloptes -
Dr. Nikolaus Klepp -
Felix Miata -
Felmon Davis -
Gene Heskett -
Marvin Jones via trinity-users