Hi all,
I found that TCC does overwrite ~/.bashrc. From my level of proficiency
that is a no-go and should not happen at all, especially not without
informing the user.
What happens:
All utf8 characters in .bashrc get replaced with strange characters when
GTK2 Fonts are changed from the TCC GUI.
Reproduce:
I can reproduce this behaviour on my system by simply changing the
configuration in
TCC -> Appearance and Themes -> GTK Style and Fonts -> GTK2 Fonts:
from "Use my TDE fonts" to "Use another font" or the other way
around.
I confirmed this misbehaviour within a new, pristine user account with a
default debian .bashrc where I inserted three lines with utf8
characters:
$ diff utf8.bashrc utf8-mangled.bashrc
--- utf8.bashrc 2022-01-18 10:21:23.700348782 +0100
+++ utf8-mangled.bashrc 2022-01-18 10:31:59.659323727 +0100
@@ -3,11 +3,11 @@
# for examples
-# Test Umlaut a: >ä<
+# Test Umlaut a: >ä<
-# Test long hyphen: >–<
+# Test long hyphen: >â<
-# Test Euro currency symbol: >€<
+# Test Euro currency symbol: >â¬<
# If not running interactively, don't do anything
case $- in
Additional information:
When the users .bashrc is owned by root then in ~/.xsession-errors of
the user is reported this:
[2022/01/18 10:24:59.374] TQFile::writeBlock: File (/home/user/.bashrc) not open
(where "user" is the actual user name)
Can anyone confirm this? I would then bugreport this phenomenon.
Cheers, Stefan
PS: I have been seeing this for years and never had a clue as to what
causes it, phew! Now I caught it by accident just by observing the
almost concurrent incidence of the phenomenon and changing GTK2 fonts
in TCC.