tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2024-03-20T09:10:01Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/20270Consider installing alsa-topology-conf package2024-03-20T09:10:01ZintrigeriConsider installing alsa-topology-conf packageIt includes `/lib/firmware/skl_hda_dsp_generic-tplg.bin` which is needed for some sound cards (e.g. the one in Acer Swift SF314-54 laptops as per wb:6300bb1298ef033102ff912805e93860).
Would there be any drawback in shipping this?
Tenta...It includes `/lib/firmware/skl_hda_dsp_generic-tplg.bin` which is needed for some sound cards (e.g. the one in Acer Swift SF314-54 laptops as per wb:6300bb1298ef033102ff912805e93860).
Would there be any drawback in shipping this?
Tentatively candidate for 6.1 as part of S11.Tails_6.1anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/19976backlit keyboard not working after Tails 5.82024-03-14T16:50:18ZGhost Userbacklit keyboard not working after Tails 5.8I'm using an ASUS laptop, and had no issues until after Tails v5.8.
In Tails 5.9 and later the backlit keyboard is not working anymore (verified on Tails v5.17.1).
I have tested latest release v5.17.1 on another laptop and the backlit ke...I'm using an ASUS laptop, and had no issues until after Tails v5.8.
In Tails 5.9 and later the backlit keyboard is not working anymore (verified on Tails v5.17.1).
I have tested latest release v5.17.1 on another laptop and the backlit keyboard is working correctly, so it's an issue with my particular ASUS laptop ( asus fx753vd gc193t ).
I'm used to see backlit keys, so I'm still using Tails 5.8.
Are there some shell commands that I can run on my computer, to help you diagnose the issue?
Thanks.https://gitlab.tails.boum.org/tails/tails/-/issues/16030SquashFS errors during boot lead to false-positives on graphics card error re...2024-02-20T11:12:14Zsajolidasajolida@pimienta.orgSquashFS errors during boot lead to false-positives on graphics card error reports_Originally created by @sajolida on [#16030 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16030)_
The following happened to me yesterday:
- I installed a USB stick using Tails Installer from Tails 3.9.
- Star..._Originally created by @sajolida on [#16030 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16030)_
The following happened to me yesterday:
- I installed a USB stick using Tails Installer from Tails 3.9.
- Starting it on my computer leads to GDM error message (`Error
starting GDM`) while my graphics card works fine with Tails.
- Having a closer look, I have tons of squashfs errors on boot.
I’m aware of tails/tails#5856 which has been focused on errors **while** Tor is
working (and detecting them from inside Tails). While I’d like to scope
this ticket to preventing false-positives on graphics card error
reports, while might lead to wrong information on
/support/known\_issues/graphics and be a problem for the project.
### Related issues
- **Related to** tails/tails#5856
- **Related to** tails/tails#14544
- **Related to** tails/tails#6766
- **Related to** tails/tails#17230
- **Has duplicate** tails/tails#12445Tails_6.0https://gitlab.tails.boum.org/tails/tails/-/issues/20205Error message not displayed when GDM fails2024-02-20T11:11:41ZboyskaError message not displayed when GDM failsTails 6.0~rc1 introduced a regression: when GDM fails to start (most likely because of unsupported hardware), no text is shown to the user.
see:
`config/chroot_local-includes/usr/libexec/gdm-wayland-session.tails`
To reproduce this, ju...Tails 6.0~rc1 introduced a regression: when GDM fails to start (most likely because of unsupported hardware), no text is shown to the user.
see:
`config/chroot_local-includes/usr/libexec/gdm-wayland-session.tails`
To reproduce this, just run Tails adding `autotest_broken_gnome_shell`Tails_6.0boyskaboyskahttps://gitlab.tails.boum.org/tails/tails/-/issues/19598Test all the Wi-Fi adapters that we have with Tails 62024-02-14T21:05:07Zsajolidasajolida@pimienta.orgTest all the Wi-Fi adapters that we have with Tails 6- [ ] Update https://tails.boum.org/blueprint/wi-fi_adapters/.
- [ ] Create a ticket for the next update.- [ ] Update https://tails.boum.org/blueprint/wi-fi_adapters/.
- [ ] Create a ticket for the next update.Tails_6.0sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/20121Upgrade to Linux 6.1.69 (DSA 5593-1)2024-01-10T14:13:31ZintrigeriUpgrade to Linux 6.1.69 (DSA 5593-1)https://tails.net/contribute/Linux_kernel/
To be batched with #20010.https://tails.net/contribute/Linux_kernel/
To be batched with #20010.Tails_5.22groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/20091Upgrade to Linux 6.1.672024-01-08T11:45:58ZintrigeriUpgrade to Linux 6.1.67Tails_5.22groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/16385Research how frequent MAC spoofing failures are2024-01-05T01:34:33Zsajolidasajolida@pimienta.orgResearch how frequent MAC spoofing failures are_Originally created by @sajolida on [#16385 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16385)_
Based on WhisperBack reports.
### Related issues
- **Blocks** tails/tails#16080
- **Blocks** tail..._Originally created by @sajolida on [#16385 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/16385)_
Based on WhisperBack reports.
### Related issues
- **Blocks** tails/tails#16080
- **Blocks** tails/tails#10559
- **Blocks** tails/tails#16260Tails_3.13https://gitlab.tails.boum.org/tails/tails/-/issues/20086Fix regressions introduced in Linux 6.1.662023-12-20T13:20:39ZanonymFix regressions introduced in Linux 6.1.66We just resolved #20072 by merging !1322, but there is a serious issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
However, groente pointed out that "it looks like this only affects the non-free broadcom-sta, so tails sho...We just resolved #20072 by merging !1322, but there is a serious issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
However, groente pointed out that "it looks like this only affects the non-free broadcom-sta, so tails should be unaffected" so we might just skip it.Tails_5.21groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/20072Upgrade to Linux 6.1.662023-12-18T11:07:28ZintrigeriUpgrade to Linux 6.1.66It's been [uploaded](https://tracker.debian.org/news/1482419/accepted-linux-6164-1-source-into-proposed-updates/) to stable-proposed-updates, and should be part of Bookworm 12.3, which is [scheduled](https://release.debian.org/) on 2023-...It's been [uploaded](https://tracker.debian.org/news/1482419/accepted-linux-6164-1-source-into-proposed-updates/) to stable-proposed-updates, and should be part of Bookworm 12.3, which is [scheduled](https://release.debian.org/) on 2023-12-09.
Update: superseded by https://packages.qa.debian.org/l/linux/news/20231209T175632Z.html because 6.1.64 caused ext4 FS corruption.
Update: superseded again by https://packages.qa.debian.org/l/linux/news/20231212T154708Z.html because of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
@anonym as groente's mentor: this is exactly the kind of tasks we had initially agreed on with groente's first steps as a FT helper. And not-quite-incidentally, it's a very good opportunity to learn about how we use our APT snapshots in the build system.
Process: https://tails.net/contribute/Linux_kernel/Tails_5.21groentegroentehttps://gitlab.tails.boum.org/tails/tails/-/issues/20075Ensure Tails 5.x (Bullseye, non-/usr-merged) can load all the firmware we inc...2023-12-18T09:12:51ZintrigeriEnsure Tails 5.x (Bullseye, non-/usr-merged) can load all the firmware we includeThis is a follow-up to #20066: the corresponding MR fixed the FTBFS but did not address the broader underlying issue.This is a follow-up to #20066: the corresponding MR fixed the FTBFS but did not address the broader underlying issue.Tails_5.21anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/9965Adapt our documentation to the deprecation of SD cards2023-12-05T22:16:44Zsajolidasajolida@pimienta.orgAdapt our documentation to the deprecation of SD cards_Originally created by @sajolida on [#9965 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9965)_
See
<https://mailman.boum.org/pipermail/tails-ux/2015-August/000535.html>
Feature Branch: doc/9965
### Su..._Originally created by @sajolida on [#9965 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9965)_
See
<https://mailman.boum.org/pipermail/tails-ux/2015-August/000535.html>
Feature Branch: doc/9965
### Subtasks
- [ ] tails/tails#9790
### Related issues
- **Related to** tails/tails#9884
- **Blocks** tails/tails#13423https://gitlab.tails.boum.org/tails/tails/-/issues/19470Persistent Storage fails to unlock: udevadm settle timeouts2023-11-21T15:34:04ZintrigeriPersistent Storage fails to unlock: udevadm settle timeoutsReported in:
* wb:d3a52ff56c581c1e86799b8c0f1c1873
* wb:7555f488dfb9cf3b007960f53a3f36d2
```
Feb 27 14:07:06 amnesia tps[5848]: INFO:service.py:240: Unlocking Persistent Storage...
Feb 27 14:07:09 amnesia udisksd[3991]: Unlocked device ...Reported in:
* wb:d3a52ff56c581c1e86799b8c0f1c1873
* wb:7555f488dfb9cf3b007960f53a3f36d2
```
Feb 27 14:07:06 amnesia tps[5848]: INFO:service.py:240: Unlocking Persistent Storage...
Feb 27 14:07:09 amnesia udisksd[3991]: Unlocked device /dev/sda2 as /dev/dm-0
[…]
Feb 27 14:07:31 amnesia kernel: applesmc: probe of applesmc.768 failed with error -5
Feb 27 14:07:34 amnesia systemd-udevd[460]: id: Worker [466] processing SEQNUM=3269 is taking a long time
Feb 27 14:08:27 amnesia kernel: applesmc: driver init failed (ret=-5)!
[…]
Feb 27 14:09:06 amnesia tails-greeter.desktop[5833]: [ERROR] persistent_storage.py:83 do_unlock_storage: Error unlocking Persistent Storage: g-io-error-quark: Timeout was reached (24)
Feb 27 14:09:09 amnesia tps[5848]: ERROR:object.py:192: [1] Command '['udevadm', 'settle']' returned non-zero exit status 1.
Feb 27 14:09:09 amnesia tps[5848]: Traceback (most recent call last):
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3/dist-packages/tps/dbus/object.py", line 177, in handle_method_call_inner
Feb 27 14:09:09 amnesia tps[5848]: result = func(*parameters)
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3/dist-packages/tps/service.py", line 248, in Unlock
Feb 27 14:09:09 amnesia tps[5848]: self.do_unlock(passphrase)
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3/dist-packages/tps/service.py", line 259, in do_unlock
Feb 27 14:09:09 amnesia tps[5848]: self._partition.unlock(passphrase)
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3/dist-packages/tps/device.py", line 240, in unlock
Feb 27 14:09:09 amnesia tps[5848]: executil.check_call(["udevadm", "settle"])
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3/dist-packages/tps/executil.py", line 32, in check_call
Feb 27 14:09:09 amnesia tps[5848]: subprocess.check_call(cmd, *args, **kwargs)
Feb 27 14:09:09 amnesia tps[5848]: File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
Feb 27 14:09:09 amnesia tps[5848]: raise CalledProcessError(retcode, cmd)
Feb 27 14:09:09 amnesia tps[5848]: subprocess.CalledProcessError: Command '['udevadm', 'settle']' returned non-zero exit status 1.
```
Maybe `udevadm wait DEV` would be enough for our needs here, without having to assume anything about successful initialization of unrelated drivers?
cc @segfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/19466Improve error message when impossible to create Persistent Storage on some US...2023-11-16T11:37:58Zsajolidasajolida@pimienta.orgImprove error message when impossible to create Persistent Storage on some USB stickWe received 2 reports from different laptops about this in a week:
- wb:195849370ba610d38176c9b4d0904756
* `failed to create Persistent Storage: GDBus.Error:subprocess.CalledProcessError: [...] returned non-zero exit status 32`
* Th...We received 2 reports from different laptops about this in a week:
- wb:195849370ba610d38176c9b4d0904756
* `failed to create Persistent Storage: GDBus.Error:subprocess.CalledProcessError: [...] returned non-zero exit status 32`
* The error happened after entering the passphrase. They also describe the UI remaining in a broken state leading every user interaction to display a popup.
- wb:64784a499495ba90627791e7e06d8b09 (Tails 5.9)
* `failed to create Persistent Storage: GDBus.Error:subprocess.CalledProcessError: [...] returned non-zero exit status 32`
* Had the same error on 4 different USB sticks, leading me to believe that it was not a hardware failure but rather entire categories of USB stick that get this error.
- `GDBus.Error:gi.repository.GLib.Error:udisks-error-quark: GDBus.Error.org.freedesktop.UDusks2.Error.Failed: Error creating partition on /dev/sdb: Failed add partition to device '/dev/sdb'`
"
* Also after entering the passphrase.
* wb:9413123b63e534f22bdc5c0850df8ccf
* wb:daaf97a02b973a9bbf144f3a58d0fb22
* wb:91806c68c0b03fcb1c8052a627f3ac9 (with email address)
I think that we should:
- [ ] Research what kind of USB sticks trigger this error
- [ ] Be more helpful in explaining why the creation failed and what to do next
- [ ] Fallback on a better UI than a popup for thishttps://gitlab.tails.boum.org/tails/tails/-/issues/20004Upgrade to Linux 6.1.552023-10-26T16:06:15ZintrigeriUpgrade to Linux 6.1.55https://tails.net/contribute/Linux_kernel/https://tails.net/contribute/Linux_kernel/Tails_5.19intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/17776GDM error with "Intel Corporation Device [8086:3e98]" (UHD Graphics 630) in t...2023-08-24T19:19:52ZgoupilleGDM error with "Intel Corporation Device [8086:3e98]" (UHD Graphics 630) in troubleshooting modeA user reported that GDM fails to start if Tails is started in Troubleshooting mode when using a core i7-9700 CPU on their ASUS Prime H310T motherboard. If the user chooses the normal mode, then it keeps returning to grub and never actua...A user reported that GDM fails to start if Tails is started in Troubleshooting mode when using a core i7-9700 CPU on their ASUS Prime H310T motherboard. If the user chooses the normal mode, then it keeps returning to grub and never actually start. There is no such issue with the same motherboard equiped with a Celeron G4900.
the user tried the following boot parameters without success :
`xorg-driver=modesetting`
`xorg-driver=intel`
`nomodeset`
`nomodeset xorg-driver=vesa`
though it is a Coffee-lake generation, I wonder if it could be related to #16447goupillegoupillehttps://gitlab.tails.boum.org/tails/tails/-/issues/18254Install printer-driver-brlaser2023-08-24T09:02:27ZanonymInstall printer-driver-brlaserIn WhisperBack 4c8277284f75ba6002f57aadf08ffb80 a user tried adding their Brother HL-1110 printer, but it would only print empty images. [Apparently the `printer-driver-brlaser` package](https://wiki.debian.org/Brother#Laser_printers) co...In WhisperBack 4c8277284f75ba6002f57aadf08ffb80 a user tried adding their Brother HL-1110 printer, but it would only print empty images. [Apparently the `printer-driver-brlaser` package](https://wiki.debian.org/Brother#Laser_printers) contains a proper driver for this printer, and we don't install it yet, so probably the user ended up with a generic driver which just isn't working in this situation. So let's install the proper driver.
And maybe we can consider installing some other `printer-driver-*` packages.hefeehefeehttps://gitlab.tails.boum.org/tails/tails/-/issues/18686Reconsider how "Tails in a VM" fits in our product and engineering strategy2023-07-31T09:32:11ZintrigeriReconsider how "Tails in a VM" fits in our product and engineering strategyWe've historically been discouraging users from using Tails in VMs, and not supporting this use case very actively. The main reasons for this are:
- The host OS is less trustworthy than Tails. Technically it can monitor the user activit...We've historically been discouraging users from using Tails in VMs, and not supporting this use case very actively. The main reasons for this are:
- The host OS is less trustworthy than Tails. Technically it can monitor the user activities that happen inside the Tails VM.
- Technically, traces of the user activities that happen inside the Tails VM can end up on disk (swap) for some time. An adversary could recover them.
I'm wondering:
- How many of our target users actually need protection against the 2 attacks described above.
- How much the (perceived or real) need to reboot, in order to use Tails, is a blocker for user adoption.
My hunch is that many potential users don't need said protection, are not aware of the possibility to use Tails in a VM, and end up using weaker solutions than Tails in a VM. If that's indeed the case, then setting the bar this high may be a disservice to these users and to our mission.
If we were to prioritize use cases differently, and aim at supporting "Tails in a VM" as a first-class use case, this would impact plenty of aspects of the product and of our work:
- We finally have a good solution to offer users whose hardware we don't support.
- If we start producing arm64 images, we could support running Tails in a VM on recent Apple computers (M1).
- Upgrading could happen from the host system: download & verify Tails image, replace your old one with it.
- Persistence may need to move to a different disk, i.e. essentially "boot from ISO + persistent storage on another medium".
- Backup of persistence can be handled from the host system: it's 1 (already encrypted) file to copy somewhere else.
- We would need to invest more into proper VM guest additions support (see discussion on #18666).
- Dealing with captive portals becomes lower priority.
## Research ideas
- [ ] Gather tech data: VT-x (or the AMD equivalent) still used to segment the CPU market
- [ ] Gather hardware compatibility from workshops in ~"D:Sponsor03" (@sajolida)
- [ ] Ask people interviewed as part of ~"D:Sponsor03" (@sajolida)
- [ ] Research hardware compatibility with M1 online
- [ ] Could MVP tricks from startup help us gather more data?
- [ ] Persona analysis: how will this protect our personas better (or worse) than other available tools?
- [ ] Phrase it in terms of new users rather than in terms of users who would prefer a VMTails_5.16sajolidasajolida@pimienta.orgsajolidasajolida@pimienta.orghttps://gitlab.tails.boum.org/tails/tails/-/issues/19709Creating Persistent Storage fails with "Timeout waiting for hardware access" ...2023-07-25T08:50:49ZsegfaultCreating Persistent Storage fails with "Timeout waiting for hardware access" on some hardwareFrom wb:ba432947790d2f718fd2979bd2beb351:
```
May 19 04:09:11 amnesia tps[5735]: INFO:device.py:244: [1] Mounting filesystem
May 19 04:09:11 amnesia wpa_supplicant[3850]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-100
May 19 04:09:11 amnesia ke...From wb:ba432947790d2f718fd2979bd2beb351:
```
May 19 04:09:11 amnesia tps[5735]: INFO:device.py:244: [1] Mounting filesystem
May 19 04:09:11 amnesia wpa_supplicant[3850]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-100
May 19 04:09:11 amnesia kernel: EXT4-fs error (device dm-0): ext4_find_extent:936: inode #8: comm mount: pblk 126910463 bad header/extent: invalid magic - magic 89bf, entries 17898, max 1328(0), depth 37189(0)
May 19 04:09:11 amnesia tps[5735]: mount: /live/persistence/TailsData_unlocked: wrong fs type, bad option, bad superblock on /dev/mapper/TailsData_unlocked, missing codepage or helper program, or other error.
May 19 04:09:11 amnesia kernel: jbd2_journal_init_inode: Cannot locate journal superblock
May 19 04:09:11 amnesia kernel: EXT4-fs (dm-0): Could not load journal inode
May 19 04:09:11 amnesia tps[5735]: ERROR:object.py:193: [1] Command '['mount', '-o', 'acl', '/dev/dm-0', '/live/persistence/TailsData_unlocked']' returned non-zero exit status 32.
May 19 04:09:11 amnesia tps[5735]: Traceback (most recent call last):
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/dbus/object.py", line 178, in handle_method_call_inner
May 19 04:09:11 amnesia tps[5735]: result = func(*parameters)
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/service.py", line 150, in Create
May 19 04:09:11 amnesia tps[5735]: self.do_create(passphrase)
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/service.py", line 160, in do_create
May 19 04:09:11 amnesia tps[5735]: self._partition = Partition.create(job, passphrase)
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/device.py", line 246, in create
May 19 04:09:11 amnesia tps[5735]: cleartext_device.mount()
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/device.py", line 356, in mount
May 19 04:09:11 amnesia tps[5735]: executil.check_call(["mount", "-o", "acl", self.device_path,
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/executil.py", line 49, in check_call
May 19 04:09:11 amnesia tps[5735]: return _run(cmd, *args, **kwargs, check=True)
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3/dist-packages/tps/executil.py", line 33, in _run
May 19 04:09:11 amnesia tps[5735]: p = subprocess.run(cmd, *args, **kwargs)
May 19 04:09:11 amnesia tps[5735]: File "/usr/lib/python3.9/subprocess.py", line 528, in run
May 19 04:09:11 amnesia tps[5735]: raise CalledProcessError(retcode, process.args,
May 19 04:09:11 amnesia tps[5735]: subprocess.CalledProcessError: Command '['mount', '-o', 'acl', '/dev/dm-0', '/live/persistence/TailsData_unlocked']' returned non-zero exit status 32.
```
The system is running on a Dell Latitude E6500 and according to the user, the USB drive has 1 TB capacity. The output of `lsusb` from the bug report says `Integrated Technology Express, Inc. Chipsbank CBM2199 Flash Drive`.
The journal also contains numerous kernel error messages because iwlwifi fails to initialize a device ("Timeout waiting for hardware access") but I assume that's unrelated to the issue this ticket is about.https://gitlab.tails.boum.org/tails/tails/-/issues/5463Support Thunderbolt 3 in a security-conscious way2023-07-20T22:10:16Zimport-from-RedmineSupport Thunderbolt 3 in a security-conscious way_Originally created by Tails on [#5463 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5463)_
Debian Buster supports Thunderbolt in a nice and security-conscious
way:
- <https://christian.kellner.me/2018/04/2..._Originally created by Tails on [#5463 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5463)_
Debian Buster supports Thunderbolt in a nice and security-conscious
way:
- <https://christian.kellner.me/2018/04/23/the-state-of-thunderbolt-3-in-fedora-28/>
- <https://fedoraproject.org/wiki/Changes/ThunderboltEnablement>
Let’s try to make it work in Tails.
Parent Task: tails/tails#5451
### Subtasks
- [x] tails/tails#5850
### Related issues
- **Related to** tails/tails#5547
- **Related to** tails/tails#16749
- **Related to** tails/tails#16755
- [x] **Blocked by** tails/tails#15857Tails_4.0intrigeriintrigeri