Here is the current status and my (for the moment final, whatever this means) thoughts on the subject:
On April 29th, I realized upon waking up that clicking on the + sign (located to the left of all tabs) did not produce a new tab. As I have hundreds (sometimes possibly even more than a thousand) open tabs at any time, I thought the browser (Pale Moon) had somehow reached a memory limit. However, I could use the browser normally and even open new tabs by using the CTRL+T keyboard shortcut. This indicates a problem with the Tab Mix Plus plugin, rather than the browser itself. Indeed, just yesterday I realized that there was an update for the plugin waiting to be downloaded and installed - maybe this caused it to stop functioning correctly.
I shut down the browser normally without problems, but did not start it immediately. Instead I had a look if a new version was available, so I could install and use that one. In fact there was, and, due to other upgrades that were taking place and required my attention, it took me a few days to compile and install the new version.
That's when I saw that it was using a white, flat theme (turned out to be 'breeze' and not 'Adwaita', as I thought). My beloved CDE theme
was gone! I got mad. I thought PM had reverted back to GTK2 - it had not. It was functioning fine as always, displaying a GTK3 theme as always.
It was simply that something
had created a ~/.config/gtk-3.0/settings.ini
file with the contents:
Code: Select all
gtk-font-name=Noto Sans 10
and the browser was just obeying its precedence over my global /etc/gtk-3.0/settings.ini
My rants about GTK2 should probably be understood as rants against flat, all-white themes, like 'breeze', that I confuse with some similar GTK2 theme. Let's not start a flame war.
The question remains: did the browser (or the Tab Mix Plus plugin) automatically create the settings.ini
file upon shutdown? I can't find any mention of 'Breeze' in the code - although I thought I had found one in PORTAGE_TMPDIR before it was swept away.
Whatever the cause, the reader should be aware of this possibility and search at the right places for other culprits before stirring up so much dust as I did here.
Thanks to all for your help and KUTGW.