• Para aprender qué puedes hacer con Tails lee nuestra documentación. - Para preguntas más generales acerca de qué es Tails, lee nuestras Preguntas Frecuentes.

Problemas al arrancar Tails

Esta sección lista problemas conocidos de seguridad con hardware específico. Para reportar un problema con otro hardware lee nuestras recomendaciones para reportar cuando Tails no arranca.

Memorias USB problemáticas

SanDisk

Muchas memorias USB SanDisk están configuradas por el fabricante como discos fijos, y no como discos removibles. Como consecuencia, requieres remover el parámetro de boot live-media=removable. Mira la sección de solución de problemas cuando Tails no arranca totalmente en PC o Mac.

• SanDisk Cruzer Edge 8GB
• SanDisk Cruzer Extreme USB 3.0 16GB, 32GB y 64GB
• SanDisk Cruzer Fit USB 2.0 8GB, 16GB, y 32G
• SanDisk Cruzer Force 8GB
• SanDisk Cruzer Glide 4GB, 8GB y 16GB
• SanDisk Cruzer Switch USB 2.0 8GB y 32GB
• SanDisk Cruzer USB 3.0 64GB
• SanDisk Cruzer Blade 4GB, 8GB, y 32GB
• SanDisk Cruzer Facet
• SanDisk Cruzer Orbiter 32GB (se cuelga un poco al instalar pero luego arranca bien)
• SanDisk Ultra 16GB, 32GB

SanDisk had begun the production of flash drives configured as fixed disk in 2012 to meet new requirements for Windows 8 Certification, and ended it in mid-2014. The flash drives that comply with this certification will have the Windows 8 logo on their packaging. If a flash drive does not have the Windows 8 logo on its packaging, then that drive will function as a removable disk and should work with Tails.

Lee también #6397.

PNY

Al instalar Tails las memorias USB PNY tienen problemas con el peso de la escritura constante y son dados a fallar.

Aegis

• Aegis Secure Key USB 2.0

Durante el proceso de arranque el USB pierde electricidad momentáneamente, causando que las memorias Aegis cifradas por hardware se cierren, y el PIN se debe escribir de nuevo (rapidamente) para completar el proceso de arranque.

• Aegis Secure Key USB 3.0

Esta memoria USB no arranca Tails de ninguna manera, la solución de USB 2.0 no funciona para este hardware.

Kingston DataTraveler 2000

Arrancar Tails desde un Kingston DataTraveler 2000 no funciona.

Otros fabricantes

• Staples Relay USB 2.0 16GB sufre de los mismos problemas que algunas memorias USB SanDisk.

Mac

• Any Mac with 32-bit EFI may not succeed in booting Tails USB stick created by Tails Installer. You can check if a given Mac is 32-bit or 64-bit EFI on that list: http://www.everymac.com/mac-answers/snow-leopard-mac-os-x-faq/mac-os-x-snow-leopard-64-bit-macs-64-bit-efi-boot-in-64-bit-mode.html
• MacBook Pro 2016 y 2017: el teclado, trackpad y barra táctil no funcionan.
• MacBook Pro 5,5 no arranca con Tails en modo UEFI.
• MacBook Pro 5,1 17" (Nvidia GeForce 9400M): debes añadir la opción de arranque nouveau.noaccel=1 para que la pantalla funcione correctamente.
• MacBook Air 3,2 (A1369 EMC 2392) se congela al arrancar Tails en modo UEFI.
• Mac Pro Tower y MacBook Pro 4,1 (ambos de principios de 2008) no arrancan de una memoria USB creada con Tails Installer.

PC

Acer Travelmate 8573T-254G50M

Arrancar desde DVD funciona bien, pero no inicia desde memorias USB creadas usando Tails Installer.

Este problema puede estar corregido en Tails 1.1 y versiones mas nuevas: por favor repórtanos los resultados de tus tests.

Acer Aspire 5315-ICL50 y Acer ES-1-331

No inicia en memorias USB creadas usando Tails Installer.

ASUS VivoBook X202E

Debes habilitar Legacy support para arrancar Tails. Para habilitar legacy support, habilita 'Launch CSM' en el menú boot.

Este problema puede estar corregido en Tails 1.1 y versiones mas nuevas: por favor repórtanos los resultados de tus tests.

Dell Chromebook LULU

Debes añadir nomodeset a las opciones de arranque para iniciar Tails.

Dell Inc. Latitude E6430 y E6230

No inicia en memorias USB creadas usando Tails Installer.

Con versiones de BIOS A03 06/03/2012 (y A09, A11, y A12)

Mensaje de error: Invalid partition table!

Solución (al menos con las versiones de BIOS A09, A11, y A12): presiona Enter y continuará con el boot.

Este problema puede estar corregido en Tails 1.1 y versiones mas nuevas: por favor repórtanos los resultados de tus tests.

Dell XPS L702X/03RG89, Samsung RV520, Samsung Series 7 Chronos

No inicia en memorias USB creadas usando Tails Installer.

Nos han reportado que la legacy BIOS que tienen estos sistemas no sabe cómo manejar el sistema de particiones GPT instalado por Tails Installer.

Este problema puede estar corregido en Tails 1.1 y versiones mas nuevas: por favor repórtanos los resultados de tus tests.

http://en.community.dell.com/support-forums/laptop/f/3518/p/19392884/20010995.aspx

Dell Inspiron 8100

La pantalla tendrá la resolución incorrecta a menos que añadas video=LVDS-1:1600x1200 nouveau.noaccel=1 a las opciones de arranque. Este problema se puede corregir en Tails 1.1 y posteriores: por favor repórtanos los resultados de tus tests.

Dell Dimension 2400

No arranca ni de USB ni de DVD. El sistema se rompe con una pantalla en blanco y el teclado se bloquea. Este problema puede estar corregido en nuevas versiones: por favor repórtanos tus resultados.

Fujitsu Siemens Amilo A 1667G

No inicia en memorias USB creadas usando Tails Installer.

HP Compaq dc5750 Microtower

No arranca Tails 1.2.3 creado con Tails Installer.

HP Compaq 615

Necesitas actualizar el firmware a su última versión para poder arrancar con un dispositivo instalado usando el Tails Installer.

HP Compaq CQ60-214DX

Tails 3.3 no arranca. (#14739)

HP Pavilion 15-ab277ca

Tails 3.3 se reinicia al arrancar y nunca termina de arrancar bien (#15152).

HP Pavilion dv7

Desde Tails 1.3 se queda atorado en el menú de arranque Boot, si Tails es instalado manualmente o usando Tails Installer.

HP ProBook

Con UEFI habilitado, cuando eligas un dispositivo de boot, selecciona Boot From EFI File y luego Filesystem Tails y EFI/BOOT/BOOTX64.EFI.

Esa solución aplica a, al menos, a la siguiente HP ProBook:

• 4330s
• 6560b

Lenovo IdeaPad Y410p

No arranca Tails 1.1 desde una memoria USB instalada manualmente en Linux.

Lenovo IdeaPad z585

Vuelve continuamente al menú de arranque cuando Tails está instalado en DVD.

Clevo W258CU, ThinkPad X121e, T420i, T410, T520, W520, T530, T60, E325, y E530

Estas máquinas no inician desde una memoria USB creada usando Tails Installer debido a una limitación del firmware.

Una solución para estas máquinas es utilizar el proceso de instalación manual. Ten en cuenta, sin embargo, que esta técnica no te permite configurar un volumen persistente.

Este problema puede estar corregido en Tails 1.1 y versiones mas nuevas: por favor repórtanos los resultados de tus tests.

Problemas del Wi-Fi

Broadcom Wi-Fi network interface needing broadcom-sta-dkms

Some Broadcom Wi-Fi interfaces require the wl driver, provided by the broadcom-sta-dkms Debian package, to work in Tails.

The wl driver is not included in Tails because it is proprietary.

To find out if your Wi-Fi interface requires the wl driver:

1. Execute the following command in a terminal:

   lspci -nn | grep Network
   

2. Verify if your device is in the list of devices supported by the broadcom-sta-dkms package on the corresponding Debian wiki page. If you find your device in the list of supported devices, then it is impossible to use your Wi-Fi card in Tails.

Systems with RTL8723be Wi-Fi adapter

On some computers with a RTL8723be Wi-Fi adapter, Tails may fail to discover Wi-Fi networks, may provide unreliable Wi-Fi connections, or may provide poor Wi-Fi performance.

Most such problems can be solved by adding startup options.

The exact combination of options that will work depends on the computer, so try the following instructions until you find a combination that works for you:

1. Add rtl8723be.fwlps=0 rtl8723be.ips=0 to the startup options.
2. Add rtl8723be.ant_sel=1 to the startup options.
3. Add rtl8723be.ant_sel=2 to the startup options.
4. Add rtl8723be.ant_sel=1 rtl8723be.fwlps=0 rtl8723be.ips=0 to the startup options.
5. Add rtl8723be.ant_sel=2 rtl8723be.fwlps=0 rtl8723be.ips=0 to the startup options.

Security issues

Tails no borra la memoria de vídeo

Tails no borra la Memoria gráfica de acceso aleatorio. Luego de usar Tails y reiniciar el ordenador en otro sistema operativo, este otro sistema operativo puede ver qué se mostró en la pantalla dentro de Tails.

Apagar el ordenador totalmente, en lugar de reiniciarlo, puede ayudar a que la memoria de video se vacíe.

Ver Erase video memory on shutdown.

Tails falla al apagarse o reiniciar

When stopping Tails on some hardware, the memory wipe procedure fails to complete: the display gets scrambled, but the computer doesn't completely shutdown or restart. Sometimes the caps-lock button light of the keyboard flashes.

Este problema ha sido reportado en el hardware siguiente:

• Apple when booting from a USB stick:
  • MacBook Air 5,1
  • MacBook Air 5,2 (using a device installed with Tails Installer)
  • MacBook Air 6,2
  • MacBook Pro 7,1 13-inch (mid 2010)
  • MacBook Pro 9,2 13-inch (mid 2012)
  • MacBook Pro 8,1 13-inch (late 2011)
  • MacBook Pro 10,2
  • MacBook Pro Retina 11,1 (late 2013)
  • MacBook Pro Retina 13-inch (early 2015)
• Hewlett-Packard HP ENVY x360
• Hewlett-Packard HP Pavilion dv6 Notebook PC
• Hewlett-Packard HP ProBook 450 G0
• Lenovo ThinkPad X61, only on emergency shutdown when pulling out the USB stick
• Lenovo ThinkPad X220
• Toshiba Satellite C855D
• Dell Inc. Studio 1458
• Fujitsu Lifebook AH531/GFO, only on regular shutdown, emergency shutdown works
• Samsung N150P
• Acer Aspire e1-572
• Dell Latitude E6230
• Microsoft Surface Pro 3

Otros problemas

Chainloading Tails from GRUB

To workaround problems in booting Tails on laptops with UEFI support, it is possible to chainload the syslinux on the ISO image from another boot loader that is already working on the laptop, like GRUB. Be careful not to modify at all the options of syslinux in the process.

The following commands, run from the GRUB shell, might be helpful:

set root=(hd1)
chainloader +1
boot

Boot Loader Menu has display issues

Since Tails 1.1, on some hardware (ThinkPad X230, MacBook Pro 8,1), the Boot Loader Menu is not displayed properly. Tails starts fine, though.

Connecting to FTP servers is not possible

Public FTP servers on the Internet are not reachable using Tails. See Fix FTP support for more details.

Tails fails to connect to certain Wi-Fi networks

This might be related to the introduction of wireless regulation support in Tails 0.13.

The desktop crashes when run with the default QEMU emulated processor

Due to a bug in llvmpipe, when Tails runs in a QEMU virtual machine with the default emulated CPU, the GNOME desktop crashes after login.

To workaround this problem, pass @-cpu host@ on the QEMU command-line. If you use libvirt, choose Copy host CPU configuration in virt-manager's processor configuration screen.

Touchpad configurations

Acer TravelMate B113 - ETPS/2 Elantech Touchpad

synclient FingerPress=256;
synclient TapButton3=0;
synclient Clickpad=1;
synclient VertTwoFingerScroll=1;
synclient FingerLow=1;
synclient FingerHigh=1;

Acer C720 - Cypress APA Touchpad

synclient FingerLow=5;
synclient FingerHigh=5;

Bluetooth devices don't work

Bluetooth is not enabled in Tails for security reasons.

Tor Browser is translated in a limited number of languages

Since Tails 1.2, the web browser is based on Tor Browser which is translated in less languages than before. You can see the list of languages available in Tor Browser from the Tor Browser homepage.

Playing WebM videos in the Tor Browser fails on old hardware

On systems that only have one CPU code, WebM videos may fail to play in the Tor Browser, and show the error message: "Video can't be played because the file is corrupt". You can work around this by downloading the video and watching it in the Totem video player.

Tails does not boot after automatic upgrade

Sometimes, after an automatic upgrade, Tails gets blocked when booting, often after the message 'Loading, please wait...'.

To fix this problem, you can update your Tails manually.

Note that your Persistent Volume will be safely preserved.

Persistent folder disappears and persistent feature configurations do not load

Sometimes, the Persistent folder is missing and the configurations for persistent features do not load.

Most likely this means that the persistence.conf file has disappeared. However, the files in the Persistent folder and the persistent feature configurations should still be saved.

If you encounter this problem:

1. Enable your encrypted persistent storage in Tails Greeter when you start Tails.

2. Choose Applications ▸ Tails ▸ Configure persistent volume.

3. If you are asked to enter a passphrase, enter the same passphrase that you used to unlock your persistent storage.

4. Click Save, then restart Tails.

Your Persistent folder and persistent feature configurations should be restored.

Tails behaves weirdly if an automatic upgrade is only partially applied

Tails might behave weirdly if an automatic upgrade is only partially applied. For example, your keyboard might not respond to key presses or you might be unable to connect to networks.

To fix this problem:

Mount your Tails system partition in another Linux system

1. Start in another Tails or in a Linux system such as Debian or Ubuntu.

2. Open GNOME Disks.

3. Plug in your Tails USB stick that behaves weirdly.

4. If a prompt appears to unlock the persistent volume on your Tails USB stick, click Cancel.

5. Your Tails USB stick should appear in the left pane of GNOME Disks. Click on your Tails USB stick.

6. In the right pane, click on the partition labeled Tails. It should be listed as Partition 1.

7. Click on the button to mount the Tails partition.

8. Click on the link in the right pane to open the Tails partition in the Files browser. The link should look something like /media/username/Tails.

Edit your Tails.module file

1. In the Files browser, open the live folder. Then open the file named Tails.module with a text editor, for example, GNOME Text Editor.

2. Add the line x.x.squashfs to the end of the Tails.module file. Replace x.x with the Tails version you are upgrading to.

   For example, if you are upgrading to version 3.8, you would add 3.8.squashfs to the end of the Tails.module file.

   Your Tails.module file should look something like this, with different version numbers:

   filesystem.squashfs
   3.7.squashfs
   3.7.1.squashfs
   3.8.squashfs
   

3. Save the Tails.module file.

4. In the sidebar of the Files browser, click on the button on the Tails label to unmount the partition. If your persistent volume shows in the sidebar, also click on the button on the persistent volume label.

5. Unplug your Tails USB stick.

Your Tails should now work properly.

Icons and information located on the top right corner of the screen disappeared

Sometimes, some of the icons located on the top right corner of the screen are not displayed entirely, or at all. For example, the icon that allows to change to another keyboard layout may be hidden. Other information, such as the clock, may not be visible.

Press Alt+F2 and type r to restart GNOME Shell, which often solves this problem.

See #10576 for more details.

Some languages do not have the correct keyboard layout set by default

When selecting some languages in the Tails Greeter, the default associated keyboard layout fallbacks to US.

To use the right keyboard layout during a session, set it in the Tails Greeter after having set the language. When the desktop has started, apply the keyboard layout by clicking on the en systray icon.

Affected language codes are AYC, BHB, BRX, CMN, HAK, HNE, LIJ, LZH, MHR, NAN, NHN, QUZ, SGS, SHS, TCY, THE, UNM, WAE and YUE.

The OpenPGP passphrase prompt steals the keyboard and mouse focus

This happens when one has enabled the GnuPG persistence feature before Tails 2.3. To fix this problem, execute the following command in a terminal:

echo "no-grab" >> ~/.gnupg/gpg-agent.conf

Problems when the system clock goes backwards

When connecting to Tor, Tails sets the system time to the current time in the Coordinated Universal Time (UTC) timezone. Many operating systems, such as Linux and macOS, write time expressed in UTC to the hardware clock of the computer. But, Windows instead writes time expressed in the local timezone to the hardware clock of the computer. So, if you are east of the United Kingdom (which is in the UTC timezone) on a computer that also runs Windows, Tails will make the system clock go backwards during startup. Unfortunately, this may trigger software errors in Tails.

For example, when this happened in Tails 3.4 the Applications menu sometimes stops working.

To solve this problem permanently on a Windows computer, set the hardware clock of the computer to UTC.

See #15168 for more details.

Lenovo ThinkPad 11e

Tails may be unstable and stop working regularly on some Lenovo ThinkPad 11e laptops, such as the 2015 model.

Para corregir este problema añade intel_idle.max_cstate=1 a las opciones de arranque.