Bug #17166

Unknown escape sequence in tails-gdm-failed-to-start.service

Added by segfault 2019-10-19 15:06:56 . Updated 2019-12-17 03:13:36 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Target version:
Tails_4.1.1
Start date:
Due date:
% Done:

100%

Feature Branch:
bugfix/17166-fix-unknown-escape-sequence
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The journal of a booted 4.0~rc1 image contains this message:

/lib/systemd/system/tails-gdm-failed-to-start.service:11: Ignoring
unknown escape sequences: "MAX_LENGTH=254 ;       PREFIX="Error starting
GDM with your graphics card: " ;       SUFFIX=". Please take note of
this error and visit https://tails.boum.org/gdm for troubleshooting." ;
      MAX_VIDEO_CARD_LENGTH=$(($MAX_LENGTH - $(echo -n "$PREFIX$SUFFIX"
| wc -c))) ;       VIDEO_CARD=$(lspci -d::0300 -nn | sed -E "s,.* VGA
compatible controller \[0300\]: *,," | cut -c
"1-$MAX_VIDEO_CARD_LENGTH") ;       /bin/plymouth display-message
--text="$PREFIX$VIDEO_CARD$SUFFIX"      "

Subtasks

History

#1 Updated by segfault 2019-10-19 15:07:11

  • Target version set to Tails_4.0

#2 Updated by intrigeri 2019-10-19 15:20:15

FTR and FWIW: this has been the case since I implemented this feature. I did not manage to fix it back then, but (at least back then) it did not prevent this feature from working. I don’t recall testing it on Buster though, so possibly with a newer systemd things are different.

#3 Updated by intrigeri 2019-10-21 11:46:18

  • Target version changed from Tails_4.0 to Tails_4.1

#4 Updated by segfault 2019-12-03 09:28:37

  • Status changed from Confirmed to Needs Validation
  • Assignee changed from segfault to intrigeri
  • Target version changed from Tails_4.1 to Tails_4.2
  • Feature Branch set to bugfix/17166-fix-unknown-escape-sequence

Forgot that I already had a branch on which this is fixed.

#5 Updated by segfault 2019-12-03 09:34:53

  • Status changed from Needs Validation to In Progress

Applied in changeset commit:tails|f27236ef33901ab208d7405cd3720acac25eb50e.

#6 Updated by intrigeri 2019-12-05 20:08:07

  • Status changed from In Progress to Needs Validation

I’m assuming the previous status change was a mistake.

#7 Updated by segfault 2019-12-06 09:59:49

intrigeri wrote:
> I’m assuming the previous status change was a mistake.

Correct.

#8 Updated by intrigeri 2019-12-13 09:51:27

  • Status changed from Needs Validation to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|3d1a4029a158ddd4f0b377d77fef35bb863a69ad.

#9 Updated by CyrilBrulebois 2019-12-17 03:13:36

  • Target version changed from Tails_4.2 to Tails_4.1.1

Adjusting target version, it’s getting released in 4.1.1 instead of the planned 4.2 (only bugfix in addition to Bug #17320).