On Fri, Jan 10, 2014 at 03:28:42PM +0000, Mathieu Roy wrote: > Package: locales > Version: 2.17-97 > Severity: important > > Hello, > > On a fresh (deboostrap) testing install, I end up with a weird issue. > > i18n seems to be mostly working. For instance, the shell is properly localized > > # bash --version > GNU bash, version 4.2.45(1)-release (x86_64-pc-linux-gnu) > Copyright (C) 2011 Free Software Foundation, Inc. > Licence GPLv3+ : GNU GPL version 3 ou ultĂ©rieure > <http://gnu.org/licenses/gpl.html> > > Ceci est un logiciel libre ; vous ĂȘtre libre de le modifier et de le > redistribuer. > Aucune garantie n'est fournie, dans la mesure de ce que la loi autorise. > > > KDE, however, is not, showing in systemconfig that the system have no valid > system language. > > Trying to understand why, I noticed it tries > > open("/usr/share/locale/fr_FR.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 > ENOENT > (No such file or directory) > open("/usr/share/locale/fr_FR.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 > ENOENT ( > No such file or directory) > open("/usr/share/locale/fr_FR/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No > su > ch file or directory) > open("/usr/share/locale/fr.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT > (No > such file or directory) > open("/usr/share/locale/fr.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT > (No > such file or directory) > open("/usr/share/locale/fr/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No > such > file or directory) > > This tells me that the system language setting is properly (fr.UTF-8) set, > accordingly to /etc/default/locale > > And that's something is fishy with the locales package that is supposed to > provide the relevant file: > > # dpkg -S /usr/share/locale/fr/LC_MESSAGES/libc.mo > locales: /usr/share/locale/fr/LC_MESSAGES/libc.mo > > I tried to regenerate locales doing dpkg-reconfigure locales: no effect. > Then I dpkg --purge and install of locales package: no effect. > I did a apt --reinstall install of libc6 package: no effect > > I dont know exactly what I should do/try next. Any clues?
Have you checked your filesystem is in a good state? There is no need to reinstall or to regenerate locales, libc.mo is provided by the locales packages directly, as your dpkg -S search shows. So if the file is there but can't be opened by the kernel, I would go for a kernel or a filesystem issue. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org