After update I get this message box.

Error found when loading ‘/etc/profile’

locale: Cannot set LC_ALL to default locale no such file or directory
locale: Cannot set LC_ALL to default locale no such file or directory

As a result the session will not be configured correctly.
You should fix the problem as soon as feasible.

When I click OK, boot hangs, and I have to restart The computer, and the message reappears.

When in recovery mode I do a locale command, LC_ALL is blank, The rest has nn_NO.utf8

When I type locale-gen command I get

Cannot remove ‘usr/lib/locale/locale-archive’: Read-only file system
Generating locales
en_AU.UTF-8... cannot open local archive ‘usr/lib/locale/locale-archive’:
  Read-only file system

This message just repeats for each locale

What to do?

  • 1
    The message box should be a warning, and you ought to be able to log in the normal way. Once logged in, please run the command cat /etc/profile and show us what it outputs by editing your question. – Gunnar Hjalmarsson Apr 20 '18 at 19:25
  • 1
    If the graphical login fails, try to open a tty console with Ctrl+Alt+F2 and log in there. I'm not quite sure what you should look for, though. If you edited /etc/profile, the error may be there, but I'm not quite sure. Did you do anything with your locale settings recently? If so, which file did you edit? – Gunnar Hjalmarsson Apr 21 '18 at 2:52
  • 1
    To those who want to close this due to it being a bug: There is no evidence that this is a bug. A broken locale may cause bad behavior in any version. – Gunnar Hjalmarsson Apr 21 '18 at 10:32
  • I have the same issue. I stopped my upgrade from 17.10 when it got stuck. Now I am not sure what is wrong. I am not able to install any software – SPV May 8 '18 at 2:07
  • 1
    @Zanna: The "Error found..." message may show up only at session login (I know since I wrote that code), so to me it looks like the boot is completed. But since the OP does not respond to suggestions, he probably fixed the problem and moved on... – Gunnar Hjalmarsson May 10 '18 at 13:23

I moved on after not being able to boot into the desktop. Tried to correct and create a new locale from command, but failed - and ultimately did a complete reinstall.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.