Bug 14774 - Locale not being set
Summary: Locale not being set
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-09-16 04:55 UTC by Alexandre Faria
Modified: 2014-01-18 15:28 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alexandre Faria 2013-09-16 04:55:24 UTC
Locale is not being set.

public class A
        public static void Main(string[] args)

Expected behaviour:

Current behaviour

Mono version:
Mono JIT compiler version 3.2.3 (master/bb2bc9a Dom Set 15 10:40:56 WEST 2013)
Copyright (C) 2002-2012 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          yes(3.3svn-mono)
	GC:            sgen
Comment 1 Rodrigo Kumpera 2014-01-17 14:49:34 UTC
Please provide test instructions as running your sample does return the right locale for me.
Comment 2 Alexandre Faria 2014-01-18 15:28:57 UTC
I just updated mono from git, and in the latest git I can confirm its working again.
So its no longer a bug.