by the way, that method of modifying ~/.profile breaks its contents since it replaces _all_ occurences of that export entries.
This makes it impossible to share .profile files between different computers with different language settings, even if it contains case-instructions for the different computers. It even destroys the old settings, and loss of data is usually to be considered as a severe and important bug.
Automatically modifying user-written shell scripts is an absolute no-go and really broken by design. This design decision should have never been made.
There's lots of better files for doing that. Files in /etc/X11/Xsession.d read things like ~/.gnomerc or ~/.xsessionrc which would be much better (or even use a specific file for language settings), but under all circumstances keep fingers from ~/.profile.
Even worse, this affects the settings if someone is logging in through ssh or with other desktops.
This is not just bad design, this is really a bug.
by the way, that method of modifying ~/.profile breaks its contents since it replaces _all_ occurences of that export entries.
This makes it impossible to share .profile files between different computers with different language settings, even if it contains case-instructions for the different computers. It even destroys the old settings, and loss of data is usually to be considered as a severe and important bug.
Automatically modifying user-written shell scripts is an absolute no-go and really broken by design. This design decision should have never been made.
There's lots of better files for doing that. Files in /etc/X11/Xsession.d read things like ~/.gnomerc or ~/.xsessionrc which would be much better (or even use a specific file for language settings), but under all circumstances keep fingers from ~/.profile.
Even worse, this affects the settings if someone is logging in through ssh or with other desktops.
This is not just bad design, this is really a bug.
regards