Bug 259802

Verified (yast2-2.14.5-10).

I do not understand the report. Which version did you test? 2.14.5 version line is on openSUSE 10.2, not 10.3 Alpha.

And what exactly happened? Were there any packages installed? 

Please attach /etc/sysconfig/language and y2logs.

It seems the correct packages are installed because when you logout your current (non-root) desktop user from whom you started YaST and relogin then all YaST modules appear in the selected language. Just restarting YaST alone doesn't change anything.

Looks like your desktop environment didn't propagate the new locale settings to the yast. What if you open xterm, check if the locale was changed and run /sbin/yast2 from xterm?

BTW, you didn't attached required files.

Created attachment 128411 [details]
/etc/sysconfig/language and y2logs

The locale of the user stays with the previous locale (until he relogins and you didn't modify the user's setting to have another locale of course).

The (user's) desktop environment should have no influence here at all IHMO, the yast control center and the other modules simply should read the language setting the same way the System/Language module does.

System/Language module reads the language setting from /etc/sysconfig/language, while YaST uses the environment variable.
Why do you think this should be the same? The standard and correct way is to get the info from locale, System/Language IMHO reads the file directly to work even in special cases like installation, or maybe there's some other historic reason for this.

The need to relogin so the locale is in correct state is common IMHO - KDE says so as well. It think there is nothing to change on YaST side.

> Why do you think this should be the same?

A language change should be reflected immediately/as soon as possible.
Different YaST modules shouldn't communicate with the user in different languages. 
The YaST modules should use the system/administrator's language, not the language of a random desktop user being logged in.

Hm. I believe the system locale was set correctly after first yast call (you can check it on your own). So the problem is that the second call of yast doesn't know correct system locale - but someone else must care about this, not yast.

For me it looks like a duplicate (or another part) of bug 222728.

*** This bug has been marked as a duplicate of bug 222728 ***

The same happens also on a GNOME desktop, so it's for sure not kdesu's fault.

No. But bug 222728 is not kdesu related as well, it's sudo related AFAIK.

Please read again: YaST starts with the locale that is read from environment. If this is wrong, don't blame YaST.

*** This bug has been marked as a duplicate of bug 222728 ***

It would be highly unprofessional, if a change of the system language would not affect the YaST modules as well. It contradicts usability issues like user expectations and task adequacy.
Jiri, if you can't fix the problem, than please tell us anyone else who we can address in this issue.
Thanks!

Just did the same test on openSUSE 10.2 and there restarting the YaST control center did switch the language of the control center and all started modules. 

So it's a regression since openSUSE 10.2.

Could you please tell me, _how_ did you restart YaST control center (10.2 and 10.3) and what are the locale settings of the process that does it?

(For the answer of second question, it could help to attach whole /var/log/YaST2/ directory).

A agree that this bug might be different but I still think it's sudo issue and not YaST. Please provide the needed info.

Any info?

I did start the YaST control center by clicking its entry in the respective start menus of GNOME and KDE. The user has

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"

while the system language was switched to German as test. And their are not more log files generated by language switching, and there are no others as I deleted the YaST2 log file before trying.

May I suggest you try it yourself first once before bombarding me with with NEEDINFOs?

This is the user locale (which will be changed after re-login). The system locale was changed correctly (check by 'su - -e locale') - this is what I checked on my system and I asked for your info so you could see it works correctly also on yours.

But when you run YaST using the KDE or GNOME menu, it launches it with kdesu/gnomesu. These commands are using sudo and actually do not call the process with the root's language environment variables. This is probably just the opposite case of the one solved in bug #222728.

But anyway - nothing for YaST to solve. Reassigning to sudo maintainer.

Sudo keeps and will keep these environment variables:
"LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS". I do not know how to help in fixing this issue.

Closing as WONTFIX.