Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 250710 - SLiM doesn't acknowledge Locale settings
Summary: SLiM doesn't acknowledge Locale settings
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Jeremy Olexa (darkside) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-12 16:03 UTC by Michael Sawczuk
Modified: 2009-01-09 18:46 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge-info.txt,3.20 KB, text/plain)
2008-12-12 16:05 UTC, Michael Sawczuk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Sawczuk 2008-12-12 16:03:34 UTC
My system has been configured with the locale of en_GB.utf8 as per the gentoo localisation guide, when I login via tty and do locale all the values are en_GB.utf8 which is correct, however when I login via SLiM and do locale all the values are POSIX, so it seems SLiM ignores the locale values or re-assigns them to POSIX.

Reproducible: Always

Steps to Reproduce:
1. Set locale to en_GB (not tried under en_US)
2. Login via SLiM
3. Run the command locale, values will be set to POSIX

Actual Results:  
System locale settings are set to POSIX

Expected Results:  
Locale should be set to what is system wide, in my case en_GB

I've tried this on two gentoo systems (both AMD64), both exhibit the same problem.
Comment 1 Michael Sawczuk 2008-12-12 16:05:24 UTC
Created attachment 175112 [details]
emerge --info
Comment 2 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-12-12 17:25:40 UTC
hm, fun. I'll see if upstream has any clues.
Comment 3 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-12-31 04:42:33 UTC
upstream is pretty elusive. Do you have any spare time to revert to 1.3.0 and see if this is a regression or not? Maybe we can find something in the code if so.
Comment 4 Michael Sawczuk 2009-01-09 18:46:26 UTC
Hi,
I rolled back and decided to wipe my config file with update-etc, I must of had an invalid config setting somewhere as it is now working correctly.

Thanks