[Bug 1374749] Re: ubi-console-setup failed with exit code 141 with "KeyError: Russian'" even in 2.18.8.2

[Jonathan Riddell]

*** This bug is a duplicate of bug 1182784 ***
    https://bugs.launchpad.net/bugs/1182784

** This bug is no longer a duplicate of bug 1373033
   ubi-console-setup failed with exit code 141 with "KeyError: '英語 (美式)'" after Ubiquity 2.18.8.2
** This bug has been marked a duplicate of bug 1182784
   Install with non English language fails on Keyboard: "ubi-console-setup failed with exit code 141" or "Installer Crashed"

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1374749

Title:
   ubi-console-setup failed with exit code 141 with "KeyError: Russian'"
  even in 2.18.8.2

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I can reproduce bug #1182784 even when 2.18.8.2 is installed. The
  system locale is zh_TW.UTF-8 and I didn't change it in the installer.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.8.2
   ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CasperVersion: 1.340
  CurrentDesktop: KDE

  __________________________________________________________________________________________________________________

  Russian Keyboard abolutely does not work in kUbuntu 14.04.1 Installer!
  No Way!

  __________________________________________________________________________________________________________________

  Try to install with Russian Keyboard (i.e. choose it at boot screen)
  and there's a "ubi-console-setup failed with exit code 141" after
  setting the timezone; later (after ignore) the installation completely
  fails.

  
  Starting with version 2.18.8.2 when choosing Russian keyboard layout , the installer fails.
  Prior to version 2.18.8.1 everything worked perfectly !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1374749/+subscriptions