Bug #15451

Greeter freezes if the persistent filesystem is corrupted

Added by eugene__k 2018-03-23 05:29:32 . Updated 2020-04-15 06:02:16 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:
User interface design

Affected tool:
Welcome Screen
Deliverable for:


If the user attempts to mount the persistent filesystem from the greeter UI and it happens to be corrupted, the attempting-to-mount animation never goes away, and the “Start Tails” button stops working. There are no errors and it is not apparent to the user why it’s stuck. After that, the user has no choice but to to hard-reboot the system since the OS won’t load.

I’ve seen this happen on two separate occasions, probably because the OS was not properly flushing its caches on shutdown (which may be a separate issue) or because the thumb drive was somehow malfunctioning. In both cases, after I rebooted and logged in without mounting persistent storage up front, I could unlock the partition using the “Disks” app with no errors, but the underlying partition was displayed as “Unknown” (rather than “ext4”) and I had to run fsck to repair it.

Instead of freezing, the UI should attempt to unlock the filesystem and, if the filesystem is unlocked but can’t be mounted, display an error advising the user that the filesystem may be corrupted.



#1 Updated by emmapeel 2018-05-04 08:51:28

  • Assignee set to alant
  • QA Check set to Info Needed
  • Affected tool set to Greeter

I assign this ticket to you alant so you can triage it as part of the new Greeter UX feedback

#2 Updated by intrigeri 2019-06-02 15:20:23

  • Status changed from New to Confirmed
  • Assignee deleted (alant)
  • QA Check deleted (Info Needed)

#3 Updated by intrigeri 2020-04-15 06:02:16

  • Affected tool changed from Greeter to Welcome Screen