summaryrefslogtreecommitdiffstats
path: root/wiki/src/support/known_issues.mdwn
blob: 61f56d65237cd40eef3f98f11eb30bdf01d8cc9e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
[[!meta title="Known issues"]]

- For issues with graphics cards, see our [[know issues with graphics cards|known_issues/graphics]].
- To learn what you can do with Tails, refer to our [[documentation|doc]].
- For more general questions about Tails, refer to our [[FAQ|support/faq]].

[[!toc levels=3]]

Problems starting Tails
=======================

This section lists known problems with specific hardware. To report a problem
with different hardware see our [[report guidelines when Tails does not
start|doc/first_steps/bug_reporting#does_not_start]].

<a id="problematic-usb-sticks"></a>

<a id="pny"></a>

### PNY

<!--
Last updated: 2014-08-02
PNY is quite popular among WB reporters:
-->

When installing Tails, PNY USB sticks have problems with the constant write load
and are prone to failure.

<a id="aegis"></a>

### Aegis

<!--
Last updated: 2015-04-10
-->

* Aegis Secure Key USB 2.0

During the boot process, USB is briefly powered off, that causes Aegis hardware-encrypted USB sticks to lock down, and the PIN must be entered again (fast) in order to complete the boot.

* Aegis Secure Key USB 3.0

This USB stick doesn't start Tails at all, the USB 2.0 workaround is not working for that hardware.

<a id="datatraveler-2000"></a>
<a id="datatraveler-100-g3"></a>

### Kingston DataTraveler 2000, Kingston DataTraveler 100 G3

Starting Tails from a Kingston DataTraveler 2000 or DataTraveler 100G3 doesn't work.

<a id="mac"></a>

Mac
---

<!--
Last updated:
- MacBook Air 3,2: 2014-06-27
- MacBook Pro 5,1: 2015-06-19
- MacBook Pro 4,1: 2014-08-15
-->

* Any Mac with 32-bit EFI might not start on Tails.
  You can check if a given Mac is 32-bit
  or 64-bit EFI on that list:
  <https://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 and 2017: the keyboard, trackpad and Touch Bar do
  not work.

* MacBook Pro 5,1 17" (Nvidia GeForce 9400M): one must add the
  `nouveau.noaccel=1` boot parameter so that the display
  works properly.

* MacBook Air 3,2 (A1369 EMC 2392) freezes when booting Tails in
  UEFI mode.

* Mac Pro Tower and MacBook Pro 4,1 (both from early 2008)
  fails to start on Tails.

<a id="pc">

PC
--

<a id="lockup"></a>

### "Soft lockup" error

<!--
Last updated: 2019-05-20
-->

On some laptops, Tails starts with the following error:

<p class="pre">soft lockup - CPU#<span class="command-placeholder">N</span> stuck for <span class="command-placeholder">N</span>s</p>

To make Tails start successfully, add the following options to the
[[startup options|/doc/first_steps/startup_options/#boot_loader_menu]]:

    acpi_rev_override=1 nouveau.modeset=0

<a id="sg-black-screen"></a>

### Acer Travelmate 8573T-254G50M

<!--
Last updated: 2013-08-08
-->

Booting from DVD works fine, but does not start from USB sticks.

This problem might be corrected in Tails 1.1 and newer: please report
your test results back to us.

### Acer Aspire 5315-ICL50

<!--
Last updated: 2015-04-10
-->

Does not start on USB sticks.

### ASUS VivoBook X202E

<!--
Last updated: 2013-07-20
-->

Legacy support needs to be enabled in order to start Tails. To enable
legacy boot support, enable 'Launch CSM' under boot (menu).

This problem might be corrected in Tails 1.1 and newer: please report
your test results back to us.

### Dell Chromebook LULU

<!--
Last updated: 2018-01-10
-->

You need to add `nomodeset` to the
[[startup options|/doc/first_steps/startup_options/#boot_loader_menu]]
to make Tails start successfully.

### Dell Latitude E5250

<!--
Last updated: 2019-04-05
-->

Does not start on Tails USB sticks.

### Dell Latitude E6430 and E6230

<!--
Last updated: 2018-06-14 (WB#7653aff4f415e996567233d8c088da08)
-->

Does not start on USB sticks.

With BIOS versions A03 06/03/2012 (and A09, A11, and A12)

Error message: `Invalid partition table!`

Workaround (at least with BIOS versions A09, A11, and A12): just hit enter
and it will continue with the boot.

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

<!--
Last updated:
- Dell XPS L702X/03RG89: 2012-08-22
- Samsung RV520: 2012-12-21
- Samsung Series 7 Chronos: 2014-02-28
-->

Does not start on USB sticks.

We were reported that the legacy BIOS shipped on these systems doesn't
know how to deal with the GPT partition scheme used in Tails.

This problem might be corrected in Tails 1.1 and newer: please report
your test results back to us.

<https://www.dell.com/community/Laptops-General-Read-Only/GPT-Bootable-Bios-Optimus-Switch-Are-Necessary-For-L502x-L702x/m-p/3699920>

### HP Compaq dc5750 Microtower

<!--
Last updated: 2015-02-10
-->

Does not start Tails 1.2.3.

### HP Compaq 615

<!--
Last updated: 2013-11-05
-->

You need to update the firmware to its latest version in order to start from a
USB stick.

### HP Compaq CQ60-214DX

<!--
Last updated: 2018-02-16
-->

Tails 3.3 does not start.

### HP Pavilion 15-ab277ca

<!--
Last updated: 2018-01-15
Worked in 3.0 (WB#b485a1cfa7f7cc1073a70b31f428097c)
-->

Tails 3.3 restarts during startup and never starts successfully.

### HP ProBook

<!--
Last updated: 2016-05-14
-->

With UEFI enabled, when choosing a boot device, select `Boot From EFI File` and
then `Filesystem Tails` and `EFI/BOOT/BOOTX64.EFI`.

That workaround applied to, at least, the following HP ProBook:

* 4330s
* 6560b

### Lenovo IdeaPad Y410p

<!--
Last updated: 2014-08-03
-->

Does not start Tails 1.1 from USB installed manually in Linux.

### Lenovo IdeaPad z585

<!--
Last updated: 2014-08-05
-->

Goes back continuously to Boot Loader Menu on Tails installed on DVD.

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

<!--
Last updated:
- Clevo W258CU: 2014-03-29
- ThinkPad X121e: 2014-02-10
- ThinkPad T420i: 2014-06-06
- ThinkPad T410: 2014-03-27
- ThinkPad T520: 2012-10-11
- ThinkPad W520: 2014-02-17
- ThinkPad T530: 2013-08-09
- ThinkPad T60: 2018-04-30
- ThinkPad E325: 2013-02-28
- ThinkPad E530: 2014-03-17
-->

These machines do not start on USB sticks
due to a firmware limitation.

This problem might be corrected in Tails 1.1 and newer: please report
your test results back to us.

### System76 Oryx Pro

This machine does not start from a Tails USB stick: the Linux kernel
included in at least Tails 3.11 to 3.13.1, inclusive, does not support
the hardware USB controller.

<a id="wi-fi"></a>

Wi-Fi issues
============

[[!inline pages="doc/anonymous_internet/networkmanager/no-wifi.inline" raw="yes" sort="age"]]

* Check in the following sections
  if there is a workaround to get your Wi-Fi interface work in Tails.

<a id="wi-fi-workarounds"></a>

Knowing the model of your Wi-Fi interface
-----------------------------------------

1. Open <span class="application">Terminal</span> and execute the following command:

       lspci -v | grep "Network controller"

88W8897 [AVASTAR] 802.11ac Wireless
-----------------------------------

<!--
Last updated: 2018-09-19
-->

On some computers with a Marvell Avastar 88W8897 Wi-Fi adapter, such
as some Microsoft Surface Pro models, Tails fails to connect to
Wi-Fi networks.

If you experience this problem, you can try to [[disable MAC address
spoofing|doc/first_steps/startup_options/mac_spoofing]] that sometimes
fixes it.

RTL8723BE PCIe Wireless Network Adapter
---------------------------------------

<!--
Last updated: 2017-12-24
-->

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|/doc/first_steps/startup_options/#boot_loader_menu]].

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.

<a id="broadcom-sta-dkms"></a>

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

<!--
Last updated: 2019-01-29
-->

Some Broadcom Wi-Fi interfaces require the
[`wl`](https://wiki.debian.org/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.

You device requires the `wl` driver if it is in the list of devices
supported by the `broadcom-sta-dkms` package on the corresponding
[Debian wiki page](https://wiki.debian.org/wl). If you find your device
in the list of supported devices, then it is impossible to use your
Wi-Fi card in Tails.

## Lenovo Legion Y530

<!--
Last updated: 2019-05-10
-->

Wi-Fi adapter does not work.

Adding `modprobe.blacklist=ideapad_laptop` to the
[[startup options|doc/first_steps/startup_options#boot_loader_menu]] fixes the
issue.

Security issues
===============

<a id="video-memory"></a>

Tails does not erase video memory
---------------------------------

Tails doesn't erase the [[!wikipedia Video_RAM_(dual-ported_DRAM) desc="video memory"]] yet.
When one uses Tails, then restarts the computer into another operating
system, that other operating system can see what has been displayed on
the screen within Tails.

Shutting down the computer completely, instead of restarting it,
might allow the video memory to empty itself.

See [[!tails_ticket 5356 desc="Erase video memory on shutdown"]].

<a id="fails-to-shutdown"></a>

Tails fails to completely shutdown or restart
---------------------------------------------

<!--
Last updated: 2013-03-13
-->

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.

<div class="caution">

When this happens, there is no guarantee that the memory is wiped entirely.

</div>

This issue has been reported on the following hardware:

  - Apple when booting from a USB stick:
    - MacBook Air 5,1
    - MacBook Air 5,2
    - 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 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

<!--

Note: If we enable again this section in the future, we should link to
it from /doc/about/fingerprint.mdwn.

<a id="fingerprint"></a>

Browser fingerprint
===================

There are known differences between the fingerprints of <span
class="application">Tor Browser</span> inside and outside of Tails:

For more detail, see our [[documentation on the Tails
fingerprint|doc/about/fingerprint]].

-->

Other issues
============

<a id="chainloading"></a>

Chainloading Tails from GRUB
----------------------------

<!--
Last updated: 2014-04-09
-->

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
-----------------------------------

<!--
Last updated: 2014-06-27
-->

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.

Tails fails to connect to certain Wi-Fi networks
------------------------------------------------

<!--
Last updated: 2012-11-10
-->

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
---------------------------------------------------------------------

<!--
Last updated: 2015-12-31
-->

Due to a [bug in llvmpipe](https://patchwork.freedesktop.org/patch/34445/), 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 <span class="application">libvirt</span>, choose <span
class="guilabel">Copy host CPU configuration</span> in <span
class="application">virt-manager</span>'s processor configuration screen.

Touchpad configurations
-----------------------

### Acer TravelMate B113 - ETPS/2 Elantech Touchpad

<!--
Last updated: 2013-08-15
-->

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

### Acer C720 - Cypress APA Touchpad

<!--
Last updated: 2016-08-20
-->

    synclient FingerLow=5;
    synclient FingerHigh=5;

Bluetooth devices don't work
----------------------------

Bluetooth is not enabled in Tails for security reasons.

<a id="browser_languages"></a>

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](https://www.torproject.org/projects/torbrowser.html.en).

Playing WebM videos in the Tor Browser fails on old hardware
------------------------------------------------------------

On systems that only have one CPU core, 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.

<a id="automatic_upgrade_fails"></a>
<a id="partial-upgrade"></a>

Tails fails to start or behaves weirdly after an automatic upgrade
------------------------------------------------------------------

<!--
Last updated: 2016-09-16
-->

Sometimes, after an automatic upgrade, your Tails might either:

- Fail to start. Often after the message:

  <pre>Loading, please wait...</pre>

- Behave weirdly. For example, your keyboard does not work or you cannot
  connect to a network.

To fix this problem, you can [[update your Tails
manually|doc/first_steps/upgrade/#manual]].

Note that your Persistent Volume will be safely preserved.

<a id="persistence-disappears"></a>

Persistent folder disappears and persistent feature configurations do not load
------------------------------------------------------------------------------

Sometimes, the <span class="filename">Persistent</span> folder is missing and
the configurations for persistent features do not load.

Most likely this means that the <span class="filename">persistence.conf</span>
file has disappeared. However, the files in the
<span class="filename">Persistent</span> folder and the persistent feature
configurations should still be saved.

If you encounter this problem:

1. Enable your encrypted persistent storage in
   <span class="application">Tails Greeter</span> when you start Tails.

1. Choose
   <span class="menuchoice">
     <span class="guimenu">Applications</span>&nbsp;▸
     <span class="guisubmenu">Tails</span>&nbsp;▸
     <span class="guimenuitem">Configure persistent volume</span></span>.

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

1. Click <span class="button">Save</span>, then restart Tails.

Your <span class="filename">Persistent</span> folder and persistent feature
configurations should be restored.

<a id="restart-shell"></a>

## 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 <span class="keycap">Alt+F2</span> and type `r` to restart GNOME
Shell, which often solves this problem.

See [[!tails_ticket 10576]] for more details.

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

<!--
Last updated: 2017-08-07
-->

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

<!--
Last updated: 2018-01-15
-->

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|doc/first_steps/introduction_to_gnome_and_the_tails_desktop#terminal]]:

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

<a id="utc"></a>

## Problems when the system clock goes backwards

When connecting to Tor, Tails sets the system time to the current time
in the [[!wikipedia 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 might trigger software
errors in Tails.

For example, when the system clock goes backwards:

<ul>
<li>The <span class="guimenu">Applications</span> menu might stop
working.</li>
<li>[[Connecting to Tor using `obfs4` bridges|doc/first_steps/startup_options/bridge_mode]]
might be impossible and <span class="application">Tor Launcher</span>
might get stuck on <span class="guilabel">Loading Network
Consensus</span>.</li>
</ul>

To solve this problem permanently on a Windows computer,
[set the hardware clock of the computer to UTC](https://wiki.archlinux.org/index.php/System_time#UTC_in_Windows).

## Lenovo ThinkPad 11e

<!--
Last updated: 2018-03-22
-->

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

To fix this problem, add `intel_idle.max_cstate=1` to the
[[startup options|/doc/first_steps/startup_options/#boot_loader_menu]].

## Acer Aspire One

If the sound output does not work on an Acer Aspire One laptop, add
`snd-hda-intel.model=acer-aspire` to the [[startup
options|/doc/first_steps/startup_options/#boot_loader_menu]].

## Electrum is outdated and cannot connect to servers

[[!inline pages="doc/anonymous_internet/electrum/phishing.inline" raw="yes" sort="age"]]

<a id="usb-gigabyte"></a>

## USB devices are not working on some [GIGABYTE](https://www.gigabyte.com/) motherboards

<!--
Last updated: 2019-06-02
-->

To workaround this issue, you can try to:

- Use other USB ports. For example, use USB 2 ports instead of USB 3
  ports and vice versa.

- Enable these 3 options in the BIOS

  - xHCI handoff
  - EHCI handoff
  - IOMMU controller

- Add the following
  [[startup options|/doc/first_steps/startup_options/#boot_loader_menu]]:

    amd_iommu=on iommu=pt

- Disable IOMMU in the BIOS then enable it again.

Some of these workarounds may disable some of the USB ports.