locale: Cannot set LC_* to default locale: No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eglibc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I got these on a recent upgrade today:
Preparing to replace accountsservice 0.6.15-2ubuntu7 (using .../accountsser
Unpacking replacement accountsservice ...
Preparing to replace libaccountsservice0 0.6.15-2ubuntu7 (using .../libaccounts
Unpacking replacement libaccountsservice0 ...
Setting up libaccountsservice0 (0.6.15-2ubuntu8) ...
Setting up accountsservice (0.6.15-2ubuntu8) ...
Processing triggers for libc-bin ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
ldconfig deferred processing now taking place
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libc-bin 2.15-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Tue Feb 21 14:59:15 2012
Dependencies:
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en
SHELL=/bin/bash
SourcePackage: eglibc
UpgradeStatus: Upgraded to precise on 2012-01-29 (22 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.