Comment 12 for bug 222690

Ok, so you said "stick set -x" on the second line, it's not very clear !

As we are French, could you use "Globish"... (eq very simple and not ambiguous words).

Stick, as I posted above, would have implied for me: add something to something existant, as when you stick a stamp on an enveloppe ;-)

So a little bit more details :
- first don't do the sudo nano immediately when the installer starts: I did it and got stuck in the middle of typing the command because the system apparently was doing some parallel task and output a startup instruction in the middle of the command line... then everything was blocked.

- so wait a moment before typing the command, I waited till the copy starts.

- open the file with nano
- HORROR !.. the second line appears to be completely blank. So following the instruction, I typed set -x on the second line of the file that was previously blank, that is

BEFORE
#! bash/.... (something I don't remember)

set -e

AFTER
#! bash/...
set -x
set -e

Ctrl O to save
Ctrl X to exit

Ctrl Alt F7 to go back to the installer (that I had to guess... and at the end got lucky after trying many combinations)

Wait for the bug.

Then here there is another bug, the message says the system will reboot once you click OK on the error message, but apparently it does not reboot.
So you have to power down manually the computer... and it appears sometimes the install-log.zip is not flushed to the NTFS partition and you got no log at all.

1st time = OK
2nd time = no log.

Reading the log I have the impression that it does not care with my set-x on the previously blank line (user.log)
I'll try a 3rd run with set -x on a new line after the line with set -e
And may be a fourth with a line:
set -e set -x

To avoid the "not flushing install-log" bug, the best thing I can think of is: wait for a moment after clicking OK on the error message... not very precise but I have no better idea !

Here is the first log