tails issueshttps://gitlab.tails.boum.org/tails/tails/-/issues2020-05-15T14:07:44Zhttps://gitlab.tails.boum.org/tails/tails/-/issues/15550Attempting to delete an unlocked persistent volume does not tell the user any...2020-05-15T14:07:44ZalantAttempting to delete an unlocked persistent volume does not tell the user anything useful_Originally created by @alant on [#15550 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15550)_
In
tails-amd64-feature\_14594-asp-gui-3.9-20180420T2055Z-e6f49b3f4f+devel@886427ce28.iso
nightly ISO, “Delete Persiste..._Originally created by @alant on [#15550 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15550)_
In
tails-amd64-feature\_14594-asp-gui-3.9-20180420T2055Z-e6f49b3f4f+devel@886427ce28.iso
nightly ISO, “Delete Persistent Volume” is
broken.
tails-persistence-delete.desktop[10550]: In fun get_variable_from_file: parameter 1 ($file): Reference bless( ["/var/lib/live/config/tails.persistence","/var/lib/l...) did not pass type constraint "Str" at /usr/share/perl5/Tails/Persistence/Setup.pm line 758.
Parent Task: tails/tails#14595Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15544Use title capitalization consistently in persistence configuration2020-05-15T14:07:56Zsajolidasajolida@pimienta.orgUse title capitalization consistently in persistence configuration_Originally created by @sajolida on [#15544 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15544)_
Feature Branch: feature/15544-caps-in-persistence-config
Parent Task: tails/tails#14595_Originally created by @sajolida on [#15544 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15544)_
Feature Branch: feature/15544-caps-in-persistence-config
Parent Task: tails/tails#14595Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15532devel branch FTBFS since virtualbox 5.2.8-dfsg-7 was uploaded to sid2020-05-15T14:08:21Zintrigeridevel branch FTBFS since virtualbox 5.2.8-dfsg-7 was uploaded to sid_Originally created by @intrigeri on [#15532 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15532)_
```
virtualbox (5.2.8-dfsg-7) unstable; urgency=low
.
[ Whoopie ]
* Move dkms rules out to dkms package, ..._Originally created by @intrigeri on [#15532 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15532)_
```
virtualbox (5.2.8-dfsg-7) unstable; urgency=low
.
[ Whoopie ]
* Move dkms rules out to dkms package, but to utils, because
they can be used with modules builtin in the kernel itself
or the guest-source package
.
[ Gianfranco Costamagna ]
* Make the guest-utils depends on dkms not vice-versa
```
Feature Branch: kibi:bugfix/15532-fix-ftbfs-with-newer-virtualbox
### Related issues
- **Related to** tails/tails#12048
- **Blocks** tails/accounting#15139Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15478Revisit GVfs goals for iteration 12020-05-21T12:13:52ZintrigeriRevisit GVfs goals for iteration 1_Originally created by @intrigeri on [#15478 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15478)_
As explained by segfault on https://gitlab.tails.boum.org/tails/tails/-/issues/15218#note_30269:
- supporting v..._Originally created by @intrigeri on [#15478 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15478)_
As explained by segfault on https://gitlab.tails.boum.org/tails/tails/-/issues/15218#note_30269:
- supporting via GVfs ~~the simplest possible kind of VeraCrypt
volumes~~ all kinds of volumes except ones using keyfiles is easy
(or even done)
- supporting via GVfs ~~all other kinds of VeraCrypt~~ unlocking using
keyfiles is much more expensive than expected
One option would be to stop here and require users to use GNOME Disks to
unlock non-trivial VeraCrypt devices.
### Attachments
* [DialogWithOpenDisksButton.png](https://redmine.tails.boum.org/code/attachments/download/1984/DialogWithOpenDisksButton.png)
* [DialogOpenDisksLabelRephrased.png](https://redmine.tails.boum.org/code/attachments/download/1993/DialogOpenDisksLabelRephrased.png)
Parent Task: tails/tails#15214
### Related issues
- **Blocks** tails/tails#15218Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15445Migrate Debian packages we maintain to Salsa2020-05-15T14:14:42ZintrigeriMigrate Debian packages we maintain to Salsa_Originally created by @intrigeri on [#15445 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15445)_
Alioth should be shut down on May 1st. We need to migrate our stuff
before that.
Useful links:
- <https://wiki..._Originally created by @intrigeri on [#15445 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15445)_
Alioth should be shut down on May 1st. We need to migrate our stuff
before that.
Useful links:
- <https://wiki.debian.org/Salsa>
- <https://wiki.debian.org/Salsa/AliothMigration>
- <https://lists.debian.org/debian-devel/2018/03/msg00388.html>
- <https://lists.debian.org/debian-devel/2018/03/msg00266.html>
- recent cme can update Vcs-\* control fields automatically, see the
announce posted on debian-devel a couple weeks ago
We’ve already agreed to keep our mailing list(s) working under the
Alioth list continuation project so this ticket is only about Vcs-Git.
Once you’ve set up a privacy-team on Salsa I’m fine with migrating the
team packages that you’re not maintaining. But if the batch import
scripts work fine I suspect it’s not much more work to migrate all team
packages instead of a subset.Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15430live-additional-software.conf is given wrong permissions when it's updated by...2020-05-19T19:30:12Zbertagazlive-additional-software.conf is given wrong permissions when it's updated by tails-additional-software_Originally created by @bertagaz on [#15430 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15430)_
With an ISO build with 8dd945efef3e4f47f11742862cf34b098ae42cc2
- Boot from USB with network and admin password ..._Originally created by @bertagaz on [#15430 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15430)_
With an ISO build with 8dd945efef3e4f47f11742862cf34b098ae42cc2
- Boot from USB with network and admin password with no configured
persistent storage
- Install a package with APT
- Confirm you want to create the persistent storage
- Enter passphrases and confirm
- Wait for t-p-s to finish and close it
`/media/tails-persistence-setup/TailsData/live-additional-software.conf`
is `0600`
live-persist rightfully detects it’s not 0644 on next boot and disable
ASP.
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15421Improve the implementation of the #15400 bugfix2020-05-15T14:15:59ZintrigeriImprove the implementation of the #15400 bugfix_Originally created by @intrigeri on [#15421 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15421)_
See https://gitlab.tails.boum.org/tails/tails/-/issues/15400#note_22918 and follow ups.
Feature Branch: bug/1..._Originally created by @intrigeri on [#15421 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15421)_
See https://gitlab.tails.boum.org/tails/tails/-/issues/15400#note_22918 and follow ups.
Feature Branch: bug/15400-python-lib-breaks-reproducibility
### Related issues
- **Related to** tails/tails#15400Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15394BitTorrent download title does not render correctly RTL at https://tails.boum...2022-03-16T08:13:49ZemmapeelBitTorrent download title does not render correctly RTL at https://tails.boum.org/install/download/_Originally created by @emmapeel on [#15394 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15394)_
On the Farsi language, the words ‘BitTorrent download’ are overlapped
with the link ‘What is BitTorrent?’.
<https:..._Originally created by @emmapeel on [#15394 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15394)_
On the Farsi language, the words ‘BitTorrent download’ are overlapped
with the link ‘What is BitTorrent?’.
<https://tails.boum.org/install/download/index.fa.html>
The same happens on the weblate arabic version, so I think it is a RTL -
LTR problem:
<http://f3ht2g7n3bmcso7z.onion/install/download.ar.html>
Feature Branch: web/15394-what-is-bittorrent-rtl
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15391Stop shipping python-qt4 that is no longer required2020-05-15T14:18:44ZintrigeriStop shipping python-qt4 that is no longer required_Originally created by @intrigeri on [#15391 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15391)_
Potential regression since tails/tails#15022:
`config/chroot_local-packageslists/tails-common.list` says we instal..._Originally created by @intrigeri on [#15391 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15391)_
Potential regression since tails/tails#15022:
`config/chroot_local-packageslists/tails-common.list` says we install
`python-qt4` to `Enable Electrum's Qt GUI`. I believe it’s wrong since
electrum 3.0.6-1\~bpo9+1 Recommends: python3-pyqt5 and has no dependency
on Qt4.
We should check if we still need this package. If it’s pulled by
something else that needs it anyway, let’s remove it from the list. If
it’s not pulled automatically but we need it, let’s update the comment.
If we don’t need it, let’s remove it from the list.
Feature Branch: bugfix/15391-stop-installing-useless-python-packages
### Related issues
- **Related to** tails/tails#15022
- **Blocks** tails/accounting#15139Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15385"Additional Software" configuration window's title does not match the design ...2020-05-15T14:19:06Zintrigeri"Additional Software" configuration window's title does not match the design and its menu entry_Originally created by @intrigeri on [#15385 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15385)_
On the blueprint and in the apps menu it’s called “Additional Software”.
But the window title is “Additional Softw..._Originally created by @intrigeri on [#15385 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15385)_
On the blueprint and in the apps menu it’s called “Additional Software”.
But the window title is “Additional Software Configuration”. I suspect
that miscrepancy is unintentional.
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15382APT hooks for ASP should be non-blocking2020-05-19T19:30:06ZintrigeriAPT hooks for ASP should be non-blocking_Originally created by @intrigeri on [#15382 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15382)_
The APT package installation currently does not complete until the hook
has returned. I suspect that’s not on purp..._Originally created by @intrigeri on [#15382 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15382)_
The APT package installation currently does not complete until the hook
has returned. I suspect that’s not on purpose and one should add `exec`
to the command line in `DPkg::Pre-Install-Pkgs` and `DPkg::Post-Invoke`.
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15367Release Tails Verification 1.02020-05-15T14:19:58Zsajolidasajolida@pimienta.orgRelease Tails Verification 1.0_Originally created by @sajolida on [#15367 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15367)_
Now that the code is finished, I should release a new version with all
the security enforcement from the last revie..._Originally created by @sajolida on [#15367 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15367)_
Now that the code is finished, I should release a new version with all
the security enforcement from the last review.
Parent Task: tails/tails#12328
### Subtasks
- [x] tails/tails#15366Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15280Reorder persistence features2020-05-15T14:28:32ZintrigeriReorder persistence features_Originally created by @intrigeri on [#15280 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15280)_
See tails/tails#15265 for the desired design.
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/145..._Originally created by @intrigeri on [#15280 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15280)_
See tails/tails#15265 for the desired design.
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-asp-gui, feature/14594-asp-gui
Parent Task: tails/tails#14595
### Related issues
- **Related to** tails/tails#15275
- [x] **Blocked by** tails/tails#15265Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15539Reorder documentation with changes from #152802020-05-15T14:07:10ZemmapeelReorder documentation with changes from #15280_Originally created by @emmapeel on [#15539 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15539)_
There is a new order\!
We need to implement it at
wiki/src/doc/first\_steps/persistence/configure.mdwn
Featur..._Originally created by @emmapeel on [#15539 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15539)_
There is a new order\!
We need to implement it at
wiki/src/doc/first\_steps/persistence/configure.mdwn
Feature Branch: emmapeel:doc-asp/15539-new-order-elements-docs
Parent Task: tails/tails#14589Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15533Clarify the status of Tails Installer for Jessie2020-05-15T14:07:19ZintrigeriClarify the status of Tails Installer for Jessie_Originally created by @intrigeri on [#15533 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15533)_
Our end-user doc says we support Tails Installer on Jessie but we’re
shipping a very old version in jessie-backpor..._Originally created by @intrigeri on [#15533 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15533)_
Our end-user doc says we support Tails Installer on Jessie but we’re
shipping a very old version in jessie-backports (which won’t change as
one cannot upload to jessie-backports a package that’s not in Stretch)
and none in jessie-backports-sloppy. Our installation assistant was
updated for Tails Installer 5.x already (tails/tails#14677) so currently, even if
4.4.6+dfsg-1\~bpo8+1 still works, it does not match our doc.
I think we should either stop supporting Jessie that is:
- remove the package from jessie-backports
- update the installation assistant to require Stretch or newer
- update
<https://tails.boum.org/contribute/release_process/tails-installer/>
accordingly
… or make it so Jessie users can install Tails Installer 5.x (probably
via jessie-backports-sloppy).
Almost a year after the Stretch release, I recommend the former
approach.
Feature Branch: feature/15533-tails-installer-not-in-jessie
### Related issues
- **Related to** tails/tails#14650
- **Related to** tails/tails#14677
- **Related to** tails/tails#12152
- **Blocks** tails/tails#14646
- **Blocks** tails/tails#15411
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15259Add button in tails-persistence-setup to open the configuration interface of ...2018-03-06T14:13:59Zsajolidasajolida@pimienta.orgAdd button in tails-persistence-setup to open the configuration interface of Additional Software_Originally created by @sajolida on [#15259 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15259)_
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-as..._Originally created by @sajolida on [#15259 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15259)_
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-asp-gui, feature/14594-asp-gui
### Attachments
* [power.png](https://redmine.tails.boum.org/code/attachments/download/1875/power.png)
Parent Task: tails/tails#14595
### Related issues
- **Related to** tails/tails#15314Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15588Upgrade to Tor Browser 7.5.42020-05-15T14:07:04ZbertagazUpgrade to Tor Browser 7.5.4_Originally created by @bertagaz on [#15588 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15588)_
<https://people.torproject.org/~boklm/builds/7.5.4-build1/>
Feature Branch: feature/tbb-7.5.4_Originally created by @bertagaz on [#15588 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15588)_
<https://people.torproject.org/~boklm/builds/7.5.4-build1/>
Feature Branch: feature/tbb-7.5.4Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15552Missing sudo in installation instructions for Ubuntu2022-03-16T08:13:50ZemmapeelMissing sudo in installation instructions for Ubuntu_Originally created by @emmapeel on [#15552 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15552)_
Reported by user:
When in <https://tails.boum.org/install/debian/usb/index.en.html>, step
2/6 Install Tails Instal..._Originally created by @emmapeel on [#15552 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15552)_
Reported by user:
When in <https://tails.boum.org/install/debian/usb/index.en.html>, step
2/6 Install Tails Installer for Ubuntu, there is no sudo or Root
terminal mentioned, so when users do
apt install tails-installer
They get stuck with the
error
Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?*
Please review branch.
Feature Branch: emmapeel:doc/15552-sudo_in_apt_instructions
### Related issues
- **Blocks** tails/tails#15411Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15220Iteration 1: Upstream unlocking VeraCrypt partitions in udisks2020-05-15T14:32:45ZsegfaultIteration 1: Upstream unlocking VeraCrypt partitions in udisks_Originally created by @segfault on [#15220 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15220)_
<https://github.com/storaged-project/udisks/pull/495>
Parent Task: tails/tails#15214
### Related issu..._Originally created by @segfault on [#15220 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15220)_
<https://github.com/storaged-project/udisks/pull/495>
Parent Task: tails/tails#15214
### Related issues
- [x] **Blocked by** tails/tails#15215
- **Blocks** tails/tails#15221Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15217Iteration 1: Support unlocking VeraCrypt partitions in Disks2020-05-21T12:13:13ZsegfaultIteration 1: Support unlocking VeraCrypt partitions in Disks_Originally created by @segfault on [#15217 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15217)_
Development repository:
<https://github.com/segfault3/gnome-disk-utility>
Branch: support-tcrypt
### Attac..._Originally created by @segfault on [#15217 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15217)_
Development repository:
<https://github.com/segfault3/gnome-disk-utility>
Branch: support-tcrypt
### Attachments
* [attempt_to_unlock_veracrypt_truecrypt_volume.png](https://redmine.tails.boum.org/code/attachments/download/1890/attempt_to_unlock_veracrypt_truecrypt_volume.png)
* [attempt_to_unlock_veracrypt_volume.png](https://redmine.tails.boum.org/code/attachments/download/1891/attempt_to_unlock_veracrypt_volume.png)
* [attempt_to_unlock_volume.png](https://redmine.tails.boum.org/code/attachments/download/1892/attempt_to_unlock_volume.png)
* [unlocked_volume.png](https://redmine.tails.boum.org/code/attachments/download/1893/unlocked_volume.png)
Parent Task: tails/tails#15214Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/15537Document better how to test WhisperBack2020-05-15T14:09:27Zsajolidasajolida@pimienta.orgDocument better how to test WhisperBack_Originally created by @sajolida on [#15537 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15537)_
Some information is missing from the current README:
- Build dependencies
- Explain how to run from source cod..._Originally created by @sajolida on [#15537 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15537)_
Some information is missing from the current README:
- Build dependencies
- Explain how to run from source code
Feature Branch: feature/15537-test-whisperback
### Related issues
- [x] **Blocked by** tails/tails#15440Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15534Update tails-bugs@boum.org OpenPGP key2020-05-15T14:09:31ZintrigeriUpdate tails-bugs@boum.org OpenPGP key_Originally created by @intrigeri on [#15534 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15534)_
It expires on 2018-07-23 and we support upgrading from N-2 so we must
ensure Tails 3.7 includes an updated key.
..._Originally created by @intrigeri on [#15534 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15534)_
It expires on 2018-07-23 and we support upgrading from N-2 so we must
ensure Tails 3.7 includes an updated key.
Feature Branch: bugfix/15534-update-tails-bugs-openpgp-key
### Related issues
- **Blocks** tails/accounting#15139Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15525Include vendor and product ID in WhisperBack reports2020-05-15T14:09:59Zsajolidasajolida@pimienta.orgInclude vendor and product ID in WhisperBack reports_Originally created by @sajolida on [#15525 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15525)_
Right now tails-debugging-info includes `lspci`.
I propose it to run `lspci -nn` to include the vendor and product..._Originally created by @sajolida on [#15525 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15525)_
Right now tails-debugging-info includes `lspci`.
I propose it to run `lspci -nn` to include the vendor and product ID in
the output.
The GDM debugging message from tails/tails#14521 runs `lspci -nn`.
It should make the output of the GDM debugging message and WhisperBack
reports exactly the same and help maintaining
/support/known\_issues/gdm.
Feature Branch: feature/15525-device-id-in-wbTails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15485Automatic upgrades from 3.6.1 to 3.6.2 not working2020-05-15T14:11:47ZemmapeelAutomatic upgrades from 3.6.1 to 3.6.2 not working_Originally created by @emmapeel on [#15485 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15485)_
Many users report that they cannot automatically upgrade from Tails
3.6.1 to 3.6.2
The error
says:
"Could..._Originally created by @emmapeel on [#15485 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15485)_
Many users report that they cannot automatically upgrade from Tails
3.6.1 to 3.6.2
The error
says:
"Could not determine whether an upgrade is available from our website.
Check your network connection, and restart Tails to try upgrading again.
If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html
For debugging information, execute the following command: sudo tails-debugging-info"
### And BINGO\!
when running tails-upgrade-frontend-wrapper from the terminal I
see:
Invalid signature at /usr/bin/tails-iuk-get-upgrade-description-file line 18.
at /usr/bin/tails-upgrade-frontend line 19.Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15467Cannot update backups of LimeSurvey2020-05-15T14:12:53Zsajolidasajolida@pimienta.orgCannot update backups of LimeSurvey_Originally created by @sajolida on [#15467 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15467)_
In my note and in the Puppet configuration I see:
/usr/sbin/backupninja --now --debug --run /etc/backup.d/10.m..._Originally created by @sajolida on [#15467 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15467)_
In my note and in the Puppet configuration I see:
/usr/sbin/backupninja --now --debug --run /etc/backup.d/10.mysql
But when executing this, either as `sajolida` or as `www-data` I get the
following error message:
/usr/sbin/backupninja --now --debug --run /etc/backup.d/10.mysql
Parent Task: tails/sysadmin#14540
### Related issues
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15455Synaptic error on open2020-05-15T14:13:26ZalantSynaptic error on open_Originally created by @alant on [#15455 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15455)_
Synptic error after updating cache : `W: Problem unlinking the file
lists - Clean (21: Is a directory)`
Paren..._Originally created by @alant on [#15455 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15455)_
Synptic error after updating cache : `W: Problem unlinking the file
lists - Clean (21: Is a directory)`
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15443Mangled URLs or mirror when retrying after verification failure2018-03-28T18:05:25Zsajolidasajolida@pimienta.orgMangled URLs or mirror when retrying after verification failure_Originally created by @sajolida on [#15443 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15443)_
Steps to reproduce:
1. Visit <https://tails.boum.org/install/download>.
2. Install Tails Verification.
3. Verif..._Originally created by @sajolida on [#15443 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15443)_
Steps to reproduce:
1. Visit <https://tails.boum.org/install/download>.
2. Install Tails Verification.
3. Verify a dummy file to get a verification failure.
4. Click on “Please try to download again…”
5. You get a 404 error which comes from a mangled URL returned by
replaceUrlPrefixWithRandomMirror.
See screenshot in attachment.
Feature Branch: web/15443-mangled-urls-on-download-retry
### Attachments
* [mangled.png](https://redmine.tails.boum.org/code/attachments/download/1939/mangled.png)
Parent Task: tails/tails#12328Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15440Missing WhisperBack 1.7.14 in Git2020-05-15T14:13:58ZintrigeriMissing WhisperBack 1.7.14 in Git_Originally created by @intrigeri on [#15440 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15440)_
Please push 1.7.14 (commits + tag) to Git.
### Related issues
- **Blocks** tails/tails#13198
- *..._Originally created by @intrigeri on [#15440 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15440)_
Please push 1.7.14 (commits + tag) to Git.
### Related issues
- **Blocks** tails/tails#13198
- **Blocks** tails/tails#11272
- **Blocks** tails/tails#7797
- **Blocks** tails/tails#13299
- **Blocks** tails/tails#15537Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15431tails-synchronize-data-to-new-persistent-volume-on-shutdown.service does not ...2020-05-15T14:14:21Zbertagaztails-synchronize-data-to-new-persistent-volume-on-shutdown.service does not save APT cache at the right place_Originally created by @bertagaz on [#15431 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15431)_
In t-p-s, the `/live/persistence/TailsData_unlocked/apt/cache/` is used
to store the APT cache, to be mounted on `/..._Originally created by @bertagaz on [#15431 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15431)_
In t-p-s, the `/live/persistence/TailsData_unlocked/apt/cache/` is used
to store the APT cache, to be mounted on `/var/cache/apt/archives/`.
But at `tails-synchronize-data-to-new-persistent-volume.service` copy
the APT cache into `/live/persistence/TailsData_unlocked/apt/archives/`,
so the ASP offline feature is broken.
Parent Task: tails/tails#14594Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15413Documentation contains screenshot of menu with irregular spacing2020-05-15T14:15:24ZsegfaultDocumentation contains screenshot of menu with irregular spacing_Originally created by @segfault on [#15413 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15413)_
The screenshot of the ~~status menu~~ ~~GNOME User menu~~ ~~system
menu~~ whatever you wanna call it, shows the men..._Originally created by @segfault on [#15413 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15413)_
The screenshot of the ~~status menu~~ ~~GNOME User menu~~ ~~system
menu~~ whatever you wanna call it, shows the menu as affected by
tails/tails#15377. The screenshot should be updated.
Feature Branch: doc/15413-screen-locker-spacing
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15462Purpose of the search box in the documentation browser is unclear2020-05-15T14:15:24ZemmapeelPurpose of the search box in the documentation browser is unclear_Originally created by @emmapeel on [#15462 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15462)_
Steps to reproduce:
\- Disconnect Internet
\- Click on the Documentation link on Desktop
\- Use the searchbox o..._Originally created by @emmapeel on [#15462 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15462)_
Steps to reproduce:
\- Disconnect Internet
\- Click on the Documentation link on Desktop
\- Use the searchbox on top
Feature Branch: segfault:bugfix/15462-fix-search-boxTails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15456Upgrade Linux to 4.15.0-22020-05-19T19:30:07ZintrigeriUpgrade Linux to 4.15.0-2_Originally created by @intrigeri on [#15456 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15456)_
Our devel branch FTBFS since Linux 4.15.0-1 was removed from sid. Let’s
fix this on devel first and this will give..._Originally created by @intrigeri on [#15456 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15456)_
Our devel branch FTBFS since Linux 4.15.0-1 was removed from sid. Let’s
fix this on devel first and this will give us data points wrt. tails/tails#15435.
### Related issues
- **Blocks** tails/tails#13245
- [x] **Blocked by** tails/tails#15457Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15441Document that Tails Verification doesn't work in Tails 3.6 and 3.6.12022-03-16T08:24:06Zsajolidasajolida@pimienta.orgDocument that Tails Verification doesn't work in Tails 3.6 and 3.6.1_Originally created by @sajolida on [#15441 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15441)_
Feature Branch: doc/15434-verification-extension-broken-in-3.6
Parent Task: tails/tails#15434
### R..._Originally created by @sajolida on [#15441 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15441)_
Feature Branch: doc/15434-verification-extension-broken-in-3.6
Parent Task: tails/tails#15434
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15386Confusing UX due to Additional Software configuration GUI not refreshing pack...2020-05-15T14:18:27ZintrigeriConfusing UX due to Additional Software configuration GUI not refreshing packages list_Originally created by @intrigeri on [#15386 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15386)_
Steps to reproduce:
1. Start “Additional Software” from the apps menu
2. The list is empty so I follow the inst..._Originally created by @intrigeri on [#15386 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15386)_
Steps to reproduce:
1. Start “Additional Software” from the apps menu
2. The list is empty so I follow the instructions, click on the
Synaptic “link” in the window to add packages.
3. In Synaptic I install a package
4. I get asked whether I want that package to be installed
automatically when I start Tails, and I say yay\!
5. I close Synaptic and I’m thus back in the “Additional Software”
window which is back on top. But the list in there is still empty:
my newly added package is not listed and I wonder if the operation
has failed.
6. I verify that the package was correctly added to
`live-additional-software.conf`.
I think step 5 is confusing: after completing the operation (adding a
package to my ASP as instructed) I would expect the window that told me
to do so to give me up-to-date info. I suspect the same problem exists
even if the list is not empty to start with.
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15438Add testing Tails Verification to the manual test suite2020-05-15T14:16:58Zsajolidasajolida@pimienta.orgAdd testing Tails Verification to the manual test suite_Originally created by @sajolida on [#15438 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15438)_
Feature Branch: contrib/15438-manual-tests-for-verification-extension
Parent Task: tails/tails#12328_Originally created by @sajolida on [#15438 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15438)_
Feature Branch: contrib/15438-manual-tests-for-verification-extension
Parent Task: tails/tails#12328Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15435Consider upgrading Linux in Tails 3.72020-05-15T14:38:08ZintrigeriConsider upgrading Linux in Tails 3.7_Originally created by @intrigeri on [#15435 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15435)_
### Related issues
- **Related to** tails/tails#15457
- **Related to** tails/tails#15554
- **..._Originally created by @intrigeri on [#15435 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15435)_
### Related issues
- **Related to** tails/tails#15457
- **Related to** tails/tails#15554
- **Related to** tails/tails#15436
- **Blocks** tails/accounting#15139Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15380ASP proposes me to add packages upgraded with Synaptic to my additional software2020-05-15T14:18:42ZintrigeriASP proposes me to add packages upgraded with Synaptic to my additional software_Originally created by @intrigeri on [#15380 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15380)_
I’ve started a Tails with persistence built from our topic branch,
started Synaptic, which showed me its “upgradab..._Originally created by @intrigeri on [#15380 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15380)_
I’ve started a Tails with persistence built from our topic branch,
started Synaptic, which showed me its “upgradable” screen. Two packages
were listed there: `tor` and `tor-geoipdb`. I felt encouraged to accept
Synaptic’s proposal so I clicked “Mark All Upgrades” and then “Apply”.
Synaptic upgraded these two packages and then a notification popped up
saying “Add tor-geoipdb tor to your additional software?”. Note that
these two packages were *already* installed earlier, all what happened
was an *upgrade*. I suspect that we’re comparing versions, and not only
package names, when we identify candidate packages for adding to ASP
upon APT operations.
Parent Task: tails/tails#14594Tails_3.7alantalanthttps://gitlab.tails.boum.org/tails/tails/-/issues/15432Tails Installer sometimes fails when setting partition type during (since Tai...2022-03-16T08:19:49ZemmapeelTails Installer sometimes fails when setting partition type during (since Tails 3.6?)_Originally created by @emmapeel on [#15432 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15432)_
Some users are reporting errors when trying to install or upgrade with
Tails Installer. I still don’t have much inf..._Originally created by @emmapeel on [#15432 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15432)_
Some users are reporting errors when trying to install or upgrade with
Tails Installer. I still don’t have much information but the errors can
be:
When installing to a new USB:
Partitionnement du périphérique /dev/sdd
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Partition' on object at path /org/freedesktop/UDisks2/block_devices/sdd1 (19)
L'installation de Tails a échoué !
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Partition' on object at path /org/freedesktop/UDisks2/block_devices/sdd1 (19)
Another log about a similar issue (note that `/dev/sdb` had no partition
nor FS
initially):
2018-04-01 11:13:11,060 [creator.py:856 (partition_device)] INFO: Speichermedium /dev/sdb wird partitioniert
2018-04-01 11:13:11,060 [creator.py:859 (partition_device)] DEBUG: Creating partition table
2018-04-01 11:13:13,565 [creator.py:879 (partition_device)] DEBUG: Creating partition
2018-04-01 11:13:14,169 [creator.py:279 (popen)] DEBUG: sync
2018-04-01 11:13:19,230 [creator.py:279 (popen)] DEBUG: sync
2018-04-01 11:13:25,426 [gui.py:264 (run)] ERROR: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Partition' on object at path /org/freedesktop/UDisks2/block_devices/sdb1 (19)
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 203, in run
self.live.partition_device()
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 924, in partition_device
system_partition.call_set_type_sync(ESP_GUID, GLib.Variant('a{sv}', None))
Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Partition' on object at path /org/freedesktop/UDisks2/block_devices/sdb1 (19)
2018-04-01 11:13:25,428 [gui.py:265 (run)] DEBUG: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 203, in run
self.live.partition_device()
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 924, in partition_device
system_partition.call_set_type_sync(ESP_GUID, GLib.Variant('a{sv}', None))
Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Partition' on object at path /org/freedesktop/UDisks2/block_devices/sdb1 (19)
Feature Branch: installer:bugfix/15432-installer-robustness, bugfix/15432-installer-robustness
### Related issues
- **Blocks** tails/accounting#15139Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15426Update the SquashFS sort file for Linux 4.15 and other Tails 3.6 changes2020-05-15T14:17:25ZintrigeriUpdate the SquashFS sort file for Linux 4.15 and other Tails 3.6 changes_Originally created by @intrigeri on [#15426 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15426)_
Apparently this step of the release process was skipped during the 3.6
release (noticed this because all kernel mo..._Originally created by @intrigeri on [#15426 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15426)_
Apparently this step of the release process was skipped during the 3.6
release (noticed this because all kernel modules are badly sorted).
Let’s ensure this does not happen for 3.7.Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15423Clarify unspecified items of the interface2020-05-15T14:17:27Zsajolidasajolida@pimienta.orgClarify unspecified items of the interface_Originally created by @sajolida on [#15423 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15423)_
See 5d8edf990a and 555cf22ea3.
Parent Task: tails/tails#14594_Originally created by @sajolida on [#15423 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15423)_
See 5d8edf990a and 555cf22ea3.
Parent Task: tails/tails#14594Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15061Document the relevant security aspects of the Tails Verification / Installati...2020-05-15T14:44:20Zsajolidasajolida@pimienta.orgDocument the relevant security aspects of the Tails Verification / Installation Assistant_Originally created by @sajolida on [#15061 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15061)_
<https://mailman.boum.org/pipermail/tails-dev/2017-November/011916.html>
« Once we’re done here, I’d like to see t..._Originally created by @sajolida on [#15061 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15061)_
<https://mailman.boum.org/pipermail/tails-dev/2017-November/011916.html>
« Once we’re done here, I’d like to see the security reasoning that
leads to the “it’s safe” conclusion documented somewhere in the
extension Git repo: we want our code to be friendly to auditors, and
mailing list archive are not an obvious place to find such doc.
@sajolida: I volunteer to take care of this if Uzair does not. »
Feature Branch: contrib/15061-document-security-of-verification-extension
Parent Task: tails/tails#12328
### Related issues
- **Related to** tails/tails#14815Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15399Write https://tails.boum.org/gdm2020-05-15T14:20:44Zsajolidasajolida@pimienta.orgWrite https://tails.boum.org/gdm_Originally created by @sajolida on [#15399 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15399)_
Pointed to from
config/chroot\_local-includes/lib/systemd/system/tails-gdm-failed-to-start.service.
Feature Br..._Originally created by @sajolida on [#15399 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15399)_
Pointed to from
config/chroot\_local-includes/lib/systemd/system/tails-gdm-failed-to-start.service.
Feature Branch: doc/15399-gdm-debugging
### Related issues
- **Blocks** tails/tails#15411Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15320Have the aufs regression since Linux 4.14 fixed upstream2020-05-15T14:22:41ZintrigeriHave the aufs regression since Linux 4.14 fixed upstream_Originally created by @intrigeri on [#15320 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15320)_
On <https://bugs.debian.org/886329> we’re asked to provide more info so
the bug can be forwarded upstream.
Our wo..._Originally created by @intrigeri on [#15320 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15320)_
On <https://bugs.debian.org/886329> we’re asked to provide more info so
the bug can be forwarded upstream.
Our workaround is ugly, makes UX poor, and confused users overload our
help desk.
### Related issues
- **Blocks** tails/tails#13245
- **Blocks** tails/tails#15339Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15046Support unlocking with VeraCrypt keyfiles in udisks2020-05-15T14:45:13ZsegfaultSupport unlocking with VeraCrypt keyfiles in udisks_Originally created by @segfault on [#15046 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15046)_
During the UX sprint we decided that we must support unlocking with
keyfiles, because it is an often used feature (..._Originally created by @segfault on [#15046 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15046)_
During the UX sprint we decided that we must support unlocking with
keyfiles, because it is an often used feature (43% of survey
participants).
This is already supported by cryptsetup, so we will have to patch
libblockdev and udisks for this.
Parent Task: tails/tails#6337Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/15314Replace custom widget button in persistent wizard with standard GNOME switches2018-03-05T15:34:13Zsajolidasajolida@pimienta.orgReplace custom widget button in persistent wizard with standard GNOME switches_Originally created by @sajolida on [#15314 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15314)_
Currently the persistent storage configuration relies on custom widgets
to activate each feature: a button with a p..._Originally created by @sajolida on [#15314 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15314)_
Currently the persistent storage configuration relies on custom widgets
to activate each feature: a button with a persistent state and a tick
mark, acting like a switch.
Newest settings in GNOME all rely on a different pattern: a vertical
list of options with corresponding widgets on the right to activate or
configure them. See “power.png” screenshot from Tails 3.5. This tendency
continues in newest versions of GNOME.
I’m attaching a rewrite of the persistent storage configuration using
this pattern.
As part of the work on Additional Software, using this pattern makes it
easier to add a “Configure” button that goes together with the
“Additional Software” feature. With the current design we would have
to either add a button inside the button of the feature or use a link
inside the button.
Not a break dealer but probably with a poorer usability and clearly not
going in the direction of newest GNOME
interfaces.
See:
![](https://raw.githubusercontent.com/sajolida/tails-wireframes/master/additional%20software/png/persistent%20storage%20-%20configuration%20changed.png)
That would be an important improvement on tails/tails#15259 for SponsorW.
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-asp-gui, feature/14594-asp-gui
Parent Task: tails/tails#14595
### Related issues
- **Related to** tails/tails#15259Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15366Test the verification extension in Firefox 60 beta2020-05-15T14:22:50Zsajolidasajolida@pimienta.orgTest the verification extension in Firefox 60 beta_Originally created by @sajolida on [#15366 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15366)_
Firefox 60 will be the next ESR. It will be released as a beta on
2018-03-13.
And create a ticket for the next ESR..._Originally created by @sajolida on [#15366 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15366)_
Firefox 60 will be the next ESR. It will be released as a beta on
2018-03-13.
And create a ticket for the next ESR.
Parent Task: tails/tails#15367Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15037Have plans to release our VeraCrypt work in Tails2020-05-15T14:46:32Zsajolidasajolida@pimienta.orgHave plans to release our VeraCrypt work in Tails_Originally created by @sajolida on [#15037 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15037)_
Our work on VeraCrypt will likely:
- Affect many Debian packages (libblockdev, udisks,
gnome-disk-utility, g..._Originally created by @sajolida on [#15037 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15037)_
Our work on VeraCrypt will likely:
- Affect many Debian packages (libblockdev, udisks,
gnome-disk-utility, gvfs, libgtk, gnome-shell)
- Be based on the development version of these packages. For example,
the dialog to format a partition in Disks has been rewritten since
the version in Debian Stretch.
- As a consequence, not be easy to backport in Debian Stretch.
So we could take different approaches to have our changes land in Tails:
- A. Create backports our changes to make them work in Debian Stretch
and maintain these backports during the Stretch cycle. But I don’t
see this being considered in the budget.
- B. Build custom packages of our changes to have them in Tails only
and maintain these custom packages during the Stretch cycle.
- C. Build custom packages and only use them in a beta version for
user testing and community feedback. Then wait until Tails is based
on Debian testing or Stretch to have them in Tails. That would
change our plans regarding the delivery of these changes in our
official version.
We discussed this with u and segfault during the sprint but felt like we
needed some insight from intrigeri regarding what would be best to do,
both as our high level manager and as the one behind tails/tails#12615, because
having Tails based on Debian testing would solve this but we understand
that we can’t rely on this.
intrigeri: Did you had something in mind for that already that we
missed?
Parent Task: tails/tails#14468Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15031Installing to a device that previously had an hybrid ISO copied to it is fragile2020-05-21T12:17:08ZintrigeriInstalling to a device that previously had an hybrid ISO copied to it is fragile_Originally created by @intrigeri on [#15031 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15031)_
I don’t know if it’s a bug in Tails Installer or in our test suite. The
attached screenshot reads: “‘NoneType’ obj..._Originally created by @intrigeri on [#15031 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15031)_
I don’t know if it’s a bug in Tails Installer or in our test suite. The
attached screenshot reads: “‘NoneType’ object has no attribute
‘props’”.
```
Scenario: Writing a Tails isohybrid to a USB drive and booting it, then installing Tails on top of it using Tails Installer, and it still boots # features/usb_install.feature:104
Given a computer # features/step_definitions/common_steps.rb:46
And I temporarily create a 7200 MiB disk named "isohybrid" # features/step_definitions/common_steps.rb:59
00:57:05.550577319: libguestfs: trace: set_autosync true
00:57:05.550726607: libguestfs: trace: set_autosync = 0
00:57:05.550802746: libguestfs: trace: add_drive "/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable-3.3.1-20171209T0717Z-15ff263293.iso" "readonly:true" "format:raw"
00:57:05.550875146: libguestfs: trace: get_tmpdir
00:57:05.550926565: libguestfs: trace: get_tmpdir = "/tmp/TailsToaster"
00:57:05.551154663: libguestfs: trace: disk_create "/tmp/TailsToaster/libguestfs0rfoWs/overlay1" "qcow2" -1 "backingfile:/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable-3.3.1-20171209T0717Z-15ff263293.iso" "backingformat:raw"
00:57:05.579030575: libguestfs: trace: disk_create = 0
00:57:05.579201015: libguestfs: trace: add_drive = 0
00:57:05.579284348: libguestfs: trace: add_drive "/tmp/TailsToaster/TailsToasterStorage/isohybrid" "format:qcow2"
00:57:05.579569412: libguestfs: trace: add_drive = 0
00:57:05.579633214: libguestfs: trace: launch
00:57:05.579713084: libguestfs: trace: get_backend_setting "force_tcg"
00:57:05.579798129: libguestfs: trace: get_backend_setting = NULL (error)
00:57:05.580110985: libguestfs: trace: get_cachedir
00:57:05.580174768: libguestfs: trace: get_cachedir = "/tmp/TailsToaster"
00:57:05.622928849: libguestfs: trace: get_cachedir
00:57:05.623092760: libguestfs: trace: get_cachedir = "/tmp/TailsToaster"
00:57:05.623441255: libguestfs: trace: get_sockdir
00:57:05.623552604: libguestfs: trace: get_sockdir = "/tmp"
00:57:05.623736442: libguestfs: trace: get_backend_setting "gdb"
00:57:05.623814286: libguestfs: trace: get_backend_setting = NULL (error)
00:57:09.872461138: libguestfs: trace: launch = 0
00:57:09.873668738: libguestfs: trace: list_devices
00:57:09.874559509: libguestfs: trace: list_devices = ["/dev/sda", "/dev/sdb"]
00:57:09.874697398: libguestfs: trace: copy_device_to_device "/dev/sda" "/dev/sdb"
00:57:13.280787443: libguestfs: trace: copy_device_to_device = 0
00:57:13.281530238: libguestfs: trace: close
00:57:13.281751741: libguestfs: trace: internal_autosync
00:57:13.285347754: libguestfs: trace: internal_autosync = 0
And I write the Tails ISO image to disk "isohybrid" # features/step_definitions/untrusted_partitions.rb:30
00:57:15.511200761: [log] CLICK on L(1023,384)@S(0)[0,0 1024x768]
00:57:18.464493348: [log] TYPE " autotest_never_use_this_option blacklist=psmouse #ENTER."
00:58:31.329441732: calling as root: echo 'hello?'
00:58:31.580749618: call returned: [0, "hello?\n", ""]
00:58:31.581234839: calling as root: service tor status
00:58:31.886917552: call returned: [3, "â— tor.service - Anonymizing overlay network for TCP (multi-instance-master)\n Loaded: loaded (/lib/systemd/system/tor.service; disabled; vendor preset: enabled)\n Active: inactive (dead)\n", ""]
00:58:31.887399714: opening file /etc/tor/torrc in 'append' mode
00:58:32.117561470: append complete
00:58:32.914113117: [log] CLICK on L(767,159)@S(0)[0,0 1024x768]
00:58:32.914711994: calling as root: loginctl
00:58:33.164239184: call returned: [0, " SESSION UID USER SEAT TTY \n c1 150 Debian-gdm seat0 /dev/tty1 \n\n1 sessions listed.\n", ""]
00:58:34.164964513: calling as root: loginctl
00:58:34.388422846: call returned: [0, " SESSION UID USER SEAT TTY \n 5 1000 amnesia seat0 /dev/tty2 \n c1 150 Debian-gdm seat0 /dev/tty1 \n\n2 sessions listed.\n", ""]
00:58:52.641655215: calling as amnesia: gsettings set org.gnome.desktop.session idle-delay 0
00:58:52.859365047: call returned: [0, "", ""]
00:58:52.859694847: calling as amnesia: gsettings set org.gnome.desktop.interface toolkit-accessibility true
00:58:53.020689674: call returned: [0, "", ""]
00:58:53.021051002: executing Python as amnesia:
import dogtail.config
import dogtail.tree
import dogtail.predicate
dogtail.config.logDebugToFile = False
dogtail.config.logDebugToStdOut = False
dogtail.config.blinkOnActions = True
dogtail.config.searchShowingOnly = True
node133 = dogtail.tree.root.application('gnome-shell')
00:58:54.380157294: execution complete
00:58:55.107919556: executing Python as amnesia: node134 = node133.child('No Notifications', roleName='label')
00:58:55.137823667: [log] CLICK on L(512,10)@S(0)[0,0 1024x768]
00:58:56.930571727: execution complete
00:58:56.930787423: executing Python as amnesia: node135 = node133.child('No Notifications', roleName='label')
00:58:58.358828894: execution complete
00:58:58.401186412: [log] TYPE "#ESC."
And I start Tails from USB drive "isohybrid" with network unplugged and I login # features/step_definitions/common_steps.rb:137
00:58:58.404163065: calling as root: udevadm info --device-id-of-file=/lib/live/mount/medium
00:58:58.696822251: call returned: [0, "8:1\n", ""]
00:58:58.697011300: calling as root: readlink -f /dev/block/'8:1'
00:58:59.062760544: call returned: [0, "/dev/sda1\n", ""]
00:58:59.062958109: calling as root: udevadm info --query=property --name='/dev/sda1'
00:58:59.453972185: call returned: [0, "DEVLINKS=/dev/disk/by-path/pci-0000:02:00.0-usb-0:2:1.0-scsi-0:0:0:0-part1 /dev/disk/by-id/usb-QEMU_QEMU_HARDDISK_1-0000:00:01.1:00.0-2-0:0-part1 /dev/disk/by-uuid/2017-11-15-12-11-29-00 /dev/disk/by-partuuid/0000002a-01 /dev/disk/by-label/TAILS\\x203.3.1\\x20-\\x2020171115\nDEVNAME=/dev/sda1\nDEVPATH=/devices/pci0000:00/0000:00:01.1/0000:02:00.0/usb2/2-2/2-2:1.0/host6/target6:0:0/6:0:0:0/block/sda/sda1\nDEVTYPE=partition\nID_BUS=usb\nID_DRIVE_DETACHABLE=0\nID_FS_APPLICATION_ID=THE\\x20AMNESIC\\x20INCOGNITO\\x20LIVE\\x20SYSTEM\nID_FS_BOOT_SYSTEM_ID=EL\\x20TORITO\\x20SPECIFICATION\nID_FS_LABEL=TAILS_3.3.1_-_20171115\nID_FS_LABEL_ENC=TAILS\\x203.3.1\\x20-\\x2020171115\nID_FS_PUBLISHER_ID=HTTPS:\\x2f\\x2fTAILS.BOUM.ORG\\x2f\nID_FS_TYPE=iso9660\nID_FS_USAGE=filesystem\nID_FS_UUID=2017-11-15-12-11-29-00\nID_FS_UUID_ENC=2017-11-15-12-11-29-00\nID_FS_VERSION=Joliet Extension\nID_INSTANCE=0:0\nID_MODEL=QEMU_HARDDISK\nID_MODEL_ENC=QEMU\\x20HARDDISK\\x20\\x20\\x20\nID_MODEL_ID=0001\nID_PART_ENTRY_DISK=8:0\nID_PART_ENTRY_FLAGS=0x80\nID_PART_ENTRY_NUMBER=1\nID_PART_ENTRY_OFFSET=0\nID_PART_ENTRY_SCHEME=dos\nID_PART_ENTRY_SIZE=2377620\nID_PART_ENTRY_TYPE=0x17\nID_PART_ENTRY_UUID=0000002a-01\nID_PART_TABLE_TYPE=dos\nID_PART_TABLE_UUID=0000002a\nID_PATH=pci-0000:02:00.0-usb-0:2:1.0-scsi-0:0:0:0\nID_PATH_TAG=pci-0000_02_00_0-usb-0_2_1_0-scsi-0_0_0_0\nID_REVISION=2.5+\nID_SERIAL=QEMU_QEMU_HARDDISK_1-0000:00:01.1:00.0-2-0:0\nID_SERIAL_SHORT=1-0000:00:01.1:00.0-2\nID_TYPE=disk\nID_USB_DRIVER=usb-storage\nID_USB_INTERFACES=:080650:\nID_USB_INTERFACE_NUM=00\nID_VENDOR=QEMU\nID_VENDOR_ENC=QEMU\\x20\\x20\\x20\\x20\nID_VENDOR_ID=46f4\nMAJOR=8\nMINOR=1\nPARTN=1\nSUBSYSTEM=block\nTAGS=:systemd:\nUDISKS_IGNORE=1\nUDISKS_SYSTEM=1\nUSEC_INITIALIZED=6800938\n", ""]
00:58:59.454296650: calling as root: udevadm info --device-id-of-file=/lib/live/mount/medium
00:58:59.672356551: call returned: [0, "8:1\n", ""]
00:58:59.672547437: calling as root: readlink -f /dev/block/'8:1'
00:58:59.938788418: call returned: [0, "/dev/sda1\n", ""]
Then Tails is running from USB drive "isohybrid" # features/step_definitions/usb.rb:390
00:59:00.009208548: spawning as root: poweroff
When I shutdown Tails and wait for the computer to power off # features/step_definitions/common_steps.rb:530
00:59:11.180385404: [log] CLICK on L(1023,384)@S(0)[0,0 1024x768]
00:59:14.302285520: [log] TYPE " autotest_never_use_this_option blacklist=psmouse #ENTER."
01:00:21.685616292: calling as root: echo 'hello?'
01:00:21.949790648: call returned: [0, "hello?\n", ""]
01:00:21.950308176: calling as root: service tor status
01:00:22.245776433: call returned: [3, "â— tor.service - Anonymizing overlay network for TCP (multi-instance-master)\n Loaded: loaded (/lib/systemd/system/tor.service; disabled; vendor preset: enabled)\n Active: inactive (dead)\n", ""]
01:00:22.246294696: opening file /etc/tor/torrc in 'append' mode
01:00:22.443410316: append complete
01:00:23.231986449: calling as root: loginctl
01:00:23.252455366: [log] CLICK on L(767,159)@S(0)[0,0 1024x768]
01:00:23.474391981: call returned: [0, " SESSION UID USER SEAT TTY \n c1 150 Debian-gdm seat0 /dev/tty1 \n\n1 sessions listed.\n", ""]
01:00:24.474871169: calling as root: loginctl
01:00:24.679676655: call returned: [0, " SESSION UID USER SEAT TTY \n c1 150 Debian-gdm seat0 /dev/tty1 \n 5 1000 amnesia seat0 /dev/tty2 \n\n2 sessions listed.\n", ""]
01:00:41.360845473: calling as amnesia: gsettings set org.gnome.desktop.session idle-delay 0
01:00:41.539484364: call returned: [0, "", ""]
01:00:41.539778350: calling as amnesia: gsettings set org.gnome.desktop.interface toolkit-accessibility true
01:00:41.714149882: call returned: [0, "", ""]
01:00:41.714572090: executing Python as amnesia:
import dogtail.config
import dogtail.tree
import dogtail.predicate
dogtail.config.logDebugToFile = False
dogtail.config.logDebugToStdOut = False
dogtail.config.blinkOnActions = True
dogtail.config.searchShowingOnly = True
node136 = dogtail.tree.root.application('gnome-shell')
01:00:43.113322251: execution complete
01:00:43.837864555: [log] CLICK on L(512,10)@S(0)[0,0 1024x768]
01:00:43.838288692: executing Python as amnesia: node137 = node136.child('No Notifications', roleName='label')
01:00:45.610529214: execution complete
01:00:45.610752212: executing Python as amnesia: node138 = node136.child('No Notifications', roleName='label')
01:00:46.831920886: execution complete
And I start Tails from DVD with network unplugged and I login # features/step_definitions/common_steps.rb:116
01:00:46.880538187: calling as root: pidof -x -o '%PPID' gnome-terminal-server
01:00:46.897873733: [log] TYPE "#ESC."
01:00:47.308373704: call returned: [1, "", ""]
01:00:47.369734931: calling as amnesia: xdotool key Super
01:00:47.597787327: call returned: [0, "", ""]
01:00:49.113528940: [log] TYPE "commandline"
01:00:49.179179893: [log] ( Ctrl ) TYPE "#ENTER."
01:00:55.928519855: [log] TYPE "/usr/bin/tails-installer --verbose > /tmp/tails-installer.log 2>&1#ENTER."
01:00:55.930245654: executing Python as amnesia:
import dogtail.config
import dogtail.tree
import dogtail.predicate
dogtail.config.logDebugToFile = False
dogtail.config.logDebugToStdOut = False
dogtail.config.blinkOnActions = True
dogtail.config.searchShowingOnly = True
node139 = dogtail.tree.root.application('tails-installer')
01:00:57.908432368: execution complete
01:00:57.908663389: executing Python as amnesia: node140 = node139.child('Tails Installer', roleName='frame')
01:00:58.042805189: execution complete
01:01:01.043144445: calling as amnesia: xdotool search --name 'Tails Installer' windowactivate --sync
01:01:01.295541366: call returned: [0, "", ""]
01:01:01.328945711: executing Python as amnesia: node141 = node139.child('Target USB stick:', roleName='label')
01:01:01.399729367: execution complete
01:01:01.400078269: executing Python as amnesia: node142 = node141.parent
01:01:01.430241793: execution complete
01:01:01.430511328: executing Python as amnesia: node143 = node142.child('', roleName='combo box', recursive=False)
01:01:01.475447265: execution complete
01:01:01.475615301: executing Python as amnesia: print(node143.name)
01:01:01.509398991: execution complete
01:01:01.509909565: executing Python as amnesia: node144 = node139.button('Install')
01:01:01.637976230: execution complete
01:01:01.638173120: executing Python as amnesia: node144.click()
01:01:02.681601377: execution complete
01:01:02.681893539: executing Python as amnesia: node145 = node139.child('Question', roleName='alert')
01:01:02.755520177: execution complete
01:01:02.755759349: executing Python as amnesia: node146 = node145.button('Yes')
01:01:02.800689752: execution complete
01:01:02.800849315: executing Python as amnesia: node146.click()
01:01:03.846015158: execution complete
01:01:03.846382116: executing Python as amnesia: node147 = node139.child('Information', roleName='alert')
01:01:14.966754392: execution complete
01:01:15.967220395: executing Python as amnesia: node148 = node139.child('Information', roleName='alert')
01:01:27.562471027: execution complete
01:01:28.562951480: executing Python as amnesia: node149 = node139.child('Information', roleName='alert')
01:01:39.666474440: execution complete
01:01:40.667150989: executing Python as amnesia: node150 = node139.child('Information', roleName='alert')
01:01:51.860633064: execution complete
01:01:52.861118009: executing Python as amnesia: node151 = node139.child('Information', roleName='alert')
01:02:04.358282000: execution complete
01:02:05.358776670: executing Python as amnesia: node152 = node139.child('Information', roleName='alert')
01:02:16.814084339: execution complete
01:02:17.814545272: executing Python as amnesia: node153 = node139.child('Information', roleName='alert')
01:02:29.173825685: execution complete
01:02:30.174329016: executing Python as amnesia: node154 = node139.child('Information', roleName='alert')
01:02:41.126350135: execution complete
01:02:42.126773884: executing Python as amnesia: node155 = node139.child('Information', roleName='alert')
01:02:53.168471496: execution complete
01:02:54.168993110: executing Python as amnesia: node156 = node139.child('Information', roleName='alert')
01:03:05.033703688: execution complete
01:03:06.034298660: executing Python as amnesia: node157 = node139.child('Information', roleName='alert')
01:03:17.538883716: execution complete
01:03:18.539296914: executing Python as amnesia: node158 = node139.child('Information', roleName='alert')
01:03:29.852279679: execution complete
01:03:30.852687962: executing Python as amnesia: node159 = node139.child('Information', roleName='alert')
01:03:42.300939755: execution complete
01:03:43.301551901: executing Python as amnesia: node160 = node139.child('Information', roleName='alert')
01:03:54.218559211: execution complete
01:03:55.219043695: executing Python as amnesia: node161 = node139.child('Information', roleName='alert')
01:04:06.579836355: execution complete
01:04:07.580320535: executing Python as amnesia: node162 = node139.child('Information', roleName='alert')
01:04:18.887323398: execution complete
01:04:19.887689036: executing Python as amnesia: node163 = node139.child('Information', roleName='alert')
01:04:31.311057493: execution complete
01:04:32.311587634: executing Python as amnesia: node164 = node139.child('Information', roleName='alert')
01:04:43.859466284: execution complete
01:04:44.859826100: executing Python as amnesia: node165 = node139.child('Information', roleName='alert')
01:04:56.080986696: execution complete
01:04:57.081364031: executing Python as amnesia: node166 = node139.child('Information', roleName='alert')
01:05:08.271339918: execution complete
01:05:09.271742973: executing Python as amnesia: node167 = node139.child('Information', roleName='alert')
01:05:20.753699875: execution complete
01:05:21.754096202: executing Python as amnesia: node168 = node139.child('Information', roleName='alert')
01:05:32.724372287: execution complete
01:05:33.724850648: executing Python as amnesia: node169 = node139.child('Information', roleName='alert')
01:05:45.379189577: execution complete
01:05:46.379662310: executing Python as amnesia: node170 = node139.child('Information', roleName='alert')
01:05:57.603166279: execution complete
01:05:58.603547653: executing Python as amnesia: node171 = node139.child('Information', roleName='alert')
01:06:09.543439344: execution complete
01:06:10.543822052: executing Python as amnesia: node172 = node139.child('Information', roleName='alert')
01:06:21.639450846: execution complete
01:06:22.639957965: executing Python as amnesia: node173 = node139.child('Information', roleName='alert')
01:06:33.508917439: execution complete
01:06:34.509403801: executing Python as amnesia: node174 = node139.child('Information', roleName='alert')
01:06:46.143308999: execution complete
01:06:47.143694055: executing Python as amnesia: node175 = node139.child('Information', roleName='alert')
01:06:58.005667808: execution complete
01:06:59.006072611: executing Python as amnesia: node176 = node139.child('Information', roleName='alert')
01:07:10.067510870: execution complete
01:07:11.067951371: executing Python as amnesia: node177 = node139.child('Information', roleName='alert')
01:07:22.089735890: execution complete
01:07:23.090131385: executing Python as amnesia: node178 = node139.child('Information', roleName='alert')
01:07:33.952007384: execution complete
01:07:34.952360550: executing Python as amnesia: node179 = node139.child('Information', roleName='alert')
01:07:46.210074970: execution complete
01:07:47.210439216: executing Python as amnesia: node180 = node139.child('Information', roleName='alert')
01:07:58.049670047: execution complete
01:07:59.050168549: executing Python as amnesia: node181 = node139.child('Information', roleName='alert')
01:08:10.029370136: execution complete
01:08:11.029804538: executing Python as amnesia: node182 = node139.child('Information', roleName='alert')
01:08:21.985672691: execution complete
01:08:22.986141348: executing Python as amnesia: node183 = node139.child('Information', roleName='alert')
01:08:33.797863077: execution complete
01:08:34.798318866: executing Python as amnesia: node184 = node139.child('Information', roleName='alert')
01:08:45.822277319: execution complete
01:08:46.822815784: executing Python as amnesia: node185 = node139.child('Information', roleName='alert')
01:08:57.647495708: execution complete
01:08:58.647935011: executing Python as amnesia: node186 = node139.child('Information', roleName='alert')
01:09:09.472290664: execution complete
01:09:10.472731726: executing Python as amnesia: node187 = node139.child('Information', roleName='alert')
01:09:21.422976929: execution complete
01:09:22.423413866: executing Python as amnesia: node188 = node139.child('Information', roleName='alert')
01:09:33.259841489: execution complete
01:09:34.260289875: executing Python as amnesia: node189 = node139.child('Information', roleName='alert')
01:09:45.093082049: execution complete
01:09:46.093570707: executing Python as amnesia: node190 = node139.child('Information', roleName='alert')
01:09:56.909205881: execution complete
01:09:57.909683110: executing Python as amnesia: node191 = node139.child('Information', roleName='alert')
01:10:08.733467040: execution complete
01:10:09.733906711: executing Python as amnesia: node192 = node139.child('Information', roleName='alert')
01:10:20.551534775: execution complete
01:10:21.551947763: executing Python as amnesia: node193 = node139.child('Information', roleName='alert')
01:10:32.380758264: execution complete
01:10:33.381126427: executing Python as amnesia: node194 = node139.child('Information', roleName='alert')
01:10:44.220098221: execution complete
01:10:45.220582445: executing Python as amnesia: node195 = node139.child('Information', roleName='alert')
01:10:56.183364498: execution complete
01:10:57.183901452: executing Python as amnesia: node196 = node139.child('Information', roleName='alert')
01:11:08.252378429: execution complete
01:11:09.252889690: executing Python as amnesia: node197 = node139.child('Information', roleName='alert')
01:11:20.754025699: execution complete
01:11:21.754511168: executing Python as amnesia: node198 = node139.child('Information', roleName='alert')
01:11:32.647834297: execution complete
01:11:33.648323074: executing Python as amnesia: node199 = node139.child('Information', roleName='alert')
01:11:44.464359632: execution complete
01:11:45.464748786: executing Python as amnesia: node200 = node139.child('Information', roleName='alert')
01:11:56.562098506: execution complete
01:11:57.562522734: executing Python as amnesia: node201 = node139.child('Information', roleName='alert')
01:12:08.369873824: execution complete
01:12:09.370299351: executing Python as amnesia: node202 = node139.child('Information', roleName='alert')
01:12:20.278510227: execution complete
01:12:21.278949128: executing Python as amnesia: node203 = node139.child('Information', roleName='alert')
01:12:32.284324048: execution complete
01:12:33.284669529: executing Python as amnesia: node204 = node139.child('Information', roleName='alert')
01:12:44.150743799: execution complete
01:12:45.151212373: executing Python as amnesia: node205 = node139.child('Information', roleName='alert')
01:12:55.940304786: execution complete
01:12:56.940757090: executing Python as amnesia: node206 = node139.child('Information', roleName='alert')
01:13:07.792239910: execution complete
01:13:08.792695521: executing Python as amnesia: node207 = node139.child('Information', roleName='alert')
01:13:19.614065055: execution complete
01:13:20.614581079: executing Python as amnesia: node208 = node139.child('Information', roleName='alert')
01:13:31.434393095: execution complete
01:13:32.434927501: executing Python as amnesia: node209 = node139.child('Information', roleName='alert')
01:13:43.481264761: execution complete
01:13:44.481703053: executing Python as amnesia: node210 = node139.child('Information', roleName='alert')
01:13:55.381156164: execution complete
01:13:56.381533770: executing Python as amnesia: node211 = node139.child('Information', roleName='alert')
01:14:07.335274261: execution complete
01:14:08.335742320: executing Python as amnesia: node212 = node139.child('Information', roleName='alert')
01:14:19.236740293: execution complete
01:14:20.237155502: executing Python as amnesia: node213 = node139.child('Information', roleName='alert')
01:14:31.112704419: execution complete
01:14:32.119810308: executing Python as amnesia: node214 = node139.child('Information', roleName='alert')
01:14:43.011016524: execution complete
01:14:44.011539166: executing Python as amnesia: node215 = node139.child('Information', roleName='alert')
01:14:54.797487738: execution complete
01:14:55.797856406: executing Python as amnesia: node216 = node139.child('Information', roleName='alert')
01:15:06.847465129: execution complete
01:15:07.847910160: executing Python as amnesia: node217 = node139.child('Information', roleName='alert')
01:15:18.649313703: execution complete
01:15:19.649721431: executing Python as amnesia: node218 = node139.child('Information', roleName='alert')
01:15:30.476329088: execution complete
01:15:31.476820581: executing Python as amnesia: node219 = node139.child('Information', roleName='alert')
01:15:42.299152774: execution complete
01:15:43.299697135: executing Python as amnesia: node220 = node139.child('Information', roleName='alert')
01:15:54.178949839: execution complete
01:15:55.179410801: executing Python as amnesia: node221 = node139.child('Information', roleName='alert')
01:16:06.004259960: execution complete
01:16:07.004715013: executing Python as amnesia: node222 = node139.child('Information', roleName='alert')
01:16:17.988827186: execution complete
01:16:18.989232422: executing Python as amnesia: node223 = node139.child('Information', roleName='alert')
01:16:29.846757854: execution complete
01:16:30.848935308: executing Python as amnesia: node224 = node139.child('Information', roleName='alert')
01:16:41.785566775: execution complete
01:16:42.786040386: executing Python as amnesia: node225 = node139.child('Information', roleName='alert')
01:16:53.783270817: execution complete
01:16:54.783750714: executing Python as amnesia: node226 = node139.child('Information', roleName='alert')
01:17:05.608256741: execution complete
01:17:06.608730279: executing Python as amnesia: node227 = node139.child('Information', roleName='alert')
01:17:17.463727610: execution complete
01:17:18.464076979: executing Python as amnesia: node228 = node139.child('Information', roleName='alert')
01:17:29.314779047: execution complete
01:17:30.315123928: executing Python as amnesia: node229 = node139.child('Information', roleName='alert')
01:17:41.120457833: execution complete
01:17:42.120955587: executing Python as amnesia: node230 = node139.child('Information', roleName='alert')
01:17:52.968425550: execution complete
01:17:53.968877114: executing Python as amnesia: node231 = node139.child('Information', roleName='alert')
01:18:04.839813808: execution complete
01:18:05.840384324: executing Python as amnesia: node232 = node139.child('Information', roleName='alert')
01:18:16.707395941: execution complete
01:18:17.707862081: executing Python as amnesia: node233 = node139.child('Information', roleName='alert')
01:18:28.821963336: execution complete
01:18:29.822572495: executing Python as amnesia: node234 = node139.child('Information', roleName='alert')
01:18:40.635211106: execution complete
01:18:41.635671464: executing Python as amnesia: node235 = node139.child('Information', roleName='alert')
01:18:52.413912679: execution complete
01:18:53.414379713: executing Python as amnesia: node236 = node139.child('Information', roleName='alert')
01:19:04.314365224: execution complete
01:19:05.314978962: executing Python as amnesia: node237 = node139.child('Information', roleName='alert')
01:19:16.280811204: execution complete
01:19:17.281249135: executing Python as amnesia: node238 = node139.child('Information', roleName='alert')
01:19:28.102574338: execution complete
01:19:29.102947339: executing Python as amnesia: node239 = node139.child('Information', roleName='alert')
01:19:40.197223596: execution complete
01:19:41.197701269: executing Python as amnesia: node240 = node139.child('Information', roleName='alert')
01:19:52.049909819: execution complete
01:19:53.050359766: executing Python as amnesia: node241 = node139.child('Information', roleName='alert')
01:20:03.851228560: execution complete
01:20:04.851586364: executing Python as amnesia: node242 = node139.child('Information', roleName='alert')
01:20:15.714954013: execution complete
01:20:16.718225842: executing Python as amnesia: node243 = node139.child('Information', roleName='alert')
01:20:27.556384726: execution complete
01:20:28.556847535: executing Python as amnesia: node244 = node139.child('Information', roleName='alert')
01:20:39.329016047: execution complete
01:20:40.329461341: executing Python as amnesia: node245 = node139.child('Information', roleName='alert')
01:20:51.186500223: execution complete
01:20:52.186925074: executing Python as amnesia: node246 = node139.child('Information', roleName='alert')
01:21:03.148930147: execution complete
01:21:04.149460776: executing Python as amnesia: node247 = node139.child('Information', roleName='alert')
01:21:16.021867943: execution complete
01:21:17.022338542: executing Python as amnesia: node248 = node139.child('Information', roleName='alert')
01:21:27.830609274: execution complete
01:21:28.831043467: executing Python as amnesia: node249 = node139.child('Information', roleName='alert')
01:21:39.599832782: execution complete
01:21:40.600236116: executing Python as amnesia: node250 = node139.child('Information', roleName='alert')
01:21:51.399064221: execution complete
01:21:52.399422073: executing Python as amnesia: node251 = node139.child('Information', roleName='alert')
01:22:03.201347134: execution complete
01:22:04.201810275: executing Python as amnesia: node252 = node139.child('Information', roleName='alert')
01:22:15.102101983: execution complete
01:22:16.102571389: executing Python as amnesia: node253 = node139.child('Information', roleName='alert')
01:22:27.050704470: execution complete
01:22:28.051098297: executing Python as amnesia: node254 = node139.child('Information', roleName='alert')
01:22:39.076853642: execution complete
01:22:40.077373226: executing Python as amnesia: node255 = node139.child('Information', roleName='alert')
01:22:50.893816504: execution complete
01:22:51.894308087: executing Python as amnesia: node256 = node139.child('Information', roleName='alert')
01:23:02.628748043: execution complete
01:23:03.629221407: executing Python as amnesia: node257 = node139.child('Information', roleName='alert')
01:23:14.397530607: execution complete
01:23:15.397939227: executing Python as amnesia: node258 = node139.child('Information', roleName='alert')
01:23:26.209498837: execution complete
01:23:27.210016170: executing Python as amnesia: node259 = node139.child('Information', roleName='alert')
01:23:38.028576050: execution complete
01:23:39.028989420: executing Python as amnesia: node260 = node139.child('Information', roleName='alert')
01:23:49.946063899: execution complete
01:23:50.946457916: executing Python as amnesia: node261 = node139.child('Information', roleName='alert')
01:24:02.079375498: execution complete
01:24:03.079877825: executing Python as amnesia: node262 = node139.child('Information', roleName='alert')
01:24:13.916796437: execution complete
01:24:14.917334381: executing Python as amnesia: node263 = node139.child('Information', roleName='alert')
01:24:25.767635246: execution complete
01:24:26.768080207: executing Python as amnesia: node264 = node139.child('Information', roleName='alert')
01:24:37.505982009: execution complete
01:24:38.506447296: executing Python as amnesia: node265 = node139.child('Information', roleName='alert')
01:24:49.984507672: execution complete
01:24:50.984844226: executing Python as amnesia: node266 = node139.child('Information', roleName='alert')
01:25:01.936692563: execution complete
01:25:02.937026870: executing Python as amnesia: node267 = node139.child('Information', roleName='alert')
01:25:13.706502769: execution complete
01:25:14.706942512: executing Python as amnesia: node268 = node139.child('Information', roleName='alert')
01:25:25.635579645: execution complete
01:25:26.636022964: executing Python as amnesia: node269 = node139.child('Information', roleName='alert')
01:25:37.455222074: execution complete
01:25:38.455621036: executing Python as amnesia: node270 = node139.child('Information', roleName='alert')
01:25:49.264692721: execution complete
01:25:50.265048038: executing Python as amnesia: node271 = node139.child('Information', roleName='alert')
01:26:01.068727872: execution complete
01:26:02.069281846: executing Python as amnesia: node272 = node139.child('Information', roleName='alert')
01:26:13.183715527: execution complete
01:26:14.185868972: executing Python as amnesia: node273 = node139.child('Information', roleName='alert')
01:26:24.970883633: execution complete
01:26:25.971319225: executing Python as amnesia: node274 = node139.child('Information', roleName='alert')
01:26:36.803997074: execution complete
01:26:37.804364189: executing Python as amnesia: node275 = node139.child('Information', roleName='alert')
01:26:48.638860998: execution complete
01:26:49.639398801: executing Python as amnesia: node276 = node139.child('Information', roleName='alert')
01:27:00.741237252: execution complete
01:27:01.741618634: executing Python as amnesia: node277 = node139.child('Information', roleName='alert')
01:27:12.621476878: execution complete
01:27:13.622080063: executing Python as amnesia: node278 = node139.child('Information', roleName='alert')
01:27:24.403090800: execution complete
01:27:25.403453246: executing Python as amnesia: node279 = node139.child('Information', roleName='alert')
01:27:36.363667339: execution complete
01:27:37.364185455: executing Python as amnesia: node280 = node139.child('Information', roleName='alert')
01:27:48.219554332: execution complete
01:27:49.219998539: executing Python as amnesia: node281 = node139.child('Information', roleName='alert')
01:28:00.057568088: execution complete
01:28:01.058014176: executing Python as amnesia: node282 = node139.child('Information', roleName='alert')
01:28:11.949078027: execution complete
01:28:12.949494920: executing Python as amnesia: node283 = node139.child('Information', roleName='alert')
01:28:23.705011234: execution complete
01:28:24.705521029: executing Python as amnesia: node284 = node139.child('Information', roleName='alert')
01:28:35.585494296: execution complete
01:28:36.585925375: executing Python as amnesia: node285 = node139.child('Information', roleName='alert')
01:28:47.415791818: execution complete
01:28:48.416159249: executing Python as amnesia: node286 = node139.child('Information', roleName='alert')
01:28:59.526033701: execution complete
01:29:00.526528044: executing Python as amnesia: node287 = node139.child('Information', roleName='alert')
01:29:11.434082997: execution complete
01:29:12.434433332: executing Python as amnesia: node288 = node139.child('Information', roleName='alert')
01:29:23.405546510: execution complete
01:29:24.406005336: executing Python as amnesia: node289 = node139.child('Information', roleName='alert')
01:29:35.281927675: execution complete
01:29:36.282387200: executing Python as amnesia: node290 = node139.child('Information', roleName='alert')
01:29:47.275905184: execution complete
01:29:48.276389539: executing Python as amnesia: node291 = node139.child('Information', roleName='alert')
01:29:59.102144399: execution complete
01:30:00.102648124: executing Python as amnesia: node292 = node139.child('Information', roleName='alert')
01:30:10.907058846: execution complete
01:30:11.907591618: executing Python as amnesia: node293 = node139.child('Information', roleName='alert')
01:30:22.694091250: execution complete
01:30:23.694522660: executing Python as amnesia: node294 = node139.child('Information', roleName='alert')
01:30:34.510449988: execution complete
01:30:35.510909093: executing Python as amnesia: node295 = node139.child('Information', roleName='alert')
01:30:46.304613642: execution complete
01:30:47.305131717: executing Python as amnesia: node296 = node139.child('Information', roleName='alert')
01:30:58.211729479: execution complete
01:30:59.212118027: executing Python as amnesia: node297 = node139.child('Information', roleName='alert')
01:31:03.847305940: opening file /tmp/tails-installer.log in 'read' mode
01:31:09.994967739: Dropped out-of-order remote shell response: got id 1267 but expected id 1268
01:31:11.551816880: read complete
01:31:11.552074227: Tails Installer debug log:
2017-12-09 09:10:17,262 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop14
2017-12-09 09:10:17,262 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop14 which has no associated drive
2017-12-09 09:10:17,262 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/drives/QEMU_QEMU_HARDDISK_1_0000_3a00_3a01_2e1_3a00_2e0_2
2017-12-09 09:10:17,262 [creator.py:598 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/drives/QEMU_QEMU_HARDDISK_1_0000_3a00_3a01_2e1_3a00_2e0_2 which is not a block device
2017-12-09 09:10:17,263 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop9
2017-12-09 09:10:17,263 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop9 which has no associated drive
2017-12-09 09:10:17,263 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop18
2017-12-09 09:10:17,264 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop18 which has no associated drive
2017-12-09 09:10:17,264 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop10
2017-12-09 09:10:17,264 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop10 which has no associated drive
2017-12-09 09:10:17,264 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop16
2017-12-09 09:10:17,265 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop16 which has no associated drive
2017-12-09 09:10:17,265 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop8
2017-12-09 09:10:17,265 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop8 which has no associated drive
2017-12-09 09:10:17,265 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop6
2017-12-09 09:10:17,265 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop6 which has no associated drive
2017-12-09 09:10:17,266 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop31
2017-12-09 09:10:17,266 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop31 which has no associated drive
2017-12-09 09:10:17,266 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop30
2017-12-09 09:10:17,266 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop30 which has no associated drive
2017-12-09 09:10:17,266 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop4
2017-12-09 09:10:17,270 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop4 which has no associated drive
2017-12-09 09:10:17,270 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop3
2017-12-09 09:10:17,270 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop3 which has no associated drive
2017-12-09 09:10:17,270 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop2
2017-12-09 09:10:17,271 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop2 which has no associated drive
2017-12-09 09:10:17,271 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop11
2017-12-09 09:10:17,271 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop11 which has no associated drive
2017-12-09 09:10:17,271 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop0
2017-12-09 09:10:17,272 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop0 which has no associated drive
2017-12-09 09:10:17,272 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/sda1
2017-12-09 09:10:17,274 [creator.py:686 (detect_supported_drives)] DEBUG: {'bootable': None,
'device': '/dev/sda1',
'free': None,
'fstype': 'iso9660',
'fsversion': 'Joliet Extension',
'is_device_big_enough_for_installation': True,
'is_optical': False,
'label': '',
'model': 'QEMU HARDDISK',
'mount': None,
'mounted_partitions': set([]),
'parent': '/dev/sda',
'parent_size': 7549747200,
'parent_udi': '/org/freedesktop/UDisks2/block_devices/sda',
'removable': True,
'size': 7549747200,
'udi': '/org/freedesktop/UDisks2/block_devices/sda1',
'uuid': '2017-11-15-12-11-29-00',
'vendor': 'QEMU'}
2017-12-09 09:10:17,274 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop29
2017-12-09 09:10:17,274 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop29 which has no associated drive
2017-12-09 09:10:17,274 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop28
2017-12-09 09:10:17,274 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop28 which has no associated drive
2017-12-09 09:10:17,274 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop27
2017-12-09 09:10:17,275 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop27 which has no associated drive
2017-12-09 09:10:17,275 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop26
2017-12-09 09:10:17,275 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop26 which has no associated drive
2017-12-09 09:10:17,275 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop25
2017-12-09 09:10:17,275 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop25 which has no associated drive
2017-12-09 09:10:17,275 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop24
2017-12-09 09:10:17,276 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop24 which has no associated drive
2017-12-09 09:10:17,276 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop23
2017-12-09 09:10:17,276 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop23 which has no associated drive
2017-12-09 09:10:17,276 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop22
2017-12-09 09:10:17,276 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop22 which has no associated drive
2017-12-09 09:10:17,276 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop21
2017-12-09 09:10:17,276 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop21 which has no associated drive
2017-12-09 09:10:17,276 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop20
2017-12-09 09:10:17,277 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop20 which has no associated drive
2017-12-09 09:10:17,277 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/sda
2017-12-09 09:10:17,278 [creator.py:686 (detect_supported_drives)] DEBUG: {'bootable': None,
'device': '/dev/sda',
'free': None,
'fstype': 'iso9660',
'fsversion': 'Joliet Extension',
'is_device_big_enough_for_installation': True,
'is_optical': False,
'label': 'QEMU-QEMU-HARDDISK-1-0000:00:01.1:00.0-2',
'model': 'QEMU HARDDISK',
'mount': None,
'mounted_partitions': set([]),
'parent': None,
'parent_size': None,
'parent_udi': None,
'removable': True,
'size': 7549747200,
'udi': '/org/freedesktop/UDisks2/block_devices/sda',
'uuid': '2017-11-15-12-11-29-00',
'vendor': 'QEMU'}
2017-12-09 09:10:17,278 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop15
2017-12-09 09:10:17,278 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop15 which has no associated drive
2017-12-09 09:10:17,278 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/drives/QEMU_DVD_ROM_QM00005
2017-12-09 09:10:17,278 [creator.py:598 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/drives/QEMU_DVD_ROM_QM00005 which is not a block device
2017-12-09 09:10:17,278 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop5
2017-12-09 09:10:17,279 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop5 which has no associated drive
2017-12-09 09:10:17,279 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop12
2017-12-09 09:10:17,279 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop12 which has no associated drive
2017-12-09 09:10:17,279 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop17
2017-12-09 09:10:17,279 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop17 which has no associated drive
2017-12-09 09:10:17,279 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/sr0
2017-12-09 09:10:17,280 [creator.py:636 (detect_supported_drives)] WARNING: Skipping device '/org/freedesktop/UDisks2/block_devices/sr0' connected to '' interface
2017-12-09 09:10:17,280 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop19
2017-12-09 09:10:17,280 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop19 which has no associated drive
2017-12-09 09:10:17,280 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop13
2017-12-09 09:10:17,280 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop13 which has no associated drive
2017-12-09 09:10:17,280 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop7
2017-12-09 09:10:17,280 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop7 which has no associated drive
2017-12-09 09:10:17,280 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop1
2017-12-09 09:10:17,281 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop1 which has no associated drive
2017-12-09 09:10:17,281 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/Manager
2017-12-09 09:10:17,281 [creator.py:598 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/Manager which is not a block device
2017-12-09 09:10:17,281 [creator.py:712 (detect_supported_drives)] DEBUG: {}
2017-12-09 09:10:17,281 [gui.py:531 (add_devices)] DEBUG: drives: {'/dev/sda': {'size': 7549747200, 'is_optical': False, 'vendor': 'QEMU', 'fsversion': 'Joliet Extension', 'parent': None, 'bootable': None, 'mount': None, 'parent_size': None, 'mounted_partitions': set([]), 'removable': True, 'free': None, 'label': 'QEMU-QEMU-HARDDISK-1-0000:00:01.1:00.0-2', 'is_device_big_enough_for_installation': True, 'fstype': 'iso9660', 'parent_udi': None, 'device': '/dev/sda', 'model': 'QEMU HARDDISK', 'udi': '/org/freedesktop/UDisks2/block_devices/sda', 'uuid': '2017-11-15-12-11-29-00'}}
2017-12-09 09:10:21,170 [creator.py:527 (_set_drive)] DEBUG: /dev/sda selected: {'size': 7549747200, 'is_optical': False, 'vendor': 'QEMU', 'fsversion': 'Joliet Extension', 'parent': None, 'bootable': None, 'mount': None, 'parent_size': None, 'mounted_partitions': set([]), 'removable': True, 'free': None, 'label': 'QEMU-QEMU-HARDDISK-1-0000:00:01.1:00.0-2', 'is_device_big_enough_for_installation': True, 'fstype': 'iso9660', 'parent_udi': None, 'device': '/dev/sda', 'model': 'QEMU HARDDISK', 'udi': '/org/freedesktop/UDisks2/block_devices/sda', 'uuid': '2017-11-15-12-11-29-00'}
2017-12-09 09:10:22,323 [creator.py:803 (unmount_device)] DEBUG: Entering unmount_device for '/dev/sda'
2017-12-09 09:10:22,325 [creator.py:806 (unmount_device)] DEBUG: {'bootable': None,
'device': '/dev/sda',
'free': None,
'fstype': 'iso9660',
'fsversion': 'Joliet Extension',
'is_device_big_enough_for_installation': True,
'is_optical': False,
'label': 'QEMU-QEMU-HARDDISK-1-0000:00:01.1:00.0-2',
'model': 'QEMU HARDDISK',
'mount': None,
'mounted_partitions': set([]),
'parent': None,
'parent_size': None,
'parent_udi': None,
'removable': True,
'size': 7549747200,
'udi': '/org/freedesktop/UDisks2/block_devices/sda',
'uuid': '2017-11-15-12-11-29-00',
'vendor': 'QEMU'}
2017-12-09 09:10:22,335 [creator.py:297 (popen)] DEBUG: sync
2017-12-09 09:10:25,403 [creator.py:297 (popen)] DEBUG: /sbin/sgdisk --print /dev/sda
2017-12-09 09:10:25,529 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop14
2017-12-09 09:10:25,529 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop14 which has no associated drive
2017-12-09 09:10:25,529 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/drives/QEMU_QEMU_HARDDISK_1_0000_3a00_3a01_2e1_3a00_2e0_2
2017-12-09 09:10:25,530 [creator.py:598 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/drives/QEMU_QEMU_HARDDISK_1_0000_3a00_3a01_2e1_3a00_2e0_2 which is not a block device
2017-12-09 09:10:25,530 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop9
2017-12-09 09:10:25,530 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop9 which has no associated drive
2017-12-09 09:10:25,530 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop18
2017-12-09 09:10:25,530 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop18 which has no associated drive
2017-12-09 09:10:25,530 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop10
2017-12-09 09:10:25,532 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop10 which has no associated drive
2017-12-09 09:10:25,532 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop16
2017-12-09 09:10:25,532 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop16 which has no associated drive
2017-12-09 09:10:25,532 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop8
2017-12-09 09:10:25,532 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop8 which has no associated drive
2017-12-09 09:10:25,533 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop6
2017-12-09 09:10:25,533 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop6 which has no associated drive
2017-12-09 09:10:25,538 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop31
2017-12-09 09:10:25,538 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop31 which has no associated drive
2017-12-09 09:10:25,538 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop30
2017-12-09 09:10:25,539 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop30 which has no associated drive
2017-12-09 09:10:25,539 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop4
2017-12-09 09:10:25,539 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop4 which has no associated drive
2017-12-09 09:10:25,539 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop3
2017-12-09 09:10:25,543 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop3 which has no associated drive
2017-12-09 09:10:25,557 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop2
2017-12-09 09:10:25,569 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop2 which has no associated drive
2017-12-09 09:10:25,572 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop11
2017-12-09 09:10:25,580 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop11 which has no associated drive
2017-12-09 09:10:25,582 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/loop0
2017-12-09 09:10:25,584 [creator.py:604 (detect_supported_drives)] DEBUG: skip /org/freedesktop/UDisks2/block_devices/loop0 which has no associated drive
2017-12-09 09:10:25,587 [creator.py:596 (detect_supported_drives)] DEBUG: looking at /org/freedesktop/UDisks2/block_devices/sda1
2017-12-09 09:10:25,599 [creator.py:686 (detect_supported_drives)] DEBUG: {'bootable': None,
'device': '/dev/sda1',
'free': None,
'fstype': 'iso9660',
'fsversion': 'Joliet Extension',
'is_device_big_enough_for_installation': True,
'is_optical': False,
'label': '',
'model': 'QEMU HARDDISK',
'mount': None,
'mounted_partitions': set([]),
'parent': '/dev/sda',
'parent_size': 7549747200,
'parent_udi': '/org/freedesktop/UDisks2/block_devices/sda',
'removable': True,
'size': 7549747200,
'udi': '/org/freedesktop/UDisks2/block_devices/sda1',
'uuid': '2017-11-15-12-11-29-00',
'vendor': 'QEMU'}
2017-12-09 09:10:25,600 [gui.py:264 (run)] ERROR: 'NoneType' object has no attribute 'props'
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 198, in run
self.rescan_devices(force_partitions=False)
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 177, in rescan_devices
force_partitions=force_partitions)
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 689, in detect_supported_drives
if self.device_can_be_upgraded(data):
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 937, in device_can_be_upgraded
return self.is_partition_GPT(device) and device['fstype'] == 'vfat' \
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 920, in is_partition_GPT
if not obj.props.partition :
AttributeError: 'NoneType' object has no attribute 'props'
2017-12-09 09:10:25,601 [gui.py:265 (run)] DEBUG: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 198, in run
self.rescan_devices(force_partitions=False)
File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 177, in rescan_devices
force_partitions=force_partitions)
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 689, in detect_supported_drives
if self.device_can_be_upgraded(data):
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 937, in device_can_be_upgraded
return self.is_partition_GPT(device) and device['fstype'] == 'vfat' \
File "/usr/lib/python2.7/dist-packages/tails_installer/creator.py", line 920, in is_partition_GPT
if not obj.props.partition :
AttributeError: 'NoneType' object has no attribute 'props'
And I install Tails to USB drive "isohybrid" by cloning # features/step_definitions/usb.rb:129
try_for() timeout expired
Last ignored exception was: RuntimeError: The Dogtail script raised: SearchError: descendent of [application | tails-installer]: child with name="Information" roleName='alert' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:90:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:36:in `/^I (install|reinstall|upgrade) Tails (?:to|on) USB drive "([^"]+)" (by cloning|from an ISO)$/'
features/usb_install.feature:112:in `And I install Tails to USB drive "isohybrid" by cloning'
```
Feature Branch: bug/15031-isohybrid-by-cloning-often-fails, installer:kurono/bug/15031-isohybrid-by-cloning-often-fails
### Attachments
* [01_31_14_Writing_a_Tails_isohybrid_to_a_USB_drive_and_booting_it,_then_installing_Tails_on_top_of_it_using_Tails_Installer,_and_it_still_boots.png](https://redmine.tails.boum.org/code/attachments/download/1831/01_31_14_Writing_a_Tails_isohybrid_to_a_USB_drive_and_booting_it,_then_installing_Tails_on_top_of_it_using_Tails_Installer,_and_it_still_boots.png)
* [#15031](https://redmine.tails.boum.org/code/attachments/download/1867/%2315031)
### Related issues
- **Related to** tails/tails#10988
- **Related to** tails/tails#14724
- **Related to** tails/tails#10912Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15345Upstream our Thunderbird AppArmor profile changes2020-05-15T14:23:57ZanonymUpstream our Thunderbird AppArmor profile changes_Originally created by @anonym on [#15345 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15345)_
See the discussion starting from https://gitlab.tails.boum.org/tails/tails/-/issues/11973#note_53760 through (at leas..._Originally created by @anonym on [#15345 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15345)_
See the discussion starting from https://gitlab.tails.boum.org/tails/tails/-/issues/11973#note_53760 through (at least)
https://gitlab.tails.boum.org/tails/tails/-/issues/11973#note_53790.
### Related issues
- **Blocks** tails/tails#13245Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/15260Clarify what is Tails Greeter in the documentation of each additional setting2020-05-15T14:26:29Zsajolidasajolida@pimienta.orgClarify what is Tails Greeter in the documentation of each additional setting_Originally created by @sajolida on [#15260 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15260)_
During the UX design of Additional Software, the two people who read
<https://tails.boum.org/doc/first_steps/startu..._Originally created by @sajolida on [#15260 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15260)_
During the UX design of Additional Software, the two people who read
<https://tails.boum.org/doc/first_steps/startup_options/administration_password/>
but were not very familiar with Tails didn’t understand what **Tails
Greeter** was (nor did they click on the **<span class="underline">Tails
Greeter</span>** link).
Parent Task: tails/tails#14589
### Related issues
- **Related to** tails/tails#15122Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14965Persistence preset: displays configuration2020-09-22T07:54:55Z110100111011Persistence preset: displays configuration_Originally created by @110100111011 on [#14965 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14965)_
This is nothing overly important, but its something very annoying when
you try to use Tails with multiple monit..._Originally created by @110100111011 on [#14965 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14965)_
This is nothing overly important, but its something very annoying when
you try to use Tails with multiple monitors.
Every time you boot Tails, you first have to go into the settings, drag
your monitors around so that they fit together correctly (so that moving
the mouse out of the screen on the left side doesn’t make it appear on
the monitor thats on the right from the current screen).
Also, the setting for which monitor is the primary one has to be
adjusted, because Tails likes to pick the wrong one all the time.
Tails should remember these settings so that its not needed to readjust
these every time you boot Tails.
It should be possible that this would be saved on some non-encrypted
persistent volume so that the Tails Greeter already can appear on the
correct monitor, which it wouldn’t if the setting could only be read
after you entered the password for the encrypted persistent volume.
Ideally it should be configurable somewhere where this is saved, so that
everyone can choose if he maybe doesn’t like the monitor configuration
of the PC where Tails was last started on to be stored unencrypted on
the USB stick, or if the better usability is worth it. I personally
don’t see an issue with it being known on what PC the Tails on some
USB stick was last used with.
I guess its way easier to just store it on the encrypted persistent
volume, and that would be completely fine of course, usually doesn’t
hurt to see the Tails Greeter on the wrong monitor.
There are configurations though where it does indeed hurt to have the
Greeter always appear on the wrong monitor: If you have monitors
connected that are not powered on, and Tails decides to always consider
that the primary one, you first have to power those on or disconnect
them from the PC to be able to start Tails. And you have to do that
every time you start Tails. Having the monitor config stored
non-encrypted so that the Greeter already knows about it would be a huge
usability boost for those configurations.
Feature Branch: doc/14965-dotfile-for-monitors
### Related issues
- **Related to** tails/tails#14697
- **Related to** tails/tails#9716
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15215Iteration 1: Support unlocking VeraCrypt partitions in udisks2020-05-15T14:45:15ZsegfaultIteration 1: Support unlocking VeraCrypt partitions in udisks_Originally created by @segfault on [#15215 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15215)_
Development repository: <https://@github.com/segfault3/udisks>
Branch: support-tcrypt
Parent Task: tails..._Originally created by @segfault on [#15215 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15215)_
Development repository: <https://@github.com/segfault3/udisks>
Branch: support-tcrypt
Parent Task: tails/tails#15214
### Related issues
- **Blocks** tails/tails#15220Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/14935Future-proof the test suite vs future fundraising campaign headers2020-05-21T12:18:25ZintrigeriFuture-proof the test suite vs future fundraising campaign headers_Originally created by @intrigeri on [#14935 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14935)_
“The persistent Tor Browser directory is usable” scenario is broken by
the fundraising campaign header:
`FindFail..._Originally created by @intrigeri on [#14935 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14935)_
“The persistent Tor Browser directory is usable” scenario is broken by
the fundraising campaign header:
`FindFailed: can not find TorBrowserSavedStartupPage.png in
S(0)[0,0 1024x768]`
I think this header depends on JS to work nicely, which we don’t have on
file:/// pages.
How about we look for the “Tor check” button instead?
Feature Branch: test/14935-dogtailify-tor-browser
### Attachments
* [02_26_23_The_persistent_Tor_Browser_directory_is_usable.png](https://redmine.tails.boum.org/code/attachments/download/1801/02_26_23_The_persistent_Tor_Browser_directory_is_usable.png)
* [TorBrowserSaveOutputFileSelected.png](https://redmine.tails.boum.org/code/attachments/download/1901/TorBrowserSaveOutputFileSelected.png)
* [00_14_26_The_persistent_Tor_Browser_directory_is_usable.png](https://redmine.tails.boum.org/code/attachments/download/1902/00_14_26_The_persistent_Tor_Browser_directory_is_usable.png)
### Related issues
- **Related to** tails/tails#14923
- **Blocks** tails/tails#13241Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14881Document the survey platform in /contribute2020-05-15T14:53:44Zsajolidasajolida@pimienta.orgDocument the survey platform in /contribute_Originally created by @sajolida on [#14881 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14881)_
Parent Task: tails/sysadmin#14540_Originally created by @sajolida on [#14881 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14881)_
Parent Task: tails/sysadmin#14540Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15152Tails fails to start with an HP pavillion (broadwell chipset)2020-05-15T14:32:34ZgoupilleTails fails to start with an HP pavillion (broadwell chipset)_Originally created by @goupille on [#15152 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15152)_
A user reported that Tails 3.3 doesn’t start on this computer :
<https://support.hp.com/ca-en/document/c04785675>
..._Originally created by @goupille on [#15152 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15152)_
A user reported that Tails 3.3 doesn’t start on this computer :
<https://support.hp.com/ca-en/document/c04785675>
In the boot menu, when the user clicks on the “Start Tails” button, the
error message “Error parsing PCC subspaces from PCCT” is displayed for a
few seconds and the computer reboots.
The Toubleshooting mode, or adding xorg-driver=intel as a boot parameter
doesn’t work around this issue.
the problem is the same with
<https://nightly.tails.boum.org/build_Tails_ISO_feature-14976-linux-4.14-force-all-tests/lastSuccessful/archive/build-artifacts/>
The user was able to start previous versions of Tails and the current
Debian-live (9.3).
### Related issues
- **Blocks** tails/tails#13245Tails_3.7anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/15219Iteration 1: Upstream unlocking VeraCrypt partitions in libblockdev2020-05-15T14:33:11ZsegfaultIteration 1: Upstream unlocking VeraCrypt partitions in libblockdev_Originally created by @segfault on [#15219 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15219)_
Parent Task: tails/tails#15214
### Related issues
- [x] **Blocked by** tails/tails#15216_Originally created by @segfault on [#15219 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15219)_
Parent Task: tails/tails#15214
### Related issues
- [x] **Blocked by** tails/tails#15216Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/15216Iteration 1: Support unlocking VeraCrypt partitions in libblockdev2020-05-15T14:32:17ZsegfaultIteration 1: Support unlocking VeraCrypt partitions in libblockdev_Originally created by @segfault on [#15216 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15216)_
Development repository: <https://github.com/segfault3/libblockdev>
Branch: add\_veracrypt
Parent Task: t..._Originally created by @segfault on [#15216 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15216)_
Development repository: <https://github.com/segfault3/libblockdev>
Branch: add\_veracrypt
Parent Task: tails/tails#15214
### Related issues
- **Blocks** tails/tails#15219Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/15125Improve "needs" section of overview2020-05-15T14:34:39Zsajolidasajolida@pimienta.orgImprove "needs" section of overview_Originally created by @sajolida on [#15125 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15125)_
- Group hardware requirements
- Put time requirement first
- Put “2 hours in total”
Feature Branch: doc/..._Originally created by @sajolida on [#15125 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15125)_
- Group hardware requirements
- Put time requirement first
- Put “2 hours in total”
Feature Branch: doc/15125-improve-overview-needs
Parent Task: tails/tails#14548
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15183Prepare tails-installer release for Ubuntu Bionic Beaver2020-05-15T14:34:32ZAnonymousPrepare tails-installer release for Ubuntu Bionic Beaver_Originally created by @Anonymous on [#15183 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15183)_
Bionic Beaver scheduled for April 26th 2018. (3.6’s release date is
slightly earlier, 3.7’s slightly later…)
..._Originally created by @Anonymous on [#15183 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15183)_
Bionic Beaver scheduled for April 26th 2018. (3.6’s release date is
slightly earlier, 3.7’s slightly later…)
### Related issues
- **Related to** tails/tails#14650
- **Blocks** tails/tails#14646Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15159Monitoring of our mirrors' ability to sync2020-05-15T14:36:32ZanonymMonitoring of our mirrors' ability to sync_Originally created by @anonym on [#15159 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15159)_
After uploading Tails 3.4 it was discovered that something is broken on
the Tor Project’s side, in our mirroring setu..._Originally created by @anonym on [#15159 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15159)_
After uploading Tails 3.4 it was discovered that something is broken on
the Tor Project’s side, in our mirroring setup. To prevent these last
minute mirror problems about syncing, I wonder if we could add some
simple monitoring. For instance: at the start of each day our rsync
server creates a file with (with predictable name, e.g. today’s date),
and later in the day we check that each mirror has this expected file.
### Related issues
- **Related to** tails/tails#15162Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15114Avoid styling headers like buttons2020-05-15T14:55:12Zsajolidasajolida@pimienta.orgAvoid styling headers like buttons_Originally created by @sajolida on [#15114 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15114)_
See attachment. “News” and “Security” are headers while “Windows” and
“macOS” are buttons.
- One way would be to..._Originally created by @sajolida on [#15114 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15114)_
See attachment. “News” and “Security” are headers while “Windows” and
“macOS” are buttons.
- One way would be to use a consistent color on buttons (maybe green
like we do for links).
- Another way would be to avoid a plain dark background.
Feature Branch: feature/15114-remove-purple-rectangles
Parent Task: tails/tails#14548
### Related issues
- **Related to** tails/tails#15597
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15065Document WireframeSketcher2020-05-15T14:59:11Zsajolidasajolida@pimienta.orgDocument WireframeSketcher_Originally created by @sajolida on [#15065 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15065)_
### Related issues
- **Blocks** tails/tails#14761_Originally created by @sajolida on [#15065 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15065)_
### Related issues
- **Blocks** tails/tails#14761Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14650Package new upstream version of tails-installer -> bpo2022-03-16T08:19:49ZAnonymousPackage new upstream version of tails-installer -> bpo_Originally created by @Anonymous on [#14650 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14650)_
and upload to Debian & Ubuntu
### Related issues
- **Related to** tails/tails#15533
- **Related ..._Originally created by @Anonymous on [#14650 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14650)_
and upload to Debian & Ubuntu
### Related issues
- **Related to** tails/tails#15533
- **Related to** tails/tails#15183
- [x] **Blocked by** tails/tails#8859
- **Blocks** tails/tails#14646
- **Blocks** tails/tails#14677Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/15047Support VeraCrypt keyfiles and hidden volumes in GNOME Disks2020-05-15T14:41:04ZsegfaultSupport VeraCrypt keyfiles and hidden volumes in GNOME Disks_Originally created by @segfault on [#15047 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15047)_
Once these are supported in udisks (tails/tails#15045 and tails/tails#15046), we have to
extend the unlock dialog i..._Originally created by @segfault on [#15047 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15047)_
Once these are supported in udisks (tails/tails#15045 and tails/tails#15046), we have to
extend the unlock dialog in GNOME Disks to allow the user to choose
keyfiles and the hidden container option.
Parent Task: tails/tails#11684Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/15045Support unlocking VeraCrypt hidden volumes via udisks2020-05-15T14:42:55ZsegfaultSupport unlocking VeraCrypt hidden volumes via udisks_Originally created by @segfault on [#15045 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15045)_
During the UX sprint we decided that we must support unlocking hidden
volumes, because it is an often used feature ..._Originally created by @segfault on [#15045 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/15045)_
During the UX sprint we decided that we must support unlocking hidden
volumes, because it is an often used feature (65% of survey
participants).
This is already supported by cryptsetup, so we will have to patch
libblockdev and udisks for this.
Parent Task: tails/tails#6337Tails_3.7segfaultsegfaulthttps://gitlab.tails.boum.org/tails/tails/-/issues/14566Systematically gather data about failures when creating the intermediary Tails2020-05-15T15:10:56ZanonymSystematically gather data about failures when creating the intermediary Tails_Originally created by @anonym on [#14566 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14566)_
E.g. when using UUI etc.
The help desk team have access to this data and should design and
implement a process to do..._Originally created by @anonym on [#14566 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14566)_
E.g. when using UUI etc.
The help desk team have access to this data and should design and
implement a process to do this continuously.Tails_3.7emmapeelemmapeelhttps://gitlab.tails.boum.org/tails/tails/-/issues/14814Analyze test suite results on Buster: 2017-10 sprint2020-05-15T14:52:55ZintrigeriAnalyze test suite results on Buster: 2017-10 sprint_Originally created by @intrigeri on [#14814 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14814)_
Output: test suite updates + tickets to fix actual bugs in Tails
Parent Task: tails/tails#12615
### ..._Originally created by @intrigeri on [#14814 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14814)_
Output: test suite updates + tickets to fix actual bugs in Tails
Parent Task: tails/tails#12615
### Related issues
- **Blocks** tails/tails#13240Tails_3.7anonymanonymhttps://gitlab.tails.boum.org/tails/tails/-/issues/14681Write release notes for 3.72020-05-15T14:54:43Zsajolidasajolida@pimienta.orgWrite release notes for 3.7_Originally created by @sajolida on [#14681 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14681)_
Feature Branch: web/release-3.7_Originally created by @sajolida on [#14681 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14681)_
Feature Branch: web/release-3.7Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14678Remove expanding (zooming) effect on screenshots in installation assistant2020-05-15T14:54:49Zsajolidasajolida@pimienta.orgRemove expanding (zooming) effect on screenshots in installation assistant_Originally created by @sajolida on [#14678 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14678)_
See tails/tails#11527 and https://gitlab.tails.boum.org/tails/tails/-/issues/11527#note_53732.
This corresponds to..._Originally created by @sajolida on [#14678 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14678)_
See tails/tails#11527 and https://gitlab.tails.boum.org/tails/tails/-/issues/11527#note_53732.
This corresponds to the “screenshot” CSS class.
It should be easy to remove without breaking translations.
Feature Branch: web/14678-remove-zooming-effect
### Related issues
- **Related to** tails/tails#11527
- **Blocks** tails/tails#15392
- **Blocks** tails/tails#15411Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14724Make Tails Installer's isohybrid detection code robust2020-05-15T14:56:15ZanonymMake Tails Installer's isohybrid detection code robust_Originally created by @anonym on [#14724 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14724)_
From https://gitlab.tails.boum.org/tails/tails/-/issues/8860#note_80916:
I’m a tiny bit worried about the new isohyb..._Originally created by @anonym on [#14724 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14724)_
From https://gitlab.tails.boum.org/tails/tails/-/issues/8860#note_80916:
I’m a tiny bit worried about the new isohybrid detection code
(b7dcb936a58bb0016981645c9224caee4493112a): I’ve seen very weird
stuff happening when the kernel detects these devices, kinda lacking
determinism (sometimes it would be recognized in a way, sometimes in the
other) which is not surprising given such devices are really two
different things at the same time. Let’s not bother for now but keep it
in mind if we get related bug reports.
From https://gitlab.tails.boum.org/tails/tails/-/issues/8860#note_80948:
I think I’ve found a bug:
1. dd a Tails ISO to a USB stick
2. leave that USB stick plugged
3. start Tails Installer
4. /dev/sdc1 is automatically selected
5. the “Upgrade” button is visible (weird) but disabled (OK)
6. the “Reinstall (delete all data)” button is enabled, which is
inconsistent wrt. the “Upgrade” button (but if I click on it I’m
told “No ISO image selected” as expected); that’s another bug,
please handle it separately
7. once I select an ISO image the “Upgrade” button is enabled
8. clicking “Upgrade” fails with “Unknown GLib exception while trying
to mount device: udisks-error-quark:
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting
/dev/sdb1 at /media/intrigeri/Tails2: Wrong fs type, /dev/sdb1 has
an invalid superblock or missing helper program. (0)”
9. unplug / re-plug the USB stick => I see an “Install” button, which
works.
That’s a regression because in 4.4.18+dfsg-1 when clicking “Upgrade” I
was
told:
It is impossible to upgrade the device TOSHIBA TransMemory (7.8 GB) - /dev/sdb1 because it was not created using Tails Installer. You should instead use "Install from ISO" to upgrade Tails on this device.
… and when clicking “Install” the correct device (`/dev/sdb`) is
selected.
Granted, it’s a corner case and thankfully our doc does not instructs
anyone to do that. But it makes the developer experience a bit painful,
and (worse) confusing when working on the code that handles isohybrid’ed
devices. Also, I had doubts wrt. the robustness of some changes made in
our isohybrid detection code on this ticket, and this experience
decreases a bit my level of confidence.
And here is the response to the above from https://gitlab.tails.boum.org/tails/tails/-/issues/8860#note_80952:
So this is exactly what we do in the `Writing a Tails isohybrid to a USB
drive [...]` scenario, except that the `dd`:ing doesn’t happen during
the same session we start `tails-installer`. I’m hypothesizing that the
flakiness you’ve seen re: “isohybrid detection” only occurs during the
session the isohybrid is `dd`:ed to the disk, due to a race between the
writing of the partition table to the disk, and the scanning of said
partition table, possibly in an intermediate state of the write.
Parent Task: tails/tails#9005
### Related issues
- **Related to** tails/tails#10912
- **Related to** tails/tails#15031Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14685Fix differences in OpenPGP verification outputs2021-06-16T00:11:41ZGhost UserFix differences in OpenPGP verification outputs_Originally created by @cyberskunk on [#14685 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14685)_
GnuPG verification of Tails download output differs from that quoted
here:
<https://tails.boum.org/install/expert..._Originally created by @cyberskunk on [#14685 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14685)_
GnuPG verification of Tails download output differs from that quoted
here:
<https://tails.boum.org/install/expert/usb/index.en.html#download-verify>
With GnuPG version: 1.4.20 on Ubuntu 16.04 the command: \`gpg
—keyid-format 0xlong —verify tails-amd64-3.1.iso.sig
tails-amd64-3.1.iso\` outputs:
gpg: Signature made Wed 09 Aug 2017 01:06:36 IST
gpg: using RSA key 0xAF292B44A0EDAA41
gpg: Good signature from "Tails developers (offline long-term identity key) <tails@boum.org>"
gpg: aka "Tails developers <tails@boum.org>"
The instructions on the Tails site state that the output of this command
should be the following:
gpg: Signature made Wed Aug 9 02:06:36 2017 CEST
gpg: using RSA key 79192EE220449071F589AC00AF292B44A0EDAA41
gpg: Good signature from "Tails developers (offline long-term identity key) <tails@boum.org>" [full]
gpg: aka "Tails developers <tails@boum.org>" [full]
Primary key fingerprint: A490 D0F4 D311 A415 3E2B B7CA DBB8 02B2 58AC D84F
Subkey fingerprint: 7919 2EE2 2044 9071 F589 AC00 AF29 2B44 A0ED AA41
The instructions specifically ask the user to verify that the date of
the signature is the same.
There are three differences between actual and expected output:
1. Timezone
2. RSA Key
3. Key
fingerprint
## Potential Fixes
Running the command \`gpg —keyid-format 0xlong —with-fingerprint —verify tails-amd64-3.1.iso.sig tails-amd64-3.1.iso\` provides the fingerprints as shown on the Tails site…so maybe the provided command should be amended.
Regarding timezone, the documentation should possibly state something
like: “The date of the signature should be the same, but will be
displayed in your local timezone.”
I don’t understand why the “using RSA key…” differs. There is obviously
a relationship between the quoted value and the actual output - both
contain “AF292B44A0EDAA41”. I have tried different combinations of
\`—keyid-format\` options, but can’t get a match
Feature Branch: web/14977-improve-openpgp-instructions
### Attachments
* [wrapped.png](https://redmine.tails.boum.org/code/attachments/download/1942/wrapped.png)
### Related issues
- **Related to** tails/tails#16112
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14591Conduct User Testing of Additional Software packages GUI2020-05-15T15:06:42ZAnonymousConduct User Testing of Additional Software packages GUI_Originally created by @Anonymous on [#14591 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14591)_
As early as possible after the beta (April 15) and the doc but before
June 1st 2018. (B7)
Parent Task: ta..._Originally created by @Anonymous on [#14591 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14591)_
As early as possible after the beta (April 15) and the doc but before
June 1st 2018. (B7)
Parent Task: tails/tails#14568
### Related issues
- **Blocks** tails/tails#14592
- **Blocks** tails/tails#15567Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/13333"why 2?" window is cut out on some pages of the installation documentation.2020-05-21T12:16:26Zgoupille"why 2?" window is cut out on some pages of the installation documentation._Originally created by @goupille on [#13333 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13333)_
On <https://tails.boum.org/install/linux/usb/overview> and
<https://tails.boum.org/install/win/usb/overview/>, if t..._Originally created by @goupille on [#13333 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13333)_
On <https://tails.boum.org/install/linux/usb/overview> and
<https://tails.boum.org/install/win/usb/overview/>, if the browser is
not maximized, the “why 2?” window is cut out on the left and,
therefore, hard to read.
note that there is no probleme displaying this window on the page
before.
Feature Branch: doc/13333-dont-cut-why-2
### Attachments
* [u.png](https://redmine.tails.boum.org/code/attachments/download/1940/u.png)
* [rest.png](https://redmine.tails.boum.org/code/attachments/download/1941/rest.png)
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/14595Code for Additional Software Packages GUI: Persistence Setup2020-05-15T15:02:42ZAnonymousCode for Additional Software Packages GUI: Persistence Setup_Originally created by @Anonymous on [#14595 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14595)_
Perl code & consulting for the GUI. (B4)
Preliminary release date for the BETA: April 15th 2018.
The order of p..._Originally created by @Anonymous on [#14595 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/14595)_
Perl code & consulting for the GUI. (B4)
Preliminary release date for the BETA: April 15th 2018.
The order of priority between these tasks is:
1. ~~implement the API needed by `tails-additional-software apt-post`
so that Alan can keep working on his side:~~
1. ~~create persistent volume with ASP enabled~~
2. ~~enable ASP~~
3. ~~display config~~
4. ~~return 0 iff. success~~
2. ~~fix graphics bug: rectangle filled with black where the list of
settings was, after configuring persistence, in the “Finished”
window~~
3. tails/tails#15259: Add button in tails-persistence-setup to open the
configuration interface of Additional Software
4. tails/tails#6485: Support multiple persistent paths per preset in the
persistent volume assistant
5. tails/tails#15314: Replace custom widget button in persistent wizard with
standard GNOME switches
6. tails/tails#15280: Reorder persistence features
7. tails/tails#15313: Apply changes to persistent features without the need for a
Save button
Blueprint: https://tails.boum.org/blueprint/additional_software_packages/gui#index6h2
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-asp-gui, feature/14594-asp-gui
Parent Task: tails/tails#14594
### Subtasks
- [x] tails/tails#6485
- [x] tails/tails#15259
- [x] tails/tails#15275
- [x] tails/tails#15280
- [x] tails/tails#15314
- [x] tails/tails#15544
- [x] tails/tails#15550
### Related issues
- **Related to** tails/sysadmin#15378
- **Related to** tails/tails#15784
- [x] **Blocked by** tails/tails#14574Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/13198About menu of WhisperBack doesn't show the logo2020-05-21T12:25:58ZxinAbout menu of WhisperBack doesn't show the logo_Originally created by @xin on [#13198 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13198)_
In some gtk softwares, about menu show the logo.
In WhisperBack, it show a little grey image instead of the logo.
Tes..._Originally created by @xin on [#13198 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13198)_
In some gtk softwares, about menu show the logo.
In WhisperBack, it show a little grey image instead of the logo.
Test in 3.0.
### Attachments
* [0002-Bug-13198-Added-Logo-to-about-dialog.patch](https://redmine.tails.boum.org/code/attachments/download/1938/0002-Bug-13198-Added-Logo-to-about-dialog.patch)
### Related issues
- [x] **Blocked by** tails/tails#15440Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/12649Deal with August 2017 false positive CI notifications2020-05-15T15:29:41ZbertagazDeal with August 2017 false positive CI notifications_Originally created by @bertagaz on [#12649 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12649)_
Gather statistics about CI notifications since tails/tails#11355 brought them back
online, then see how it goes and..._Originally created by @bertagaz on [#12649 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12649)_
Gather statistics about CI notifications since tails/tails#11355 brought them back
online, then see how it goes and decide what to do.
Parent Task: tails/tails#9614
### Related issues
- **Related to** tails/tails#11355Tails_3.7bertagazbertagazhttps://gitlab.tails.boum.org/tails/tails/-/issues/12613Document Debian testing live image for debugging2020-05-15T15:31:13Zsajolidasajolida@pimienta.orgDocument Debian testing live image for debugging_Originally created by @sajolida on [#12613 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12613)_
Debian testing live images are now built
weekly:
- <http://get.debian.org/cdimage/unofficial/non-free/cd-inc..._Originally created by @sajolida on [#12613 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12613)_
Debian testing live images are now built
weekly:
- <http://get.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-live-builds/amd64/iso-hybrid/>
- <http://get.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/>
This addresses one problem we’ve been wanting to solve for years
(tails/tails#6349): very often we would like to ask bug reporters “can you
reproduce this on current Debian testing/unstable?”. Now we can\!
I believe that the unofficial GNOME image that includes non-free
firmware is the one we want to point users to in most
cases:
<http://get.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-gnome+nonfree.iso>
(signed hashes available in the parent directory).
So:
- dear help desk & foundations team: please add these links to some
place where you can find them when needed, and please start
pointing users to them when relevant.
<!-- end list -->
- dear doc writers: please consider whether we should link to these
images from some place in our troubleshooting doc.
Feature Branch: doc/12613-debian-live-images
### Related issues
- **Related to** tails/tails#6349
- **Related to** tails/tails#12474
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/13436Have Jenkins jobs that reproduce ISOs when a branch ticket is Ready for QA2020-05-15T15:27:51ZbertagazHave Jenkins jobs that reproduce ISOs when a branch ticket is Ready for QA_Originally created by @bertagaz on [#13436 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13436)_
Following the discussion on tails/tails#12715, we settled on trying to reproduce
builds for branches which Redmine ..._Originally created by @bertagaz on [#13436 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13436)_
Following the discussion on tails/tails#12715, we settled on trying to reproduce
builds for branches which Redmine ticket is Ready for QA.
Feature Branch: puppet-tails:feature/12633-lower-reproducible-builds-workload;jenkins-jobs:feature/12633-lower-reproducible-builds-workload
Parent Task: tails/tails#5630
### Related issues
- **Related to** tails/tails#12715
- **Related to** tails/sysadmin#12633
- **Related to** tails/tails#14871Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/13286Review current documentation of the translation platform2020-05-15T15:17:16ZAnonymousReview current documentation of the translation platform_Originally created by @Anonymous on [#13286 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13286)_
Feature Branch: translate-server:master
Parent Task: tails/tails#15085
### Related issues
- **R..._Originally created by @Anonymous on [#13286 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13286)_
Feature Branch: translate-server:master
Parent Task: tails/tails#15085
### Related issues
- **Related to** tails/tails#11763
- **Blocks** tails/tails#11760Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/13299Make WhisperBack easier to find in the GNOME Overview2020-05-21T12:18:22ZAnonymousMake WhisperBack easier to find in the GNOME Overview_Originally created by @Anonymous on [#13299 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13299)_
WhisperBack can be run like all applications: search for the beginning
letters “wh” and it’ll appear.
However, I ..._Originally created by @Anonymous on [#13299 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13299)_
WhisperBack can be run like all applications: search for the beginning
letters “wh” and it’ll appear.
However, I think that WhisperBack might need some metadata so that when
users search for “bug” or “report” or “tails”, they will also find the
software in the Activity overview.
The affected file is `data/whisperback.desktop` in
<https://git-tails.immerda.ch/whisperback/>.
### Attachments
* [0002-bugfix-13299-whisperback-improve-metainformation.patch](https://redmine.tails.boum.org/code/attachments/download/1944/0002-bugfix-13299-whisperback-improve-metainformation.patch)
* [bugfix-13299-whisperback-improve-metainformation.patch](https://redmine.tails.boum.org/code/attachments/download/1982/bugfix-13299-whisperback-improve-metainformation.patch)
### Related issues
- **Related to** tails/tails#11621
- **Related to** tails/tails#11689
- [x] **Blocked by** tails/tails#15440
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/13245Core work 2018Q1: Foundations Team2020-05-15T15:39:40ZintrigeriCore work 2018Q1: Foundations Team_Originally created by @intrigeri on [#13245 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13245)_
Parent Task: tails/accounting#13250
### Related issues
- [x] **Blocked by** tails/tails#11973
..._Originally created by @intrigeri on [#13245 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/13245)_
Parent Task: tails/accounting#13250
### Related issues
- [x] **Blocked by** tails/tails#11973
- [x] **Blocked by** tails/tails#14521
- [x] **Blocked by** tails/tails#15132
- [x] **Blocked by** tails/tails#15092
- [x] **Blocked by** tails/tails#15070
- [x] **Blocked by** tails/tails#15033
- [x] **Blocked by** tails/tails#15029
- [x] **Blocked by** tails/tails#15024
- [x] **Blocked by** tails/tails#14976
- [x] **Blocked by** tails/tails#14786
- [x] **Blocked by** tails/tails#13403
- [x] **Blocked by** tails/tails#12679
- [x] **Blocked by** tails/tails#12460
- [x] **Blocked by** tails/tails#15064
- [x] **Blocked by** tails/tails#14751
- [x] **Blocked by** tails/tails#15148
- [x] **Blocked by** tails/tails#15158
- [x] **Blocked by** tails/tails#15160
- [x] **Blocked by** tails/tails#15165
- [x] **Blocked by** tails/tails#15156
- [x] **Blocked by** tails/tails#15152
- [x] **Blocked by** tails/tails#14250
- [x] **Blocked by** tails/tails#15177
- [x] **Blocked by** tails/tails#15232
- [x] **Blocked by** tails/tails#15233
- [x] **Blocked by** tails/tails#15270
- [x] **Blocked by** tails/tails#15298
- [x] **Blocked by** tails/tails#15304
- [x] **Blocked by** tails/tails#15303
- [x] **Blocked by** tails/sysadmin#15318
- [x] **Blocked by** tails/tails#15320
- [x] **Blocked by** tails/tails#15201
- [x] **Blocked by** tails/tails#15341
- [x] **Blocked by** tails/tails#15340
- [x] **Blocked by** tails/tails#15345
- [x] **Blocked by** tails/tails#15344
- [x] **Blocked by** tails/tails#15434
- [x] **Blocked by** tails/tails#15437
- [x] **Blocked by** tails/tails#15433
- [x] **Blocked by** tails/tails#15449
- [x] **Blocked by** tails/tails#15456
- [x] **Blocked by** tails/tails#15457
- [x] **Blocked by** tails/tails#15471
- [x] **Blocked by** tails/tails#15173
- [x] **Blocked by** tails/tails#15475Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/12650Deal with September 2017 false positive CI notifications2020-05-15T15:24:17ZbertagazDeal with September 2017 false positive CI notifications_Originally created by @bertagaz on [#12650 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12650)_
Gather statistics about CI notifications since tails/tails#11355 brought them back
online, then see how it goes and..._Originally created by @bertagaz on [#12650 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12650)_
Gather statistics about CI notifications since tails/tails#11355 brought them back
online, then see how it goes and decide what to do.
Parent Task: tails/tails#9614
### Related issues
- **Related to** tails/tails#11355Tails_3.7bertagazbertagazhttps://gitlab.tails.boum.org/tails/tails/-/issues/12328Tails Verification: Migrate DAVE to Web Extensions and support Chrome2020-05-15T15:46:59ZAnonymousTails Verification: Migrate DAVE to Web Extensions and support Chrome_Originally created by @Anonymous on [#12328 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12328)_
This should happen by November 14 2017 \[1\].
Some useful information:
“WebExtensions can only access web conten..._Originally created by @Anonymous on [#12328 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12328)_
This should happen by November 14 2017 \[1\].
Some useful information:
“WebExtensions can only access web content by injecting separate scripts
into web pages and communicating with them using a messaging API”
(details at \[3\]).
At first glance, all the nsI\* APIs we use seem to still be available.
Note that I am not sure what
kind of add-on DAVE is, among the list of options available: overlay
add-ons, bootstrapped add-ons, and SDK add-ons. According to Mozilla’s
compatibility checker \[2\], it’s a “XUL or XPCOM add-on”, but I don’t
know for sure how to interpret this, and it seems to determine quite a
bit how the porting work will look like.
There are “Office Hours Support for Transitioning and Porting to
WebExtensions” \[4\]; available options include IRC, a web forum and a
mailing list.
\[1\]
<https://blog.mozilla.org/addons/2017/02/16/the-road-to-firefox-57-compatibility-milestones/>
\[2\] <https://compatibility-lookup.services.mozilla.com/>
\[3\]
<https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions>
\[4\]
<https://blog.mozilla.org/addons/2017/03/09/office-hours-support-transitioning-porting-webextensions/>
### Subtasks
- [x] tails/tails#11604
- [x] tails/tails#11797
- [x] tails/tails#12005
- [x] tails/tails#12581
- [x] tails/tails#12683
- [x] tails/tails#13543
- [x] tails/tails#14627
- [x] tails/tails#14628
- [x] tails/tails#14629
- [x] tails/tails#14630
- [x] tails/tails#14815
- [x] tails/tails#14912
- [x] tails/tails#14921
- [x] tails/sysadmin#14934
- [x] tails/tails#14945
- [x] tails/tails#14961
- [x] tails/tails#14977
- [x] tails/sysadmin#14979
- [x] tails/sysadmin#14980
- [x] tails/tails#14997
- [x] tails/tails#14998
- [x] tails/tails#15017
- [x] tails/tails#15056
- [x] tails/tails#15057
- [x] tails/tails#15058
- [x] tails/tails#15059
- [x] tails/tails#15060
- [x] tails/tails#15061
- [x] tails/tails#15062
- [x] tails/tails#15063
- [x] tails/tails#15133
- [x] tails/tails#15188
- [x] tails/tails#15367
- [x] tails/tails#15438
- [x] tails/tails#15443
### Related issues
- **Related to** tails/tails#10640
- **Related to** tails/tails#8531Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/12167Clarify release notes vs. changelog workflow2020-05-15T15:48:05ZintrigeriClarify release notes vs. changelog workflow_Originally created by @intrigeri on [#12167 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12167)_
Here’s some feedback produced while preparing the 2.10 release notes
since sajolida was away.
Some “external” cha..._Originally created by @intrigeri on [#12167 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12167)_
Here’s some feedback produced while preparing the 2.10 release notes
since sajolida was away.
Some “external” changelogs are handled in
`contribute/how/documentation/release_notes.mdwn`, while some are
handled in the part of the release process that’s about updating our
changelog. I’m confused: this means that potentially, some changes may
end up being documented in the release notes, but not in the changelog.
Same for “Analyze the diff of packages”. Of course, in some way it makes
sense (the changelog just states some raw facts like “upgraded Tor to
X.Y”, while the release notes have to explain the impact on users, so in
practice the release notes are not a strict subset of info that’s
already in the changelog). But then, if we think the release notes
writer must read all these changelogs, to be consistent, they must also
read the changelogs of our custom software we install as .deb:s, no? I
don’t know how we can handle this best.
Also, there seems to be some duplication between both checklists, e.g.
“the Redmine view for this release” vs. “the ”Fix committed" section
on the \*Release Manager View". I don’t understand why.
These are just examples, I’m not going to build a complete list of
things that might be a problem. What I mean here is that it seems clear
to me that the release notes vs. changelog writing processes probably
need to get to know each other better, in order to split the work
better, produce higher quality change documentation, and avoid
duplicated work.
I’m assigning this to sajolida to start with, since he wrote the release
notes checklist after we created the changelog one.
### Related issues
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/12152Update tails-installer release process2020-05-15T15:48:52ZAnonymousUpdate tails-installer release process_Originally created by @Anonymous on [#12152 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12152)_
In tails/tails#8549 we discussed that updating tails-installer for every Tails
release might now not be necessary ..._Originally created by @Anonymous on [#12152 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/12152)_
In tails/tails#8549 we discussed that updating tails-installer for every Tails
release might now not be necessary anymore. I think we still need to
update the RM release process and documentation with this new
information.
Maybe we also need to define how it will happen instead?
Or do we simply maintain things as they are currently - that is now the
RM can push to pkg-privacy? Should bertagaz also be added to pkg-privacy
then?
### Related issues
- **Related to** tails/tails#8549
- **Related to** tails/tails#15533
- **Blocks** tails/accounting#15139Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/11272Last line of Whisperback report uses different font2020-05-21T12:24:36Zmercedes508Last line of Whisperback report uses different font_Originally created by @mercedes508 on [#11272 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11272)_
Tested with Tails 2.2.1.
When writing something in the last part of a WhisperBack report (the
Desired result), ..._Originally created by @mercedes508 on [#11272 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11272)_
Tested with Tails 2.2.1.
When writing something in the last part of a WhisperBack report (the
Desired result), it uses a different font. Even though the result is the
same in the effective bug report.
Low prio.
### Attachments
* [0001-bugfix-11272-Last-line-of-Whisperback-report-uses-di.patch](https://redmine.tails.boum.org/code/attachments/download/1951/0001-bugfix-11272-Last-line-of-Whisperback-report-uses-di.patch)
### Related issues
- [x] **Blocked by** tails/tails#15440Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/11687Known issues: How to recover an Electrum wallet2020-05-15T16:20:21ZemmapeelKnown issues: How to recover an Electrum wallet_Originally created by @emmapeel on [#11687 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11687)_
We receive once in a while consults of users that cannot open their
Electrum wallet anymore.
I am almost convinced..._Originally created by @emmapeel on [#11687 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11687)_
We receive once in a while consults of users that cannot open their
Electrum wallet anymore.
I am almost convinced the wallet gets somewhat corrupted, and until now
we have proposed users to
\- Delete or move the wallet folder
\- Recreate the wallet from the seed (reconfigure Electrum with the old
seed)
We never hear from users again, so it **looks** like the process is
working.
We should add it to the Known issues page and link mention it on the
Electrum page, or add it on the same Electrum documentation, linked from
Known Issues.
I am not sure of the best place for this workaround.
Feature Branch: feature/11687-electrum_recovery
### Related issues
- **Related to** tails/tails#11665
- **Blocks** tails/tails#14758Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/11493Installation Assistant: please merge /install and /install/os2022-03-16T08:14:16ZAnonymousInstallation Assistant: please merge /install and /install/os_Originally created by @Anonymous on [#11493 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11493)_
see <https://labs.riseup.net/code/issues/11269#note-8>
Feature Branch: doc/11493-merge-install-welcome
..._Originally created by @Anonymous on [#11493 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11493)_
see <https://labs.riseup.net/code/issues/11269#note-8>
Feature Branch: doc/11493-merge-install-welcome
### Related issues
- **Related to** tails/tails#11269
- **Related to** tails/tails#11604
- **Related to** tails/tails#15597
- **Blocks** tails/tails#11494
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/11348Test Etcher, a multiplatform USB stick burner2020-05-21T12:27:18Zsajolidasajolida@pimienta.orgTest Etcher, a multiplatform USB stick burner_Originally created by @sajolida on [#11348 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11348)_
Could this replace dd graphically and on multiple platforms?
<http://www.etcher.io/>
First we should test whether..._Originally created by @sajolida on [#11348 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/11348)_
Could this replace dd graphically and on multiple platforms?
<http://www.etcher.io/>
First we should test whether it works in the first place, then whether
it modifies the ISO image in any way.
1. Download and verify an ISO image
2. Burn it on a USB stick using Etcher in Windows and Mac
3. Report a few screenshot of the process to get an idea
4. Start from this USB stick
5. Try to understand if Etcher does a byte-to-byte copy (like `dd`) or
something more fancy
6. If it’s like `dd`, try to compare the checksum of the ISO and the
resulting USB stick
7. If it’s like something else, investigate what it does, compare the
boot option, the boot loader, etc.
### Attachments
* [1.png](https://redmine.tails.boum.org/code/attachments/download/1327/1.png)
* [2.png](https://redmine.tails.boum.org/code/attachments/download/1328/2.png)
* [3.png](https://redmine.tails.boum.org/code/attachments/download/1329/3.png)
* [4.png](https://redmine.tails.boum.org/code/attachments/download/1330/4.png)
* [5.png](https://redmine.tails.boum.org/code/attachments/download/1331/5.png)
* [6.png](https://redmine.tails.boum.org/code/attachments/download/1332/6.png)
### Related issues
- **Related to** tails/tails#8802
- **Related to** tails/tails#14447Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/9308What do we do for people coming from search engines inside the assistant2020-05-15T17:48:10ZtchouWhat do we do for people coming from search engines inside the assistant_Originally created by @tchou on [#9308 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9308)_
If we do nothing special, people could crash on random pages in the
Tails Installer Assistant. At some point it could be..._Originally created by @tchou on [#9308 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/9308)_
If we do nothing special, people could crash on random pages in the
Tails Installer Assistant. At some point it could be problematic, for
example someone using firefox on a tablet comes in the “Linux/Install
Tails Downloader” extension. A user starting at the begining of the
assistant would have been routed to a specific path (no scenario for
you, sorry).
We could :
\- unindex all the internal pages of the assistant. We don’t have this
probleme anymore, but we have an other problem : maybe we could like to
have some of this pages indexed to get have some traffic.
or
\- have some warning or reminders in some pages. In wich page ?
Feature Branch: feature/9308-dont-index-installation-instructions
### Related issues
- **Blocks** tails/tails#15392Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/7797WhisperBack prevents user from removing optional PGP keyblock once they have ...2020-05-21T12:24:15ZemmapeelWhisperBack prevents user from removing optional PGP keyblock once they have entered one_Originally created by @emmapeel on [#7797 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7797)_
The code lives in <https://git-tails.immerda.ch/whisperback>.
## Steps to reproduce
1. Create a bug report.
2. Ad..._Originally created by @emmapeel on [#7797 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/7797)_
The code lives in <https://git-tails.immerda.ch/whisperback>.
## Steps to reproduce
1. Create a bug report.
2. Add an optional email address.
3. Click on “optional PGP key”.
4. Add a valid PGP key block.
5. Click “ok”.
6. Click on “optional PGP key”.
7. Remove the contents of the PGP key block.
8. Click “ok”.
9. A warning message appears saying “This doesn’t seem to be a valid
URL or OpenPGP key.”
10. Close the message and click “Cancel.”
11. Click on “optional PGP key.”
## Actual result and description of the error
The public key block is still present. If one tries to remove it,
WhisperBack prevents the removal. Sometimes it crashes, too (can’t
reproduce but happened a few times).
## Desired result
There should be a way to empty the textbox in “optional PGP key” so that
if the user changes his mind about giving email information with a PGP
key, he can without having to close WhisperBack and rewriting all his
bug information.
### Attachments
* [0001-bugfix-7797-Allow-empty-GPG-Key.patch](https://redmine.tails.boum.org/code/attachments/download/1943/0001-bugfix-7797-Allow-empty-GPG-Key.patch)
### Related issues
- **Has duplicate** tails/tails#9227
- [x] **Blocked by** tails/tails#15440Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/6485Support multiple persistent paths per preset in the persistent volume assistant2020-05-15T19:12:23ZintrigeriSupport multiple persistent paths per preset in the persistent volume assistant_Originally created by @intrigeri on [#6485 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/6485)_
It could be useful to have a single preset in tails-persistence-setup
imply adding more than 1 line in `persistence...._Originally created by @intrigeri on [#6485 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/6485)_
It could be useful to have a single preset in tails-persistence-setup
imply adding more than 1 line in `persistence.conf`.
E.g. the APT lists and packages could be merged to make things easier.
This needs a non-trivial redesign of some assumptions made in t-p-s.
Feature Branch: perl5lib:feature/14594-asp-gui, iuk:feature/14594-asp-gui, persistence-setup:feature/14594-asp-gui, feature/14594-asp-gui
Parent Task: tails/tails#14595
### Related issues
- **Blocks** tails/tails#9052Tails_3.7intrigeriintrigerihttps://gitlab.tails.boum.org/tails/tails/-/issues/5684Screen locker2020-05-21T12:19:32Zimport-from-RedmineScreen locker_Originally created by Tails on [#5684 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5684)_
Tails is currently lacking a screen locker and this has been a frequent
feature request. For example, as Tails is been ad..._Originally created by Tails on [#5684 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5684)_
Tails is currently lacking a screen locker and this has been a frequent
feature request. For example, as Tails is been adopted more and more by
journalists, they want to be able to leave their computer unattended in
their office to go to the toilets for a minute and have their screen
locked.
This has also been mentioned as a requirement for Tails Server:
<https://tails.boum.org/blueprint/server_edition/>
Team: sajolida, segfault, anonym
Blueprint: https://tails.boum.org/blueprint/screen_locker
Feature Branch: segfault:feature/5684-screen-locker
### Attachments
* [tails-lock.sh](https://redmine.tails.boum.org/code/attachments/download/1260/tails-lock.sh)
* [double password entry.png](https://redmine.tails.boum.org/code/attachments/download/1265/double%20password%20entry.png)
* [tails_screen_locker.png](https://redmine.tails.boum.org/code/attachments/download/1311/tails_screen_locker.png)
* [triple-trouble.png](https://redmine.tails.boum.org/code/attachments/download/1499/triple-trouble.png)
### Subtasks
- [x] tails/tails#5588
- [x] tails/tails#5589
- [x] tails/tails#5878
- [x] tails/tails#6017
- [x] tails/tails#8385
- [x] tails/tails#8384
- [x] tails/tails#8383
- [x] tails/tails#10970
- [x] tails/tails#12449
- [x] tails/tails#15368
- [x] tails/tails#15369
### Related issues
- **Related to** tails/tails#5660
- **Related to** tails/tails#9569
- **Related to** tails/tails#12098
- **Related to** tails/tails#5799
- **Related to** tails/tails#14556
- **Has duplicate** tails/tails#7045
- **Has duplicate** tails/tails#7719Tails_3.7https://gitlab.tails.boum.org/tails/tails/-/issues/5447Fix DVD eject at shutdown (on some computers)2020-05-15T19:40:18Zimport-from-RedmineFix DVD eject at shutdown (on some computers)_Originally created by Tails on [#5447 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5447)_
Two probably related 0.14 regressions:
- pressing the DVD reader eject button neither ejects the DVD, nor
triggers..._Originally created by Tails on [#5447 (Redmine)](https://public-redmine-archive.tails.boum.org/code/issues/5447)_
Two probably related 0.14 regressions:
- pressing the DVD reader eject button neither ejects the DVD, nor
triggers the emergency shutdown procedure
- [0.14-rc1 - DVD won’t eject before wiping of RAM during shutdown
process](https://tails.boum.org/forum/0.14-rc1_-_DVD_won__39__t_eject_before_wiping_of_RAM_during_shutdown_process/)
It might be that the old inverted logic bug that forced us to pretend to
*lock* the DVD eject button in order to effectively *unlock* it, was
fixed. Who knows.
> Indeed, linux 2.6.38-rc1 \[\[reworked disk event
handling|<http://lwn.net/Articles/423619/]]>
> and adds block.events\_dfl\_poll\_msecs that can be used to set the
> interval for polling block devices for events. This does not seem
> to work properly though: settings it to 1000 makes it work in
> VirtualBox with its virtual CD-ROM drive, but no value seems to
work
> on the one real machine I have available with a CD-ROM drive.
### Related issues
- **Related to** tails/tails#7194Tails_3.7anonymanonym