From owner-freebsd-i18n@FreeBSD.ORG Wed Dec 29 21:53:28 2010 Return-Path: Delivered-To: freebsd-i18n@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5146F1065670 for ; Wed, 29 Dec 2010 21:53:28 +0000 (UTC) (envelope-from armin@frozen-zone.org) Received: from mailbackup.inode.at (mailbackup.inode.at [213.229.60.24]) by mx1.freebsd.org (Postfix) with ESMTP id D49BF8FC08 for ; Wed, 29 Dec 2010 21:53:27 +0000 (UTC) Received: from [62.99.145.5] (port=52412 helo=mx.inode.at) by mailbackup.inode.at with esmtp (Exim 4.72) (envelope-from ) id 1PY3iq-0001iF-DJ for freebsd-i18n@freebsd.org; Wed, 29 Dec 2010 22:38:16 +0100 Received: from [84.119.26.126] (port=16176 helo=fz-sub1.local) by smartmx-05.inode.at with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PY3io-0000QY-6c; Wed, 29 Dec 2010 22:38:14 +0100 Message-ID: <4D1BAA3D.1040203@frozen-zone.org> Date: Wed, 29 Dec 2010 22:38:05 +0100 From: Armin Pirkovitsch User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20101212 Thunderbird/3.1.7 MIME-Version: 1.0 To: Grzegorz Blach , freebsd-i18n@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: locale::facet::_S_create_c_locale name not valid [ was: Miro crash on startup on FreeBSD 8.2 amd64 ] X-BeenThere: freebsd-i18n@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD Internationalization Effort List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2010 21:53:28 -0000 Hi! @i18n: Has any of you ever seen the problem below and knows a possible solution to it? @Grzegorz: I can't really reproduce the problem locally - however it sounds to me as if the trouble goes deeper than miro (especially since miro is written in python and the error looks like a C++ error to me). You could try to unset LANGUAGE, LC_ALL, LC_MESSAGES and LANG and see if that changes anything. However you might get more information from the i18n@ guys and girls concerning that problem since I have no experience with localization. Cheers, Armin PS.: please CC me in the replies to the list since I have no subscription to it and I would be quiet interested in a possible solution. On 12/29/10 19:39, Grzegorz Blach wrote: > Hi, > > When I want start Miro on my FreeBSD 8.2-RC1 amd64, > I get message: > > 2010-12-29 19:36:43,874 INFO Starting up Miro > 2010-12-29 19:36:43,875 INFO Version: 3.5.1 > 2010-12-29 19:36:43,876 INFO Revision: > ssh://ben@git.participatoryculture.org:2191/var/git/miro - e5e3cabb > 2010-12-29 19:36:43,877 INFO Builder: magik@silver.nine > 2010-12-29 19:36:43,877 INFO Build Time: 1293548208.65 > 2010-12-29 19:36:43,877 INFO Reading HTTP Password list > 2010-12-29 19:36:43,878 INFO Starting libCURL thread > 2010-12-29 19:36:43,879 INFO Starting event loop thread > 2010-12-29 19:36:43,880 INFO Restoring database... > 2010-12-29 19:36:43,881 INFO Sqlite3 version: 3.7.4 > 2010-12-29 19:36:43,882 INFO Pysqlite version: 2.4.1 > 2010-12-29 19:36:43,882 INFO opening database /home/magik/.miro/sqlitedb > 2010-12-29 19:36:43,885 INFO Linux version: FreeBSD 8.2-PRERELEASE amd64 > 2010-12-29 19:36:43,886 INFO Python version: 2.6.6 (r266:84292, > Nov 27 2010, 17:09:47) > [GCC 4.2.1 20070719 [FreeBSD]] > 2010-12-29 19:36:43,886 INFO Gtk+ version: (2, 22, 1) > 2010-12-29 19:36:43,886 INFO PyGObject version: (2, 26, 0) > 2010-12-29 19:36:43,886 INFO PyGtk version: (2, 22, 0) > 2010-12-29 19:36:43,887 INFO Language: [('LANGUAGE', > 'en_US.UTF-8'), ('LC_ALL', 'en_US.UTF-8'), ('LC_MESSAGES', > 'en_US.UTF-8'), ('LANG', 'en_US.UTF-8')] > terminate called after throwing an instance of 'std::runtime_error' > what(): locale::facet::_S_create_c_locale name not valid > Abort trap > > > And in database file /home/magik/.miro/sqlitedb > is only one table `icon_cache` with schema > `CREATE TABLE icon_cache (id integer PRIMARY KEY, etag text, modified > text, filename text, url text);` > > > I don't used this port before, so I don't known which update broke this port. > >