Feature #15399

Write https://tails.boum.org/gdm

Added by sajolida 2018-03-12 17:26:07 . Updated 2018-04-20 10:05:38 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Hardware support
Target version:
Start date:
2018-03-12
Due date:
% Done:

0%

Feature Branch:
doc/15399-gdm-debugging
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Pointed to from config/chroot_local-includes/lib/systemd/system/tails-gdm-failed-to-start.service.


Subtasks


Related issues

Blocks Tails - Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing Resolved 2018-03-14

History

#1 Updated by intrigeri 2018-03-12 22:54:06

Just in case you missed it, once the 3.6 release is out in theory this link will stop being broken:

RewriteRule ^gdm/?$ doc/first_steps/bug_reporting/#does_not_start [R,NE]

#2 Updated by sajolida 2018-03-13 09:47:16

Yeah, I saw that as well and it will be good enough as a start. But as I was saying on tails-ux this link is not very good either.

https://mailman.boum.org/pipermail/tails-ux/2018-February/003528.html

#3 Updated by sajolida 2018-03-13 13:06:52

  • Status changed from Confirmed to In Progress
  • Target version changed from Tails_3.6 to Tails_3.7

Proposal sent: https://mailman.boum.org/pipermail/tails-dev/2018-March/012050.html.

#4 Updated by sajolida 2018-04-12 09:30:54

  • blocks Feature #15411: Core work 2018Q2 → 2018Q3: Technical writing added

#5 Updated by sajolida 2018-04-12 15:31:52

  • Assignee changed from sajolida to intrigeri
  • QA Check set to Ready for QA

I think that this page is ready for review. Yeah, feels good to clean up a bit our known issues.

I’m assigning the review to intrigeri and not Cody because I’m more worried about the correctness of the technical details than about the writing in itself.

#6 Updated by intrigeri 2018-04-13 07:39:05

  • Feature Branch set to doc/15399-gdm-debugging

#7 Updated by intrigeri 2018-04-13 07:47:25

  • Assignee changed from intrigeri to sajolida
  • QA Check changed from Ready for QA to Dev Needed
  • I would write The ID is *10de:0a6c* instead of The ID is *[10de:0a6c]*.
  • s/If your problem get fixed in future versions/If your problem gets fixed in a future version/
  • The NVIDIA Pascal section links to the list of Maxwell models.
  • “software package in Tails” ← missing verb?

Other than that and without having actually built the page, looks good to me!

#8 Updated by sajolida 2018-04-20 10:05:38

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Dev Needed)

> I would write The ID is 10de:0a6c instead of The ID is [10de:0a6c].

I prefer putting the brackets because I think it will help people scan and identify these bits.

> s/If your problem get fixed in future versions/If your problem gets fixed in a future version/

Fixed!

> The NVIDIA Pascal section links to the list of Maxwell models.

Fixed!

> “software package in Tails” ← missing verb?

The verb is “install” and it’s in the link on the line before. Granted, it might not be the best link we’ve ever wrote…

Thanks for the review. I’m happy I got the technicalities right and now I can merge!