Not Localized Abrowser After Installation

Catégorie:Rapporter un bogue
Attribué:Non assigné

After installing Trisquel 6.0 in Spanish, the Abrowser interface is in English.

Steps to reproduce

  1. Download the trisquel_6.0_i686.iso 04-Mar-2013 07:40 696M from .
  2. Burn the image to a CD.
  3. Boot from CD.
  4. In the installer screen, select "Español" as the language for installation.
  5. Select "Instalar Trisquel".
  6. In "Bienvenido/a", select "Español" and click "Continuar".
  7. In "Preparando la instalación de Trisquel", click "Continuar".
  8. In "Tipo de instalación" select "Reemplazar Trisquel 5.0 con Trisquel" and click "Continuar".
  9. In "Reemplazar Trisquel 5.0 con Trisquel" click "Continuar".
  10. In "¿Dónde se encuentra?" select "Bogota" and click "Continuar".
  11. In "Distribución de teclado" select "Español (Latinoamericano)" and click "Continuar".
  12. In "¿Quién es usted?" fill the user name, computer name and password fields, and click "Continuar".
  13. Wait for the installation to finish and reboot the system when asked for.
  14. Log in
  15. Click on the Web browser icon located to the bottom left of the screen.

Expected behaviour

After following the steps above:

  1. The Web browser is displayed with its graphical interface in Spanish.
  2. The Web browser shows the page.

Unexpected behaviour (or what happens instead)

After following the steps above:

  1. The Web browser is displayed with its graphical interface in English.
  2. The Web browser shows the page.
ven, 03/15/2013 - 05:03

quidam released an update to Abrowser 19 last week. This bug was mentioned in the 2013-03-05 meeting[1]. Can you confirm if this bug is still present in the latest Abrowser?


sirgazil (non vérifié):
Sam, 03/16/2013 - 00:33

Hi, andrew.

I'd like to check again with the latest, and final, Trisquel 6.0 ISO but I'd have to use a virtual machine for that. The problem is VirtualBox is not working for me in Trisquel 6.0.

I'll see if I can find another real machine to test again.

dim, 03/17/2013 - 07:20

I just did a fresh install with the FSF (which implies i18n) amd64 image; the reported issue happened to me too.

lun, 01/12/2015 - 22:08
Statut:active» fixed

This is fixed in current versions as far as I know. Reopen if I'm wrong.

lun, 01/26/2015 - 22:10
Statut:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.