Can someone tell me why when I log in as root and start Yast it looks fine
but when I log in as a user then start Yast and enter the root password Yast
has some text in a squiggly ( Arabic perhaps ) font.
You mean the text for things like software management, hardware, etc. is
actually not readable at all? I’ve never noticed that, but I would look
at your locale settings as your non-root user. Also, how specifically
(show commands with the code (#) tag button in the web UI) are you
becoming root? I have never noticed Yast magically prompt for a root
password, so I assume you are using sudo. If so, try ‘sudo -i’ first, or
SSH in as root, or use ‘su -’, and see if those have the same issue.
Otherwise, locale stuff should show from the following command (executed
both as non-root and as ‘root’ to see differences.
env | grep LC
–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Well, when you start YaST from the menu of a desktop session (GUI, e.g. KDE or Gnome), it does open a window to ask for the root password to begin with. That has been so for ages. I do not know if you would ask this magic, bit it is simply programmed as such.
I see that too. Strange as the Arabic entries are either the category heading or the category explanation - but not both. I did check my language settings in yast and these just show GB English.
Well, the corresponding translations (package “desktop-translations”) are broken it seems.
en_GB/update-desktopfiles-yast.po contains e.g.:
#: /usr/share/applications/YaST2/users.desktop
msgctxt "GenericName(users.desktop)"
msgid "Add, Edit, Delete Users or User Groups"
msgstr "إضافة مستخدمين أو مجموعات مسخدمين أو تحرير بياناتهم أو حذفها"
xxx.po is the translation “source code”, it is “compiled” into a .mo file when the package is built and the binary package (desktop-translations.rpm) contains those binary .mo files.
The .po files (in plaintext) are only contained in the desktop-translations.src.rpm (or you can get them on OBS).
Tumbleweed x86_64 is being referred too?
Sure, that was taken from the current Tumbleweed package (noarch though, not x86_64… ).
I just had a look, and the package in 15.0 is indeed broken as well. Should be fixed with the next update there too (changes have to be in Tumbleweed first, so it takes a while to propagate them to Leap 15)
But note that apparently only en_GB is affected.
The current (fixed) version in Tumbleweed is 84.87.20180308.779a35a-1.1.
Yours must come from some additional repo… (x11:common:Factory, I guess )
NB
different rpm is needed for 32bit os’s
No.
As I already wrote, this is a noarch package.
I.e. there is only one package for 32bit and 64bit.
Aaah. I also saw others were experiencing that problem in the mailing lists since I posted, and I was almost about to ask why my system was “different”.
Thanks. I am using en_US and so that is now explained.