Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 927
    • Issues 927
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11392
Closed
Open
Created Apr 29, 2016 by elouann@elouann

Tails does not start: document workarounds to reach debug information

Originally created by @elouann on #11392 (Redmine)

A user was able to bypass the greeter by removing ‘noautologin’ from the boot options: the desktop loads directly. Then it’s possible to get more informations with ‘sudo tails-debugging’, which works without admin password

This should be added somewhere in the documentation, maybe here:
https://tails.boum.org/doc/first_steps/bug_reporting/tails_does_not_start/#entirely

The documentation must say that the resulting system will have undefined (and potentially dangerous) behaviour and should not be used for anything else than bug reporting

Related issues

  • Related to #11095 (closed)
  • Related to #7323 (closed)
  • Related to #15130
Edited May 15, 2020 by elouann
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking