Bug #11839

After automatic upgrade from Tails 2.5 to 2.6, keyboard and mouse stop working

Added by emmapeel 2016-09-24 08:31:58 . Updated 2019-02-18 18:08:32 .

Status:
Rejected
Priority:
Elevated
Assignee:
Category:
Target version:
Start date:
2016-09-24
Due date:
% Done:

10%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Upgrader
Deliverable for:

Description

Reported by several users, some even from Tails 2.6rc~1. I could not reproduce:

Steps to reproduce

- Start Tails 2.5

- Update automatically
- Restart

Keyboard and mouse don’t work when in Tails Greeter, so it is impossible to log in.

The problem can be solved doing a manual upgrade:

https://tails.boum.org/doc/first_steps/upgrade/#manual


Subtasks


Related issues

Related to Tails - Bug #8449: Tails Upgrader fails to install some IUKs Resolved 2014-12-16
Related to Tails - Bug #12523: After automatic upgrade, keyboard and mouse do not work Rejected 2017-05-06
Related to Tails - Bug #14754: Partially applied incremental upgrades cause all kinds of trouble Confirmed 2019-03-21
Related to Tails - Bug #15557: Document workaround for partially applied automatic upgrade Resolved 2018-04-30

History

#1 Updated by emmapeel 2016-09-24 08:54:20

One user claims to have seen messages of ‘echo - tainted’ and “this has been marked as dirty ” while restarting when asked during upgrade, before the memory wipe.

Then user had to shut down with the power button, and then no keyboard nor mouse.

#2 Updated by intrigeri 2016-09-25 05:08:11

  • Assignee set to emmapeel

> Reported by several users,

Did anyone reported this without having done an automatic upgrade?

> some even from Tails 2.6rc~1.

Did all the ones reporting this with 2.6~rc1 also do the automatic upgrade?

> The problem can be solved doing a manual upgrade

Wow, this is seriously weird. It seems to indicate that something went wrong either in our IUK, or in the automatic upgrade process. To debug this further, I’ll need to see files listing from such a faulty, automatically upgraded Tails 2.6, ideally with checksums for files under the live and syslinux directories, and the content of live/Tails.module.

#3 Updated by emmapeel 2016-09-25 10:52:35

intrigeri wrote:
> > Reported by several users,
>
> Did anyone reported this without having done an automatic upgrade?
>
Not the ones reporting after 2.6 release.

> > some even from Tails 2.6rc~1.
>
> Did all the ones reporting this with 2.6~rc1 also do the automatic upgrade?
>
Not sure about this, I will ask user.

> > The problem can be solved doing a manual upgrade
>
> Wow, this is seriously weird. It seems to indicate that something went wrong either in our IUK, or in the automatic upgrade process. To debug this further, I’ll need to see files listing from such a faulty, automatically upgraded Tails 2.6, ideally with checksums for files under the live and syslinux directories

What is the preferred command to do that?

sha1sum /media/amnesia/Tails/live/* ?

, and the content of live/Tails.module.

Got a user!

#4 Updated by intrigeri 2016-09-25 11:06:14

> What is the preferred command to do that?

> sha1sum /media/amnesia/Tails/live/* ?

Whatever hash will work. So yes, this command, of course after adjusting the path to the mountpoint :)

#5 Updated by wrwerdsfgvxzc 2016-09-29 13:57:51

What hardware were the users using? Certain machines can’t handle the automatic update.

#6 Updated by intrigeri 2016-10-29 13:35:44

Any chance we see the info requested a month ago? Otherwise, feel free to close this ticket, as it is not very useful in its current shape.

#7 Updated by emmapeel 2017-01-25 09:20:51

I keep receiving reports about this, not many but apparently still is happening with Tails 2.9.1 for example.

If any new user experiences this, please:

Can you:

- Start another Tails, and add an administration password.

- Start Disks from Applications -> Utilities -> Disks

- Plug your broken Tails

- Select it from the sidebar on Disks

- Select the partition called “Tails” (NOT the one called TailsData)
- Press the ‘play’ button to mount the partition.

Now that is mounted, you need to run some commands and send us the output:

- cat /media/amnesia/Tails/live/Tails.module
- sha256sum /media/amnesia/Tails/live/*

Once you have this output, mail it to us at tails-bugs@boum.org with the
reference of this ticket

#8 Updated by emmapeel 2017-01-31 13:49:19

  • Assignee changed from emmapeel to intrigeri

Ok one user sends us (after automatic update to Tails 2.10):

root@amnesia:/home/amnesia# cat /media/amnesia/Tails/live/Tails.module
filesystem.squashfs
root@amnesia:/home/amnesia# sha256sum /media/amnesia/Tails/live/*
cbeb110bb6edc7bcd4fdc390b82157ab516bb9f0ac5a18dff7a44ba4afe5177f
/media/amnesia/Tails/live/2.10.squashfs
3c06a607a0caf37f14a0331dfe719d0b90f5f0df8873643f4c9614935a983aed
/media/amnesia/Tails/live/filesystem.packages
3ffdfc4f2a5a09a7390a1741c343fc3ccaad49062ba65ec3ad73a4d3448ad324
/media/amnesia/Tails/live/filesystem.squashfs
84da94a3328f8668e51258604c2dbf510ba21cb2271596d5ebc0130dde207707
/media/amnesia/Tails/live/initrd2.img
e4d025b2950b63e46647e86dd71be4ad5f17d6d112ed060d12a6b3aabd070286
/media/amnesia/Tails/live/initrd.img
2e23dcf5b310900d298c33d3cfb2ea091e03193b69a7d4e0eb90dd1d905a6688
/media/amnesia/Tails/live/Tails.module
92de370cee9a3a4309ab8832cde2f80a3d86db613f9fbcd7f0329ec68eadbbc4
/media/amnesia/Tails/live/vmlinuz
be4a8ef0250aeb35b40dc1708919e9a751febfac3d02dfb5fc7720fe23438cdf
/media/amnesia/Tails/live/vmlinuz2

I can forward you the contact if you want

#9 Updated by intrigeri 2017-02-01 10:32:21

  • Target version set to Tails_2.11
  • QA Check deleted (Info Needed)

Thanks! So, Tails.module is wrong, it lacks the 2.10 SquashFS delta. So the machine starts with the kernel from 2.10, but the SquashFS that’s mounted has no modules for that kernel, which explains the breakage. I think that’s a duplicate of Bug #8449. Will try to have a look during this dev cycle.

Dear help desk: this user (and presumably other affected ones) could fix their Tails device by editing live/Tails.module, and appending to it the missing line. In this case, it would be 2.10.squashfs.

#10 Updated by intrigeri 2017-02-01 10:32:31

  • related to Bug #8449: Tails Upgrader fails to install some IUKs added

#11 Updated by intrigeri 2017-03-03 11:43:55

Dear Help desk, please ask all affected users to give me not only:

  • cat /media/amnesia/Tails/live/Tails.module
  • sha256sum /media/amnesia/Tails/live/*

But also:

  • ls -l /media/amnesia/Tails/live/
  • df /media/amnesia/Tails/live/
  • the date/time when the upgrade was applied

… so I can check if Tails Upgraded wrote that file at all, and whether other files are corrupted or have the wrong size (the checksum for 2.10.squashfs reported above is wrong!).

#12 Updated by intrigeri 2017-03-03 17:16:50

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to mercedes508
  • Priority changed from Normal to Elevated
  • Target version changed from Tails_2.11 to Tails_2.12
  • % Done changed from 0 to 10
  • QA Check set to Info Needed
  • Affected tool set to Upgrader

FTR I’ve submitted a branch on Bug #8449 that should fix some of these problems: I’m confident it’ll solve the “upgrade process does not update Tails.module” one, but only when that’s the only problem. Assuming my work is merged in time for 2.11, we’ll see how it goes for the 2.11 → 2.12 upgrade.

But for example, it probably won’t solve anything for people whose upgrade process went so bad that not only Tails.module was not updated, but the installed 2.10.squashfs is corrupted (or not complete), so I still need our help desk to give me the info requested above from affected people => can a help desk member take ownership of this task and assign the ticket to them? Tentatively assigning to mercedes508, who is currently on help desk duty. Feel free to self-organize within your team and determine who’s in the best position to find & relay the info I need.

There won’t be automatic upgrades from 2.12 to 3.0, so the best we can do at this point is to gather data and fix the problem in time for 3.0, which will fix 3.0 → 3.1 upgrades.

Bumping priority as this seems to have affected a number of people recently, and bricking Tails sticks is a serious problem.

#13 Updated by segfault 2017-03-08 14:04:43

Intrigeri said he would work on this during the contributors meeting.

#14 Updated by intrigeri 2017-03-08 14:21:04

> Intrigeri said he would work on this during the contributors meeting.

FTR that’s been done already.

#15 Updated by intrigeri 2017-03-28 15:02:31

intrigeri wrote:
> […] so I still need our help desk to give me the info requested above from affected people => can a help desk member take ownership of this task and assign the ticket to them?

Ping?

#16 Updated by mercedes508 2017-03-28 15:50:35

  • Assignee changed from mercedes508 to emmapeel

I’m assigning it to emmapeel who already handled a user with this problem according to this ticket.

I didn’t se reports about it lately si I can’t help right now.

#17 Updated by intrigeri 2017-03-28 16:06:30

> I’m assigning it to emmapeel who already handled a user with this problem according to this ticket.

Thanks!

#18 Updated by emmapeel 2017-03-31 11:10:37

  • Assignee changed from emmapeel to intrigeri

THe thing is that I haven’t got new reports on this problem during upgrade to 2.11…

#19 Updated by intrigeri 2017-04-01 06:37:23

  • Assignee changed from intrigeri to emmapeel

Sorry if I’ve been unclear: I need info from any affected people, even if that’s about an upgrade to a version older than 2.11.

#20 Updated by emmapeel 2017-04-07 09:45:01

Yes, but this people has already fixed their system… I haven’t got a new user with this problem anymore.

#21 Updated by intrigeri 2017-04-10 12:18:32

  • Status changed from In Progress to Rejected
  • Assignee deleted (emmapeel)

OK. I’m closing this ticket as there’s nothing we can do about it without having more info, and it’s apparently too late to gather that info. Please file a new ticket, with the requested info, next time you get a report about it. Thanks!

#22 Updated by vfguy 2017-05-05 19:00:58

Hello, I’m having the same problem after upgrading from 2.11 to 2.12.

No mouse or keyboard at tails greeter either in normal boot or troubleshooting mode.

I would like to assist in troubleshooting/resolving this. Please let me know. Thanks.

#23 Updated by emmapeel 2017-05-06 08:52:46

  • related to Bug #12523: After automatic upgrade, keyboard and mouse do not work added

#24 Updated by emmapeel 2017-05-06 08:53:21

  • Target version deleted (Tails_2.12)

vfguy wrote:
> Hello, I’m having the same problem after upgrading from 2.11 to 2.12.
>
> No mouse or keyboard at tails greeter either in normal boot or troubleshooting mode.
>
> I would like to assist in troubleshooting/resolving this. Please let me know. Thanks.

Great! Please see Bug #12523 for details on what we need

#25 Updated by intrigeri 2017-10-03 05:44:48

  • related to Bug #14754: Partially applied incremental upgrades cause all kinds of trouble added

#26 Updated by intrigeri 2018-06-18 06:26:47

  • related to Bug #15557: Document workaround for partially applied automatic upgrade added

#27 Updated by sehlax 2019-01-15 13:29:27

had the same problem (no mouse or keyboard input possible) after doing an automatic update on 7 January from 3.10.1 to 3.11. (the progress bar disappeared during the update so I thought it’d be done)
here’s the output requested (could solve the problem modifying the version number in Tails.module)
thanks for your work!!

root@amnesia:~# cat /media/amnesia/Tails/live/Tails.module
filesystem.squashfs
3.10.1.squashfs
root@amnesia:~# sha256sum /media/amnesia/Tails/live/*
dad62c437a12383493a9e922f24b5c85045c48e43177940b528030bff35b7332  /media/amnesia/Tails/live/3.10.1.squashfs
4bc8627552bfee08f3ddd02630d20d207c59bc19775e1b4ad6ae729a9f8ef0eb  /media/amnesia/Tails/live/3.11.squashfs
b8071acc73764b3b4d5a51e5003ec4917adcef8b2e494eb246fa7e719276603e  /media/amnesia/Tails/live/Tails.module
70fb3cb9fd481b255aa6ee43216d772122c40d983143bd1f69c6af8447a3c293  /media/amnesia/Tails/live/filesystem.packages
89ae4c23ff6ebf58ba924d6c8eefb95554636922f45320e38005a3e1a1dd7a4c  /media/amnesia/Tails/live/filesystem.squashfs
38f696785682ff4c34e38ae1ddc51fa07c19c17d535834a3754297421576fd4b  /media/amnesia/Tails/live/initrd.img
c786c49bcbee84b4480eda1ec37d6381718852918a68c3ba170529e2ecba6b79  /media/amnesia/Tails/live/vmlinuz
root@amnesia:~# ls -l /media/amnesia/Tails/live/
total 1758696
-rwxr-xr-x 1 root root  365301760 Oct 22 23:30 3.10.1.squashfs
-rwxr-xr-x 1 root root  224002048 Dec 10 19:37 3.11.squashfs
-rwxr-xr-x 1 root root         36 Nov  2 10:40 Tails.module
-rwxr-xr-x 1 root root      53665 Jun 25  2018 filesystem.packages
-rwxr-xr-x 1 root root 1177124864 Jun 25  2018 filesystem.squashfs
-rwxr-xr-x 1 root root   29282532 Dec 10 19:37 initrd.img
-rwxr-xr-x 1 root root    5126016 Dec 10 19:37 vmlinuz
root@amnesia:~# df /media/amnesia/Tails/live/
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/sdd1        8372232 2018096   6354136  25% /media/amnesia/Tails

#28 Updated by intrigeri 2019-02-18 18:08:32

> had the same problem (no mouse or keyboard input possible) after doing an automatic update on 7 January from 3.10.1 to 3.11. (the progress bar disappeared during the update so I thought it’d be done)

Thank you. I’ve pointed here on Bug #14754, where we now track this problem.