Bug 8861 - GDM and gnome-screensaver authentication strings are not translated
Summary: GDM and gnome-screensaver authentication strings are not translated
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-28 01:24 CET by Davy Defaud
Modified: 2017-02-08 00:41 CET (History)
1 user (show)

See Also:
Source RPM: gnome-screensaver-3.6.1-2.mga3.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Davy Defaud 2013-01-28 01:24:17 CET 
"Password: ", "Authentication failure", etc.
These strings are not translated, I suspect these strings to be in PAM. This kind of problem should be familiar to "pterjan"...
Comment 1 Nic Baxter 2015-02-25 05:05:00 CET 
still valid?

CC: (none) => nic

Comment 2 Davy Defaud 2015-02-25 12:36:23 CET 
Yes sir, still there.
Comment 3 Nic Baxter 2015-03-29 04:02:28 CEST 
Nudge
Davy Defaud 2015-06-22 21:56:19 CEST

Summary: gnome-screensaver authentication dialogs are not translated => GDM and gnome-screensaver authentication strings are not translated

Comment 4 Davy Defaud 2015-06-22 22:00:41 CEST 
This bug is affecting GDM also. Although the form is translated, the (yellow) strings returned by the authentication attempts are not translated. Could be related to setting the locale for PAM...
Comment 5 Pascal Terjan 2015-06-22 22:17:18 CEST 
I believe the (very old) fix was http://svnweb.mageia.org/packages/cauldron/tcb/current/SOURCES/tcb-1.0.3-i18n.patch?revision=5880&view=markup in pam_tcb.

Are we still using pam_tcb?
Comment 6 Davy Defaud 2015-06-22 22:39:51 CEST 
You ask me?
Seems so :
$ rpm -qa | grep pam
pam-1.1.8-10.mga5
lib64pam0-1.1.8-10.mga5
lib64pam-devel-1.1.8-10.mga5
lib64pam_userpass1-1.0.2-10.mga5
pam_tcb-1.1-5.mga5
Comment 7 Davy Defaud 2017-02-08 00:41:40 CET 
Seems to be fixed in MGA6

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.