Bug #11392

Tails does not start: document workarounds to reach debug information

Added by elouann 2016-04-29 15:19:03 . Updated 2018-03-01 17:41:01 .

Status:
Rejected
Priority:
Normal
Assignee:
emmapeel
Category:
Hardware support
Target version:
Start date:
2016-04-29
Due date:
% Done:

10%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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

Subtasks

Related issues

Related to Tails - Bug #11095: GNOME session fails to start with some AMD/ATI radeon GPU Resolved 2016-02-09
Related to Tails - Bug #7323: Wheezy's GNOME crashes randomly after Greeter login Rejected 2014-06-12
Related to Tails - Feature #15130: Restructure our support page and content Confirmed 2013-09-28

History

#1 Updated by elouann 2016-04-29 15:47:58

  • Subject changed from Tails does not start : document a workaround to reach Whisperback to Tails does not start : document workarounds to reach debug informations

#3 Updated by BitingBird 2016-06-29 06:45:54

  • related to Bug #11095: GNOME session fails to start with some AMD/ATI radeon GPU added

#4 Updated by BitingBird 2016-06-29 06:47:17

  • related to Bug #7323: Wheezy's GNOME crashes randomly after Greeter login added

#5 Updated by intrigeri 2016-08-11 10:51:59

  • Subject changed from Tails does not start : document workarounds to reach debug informations to Tails does not start: document workarounds to reach debug information

#6 Updated by intrigeri 2016-08-11 10:53:17

  • Category set to Hardware support
  • Assignee set to elouann

(As said on Bug #11095#note-13, to me it looks like this is on frontdesk’s plate. I assume it was an oversight not to assign this ticket to anyone when it was created.)

#7 Updated by Anonymous 2017-06-29 10:00:08

ping? This should be documented as part of the frontdesk role.

#8 Updated by mercedes508 2018-01-12 15:47:46

  • Assignee changed from elouann to sajolida

u wrote:
> ping? This should be documented as part of the frontdesk role.

Re-assigning to tech writers :)

#9 Updated by Anonymous 2018-01-17 15:07:54

  • Description updated

#10 Updated by Anonymous 2018-01-17 15:08:07

  • related to Feature #15130: Restructure our support page and content added

#11 Updated by sajolida 2018-02-16 20:39:05

  • Assignee changed from sajolida to emmapeel
  • QA Check set to Info Needed

This trick bypasses Tails Greeter to go directly to the desktop. I don’t understand in which circumpstances this can be useful: if people can’t get to Tails Greeter I guess that they won’t get to the desktop anyway. And if they can get to the desktop, then what is there to debug with this trick?

So I would reject this ticket but I need a confirmation from Help desk…

#12 Updated by emmapeel 2018-02-28 18:39:33

  • % Done changed from 0 to 10

I will ask in frontdesk meeting what the others think, I think there is already some work on improving the experience of users when GNOME does not start already, not sure if this workarounds are needed.

#13 Updated by emmapeel 2018-03-01 17:41:01

  • Status changed from Confirmed to Rejected

yes, we confirm we dont give this instructions.