I have reinstalled Ubuntu 16.04 LTS and the problem is resolved

[Christian Fortin]

La première fois que je boot, il y a environ 2cm de sur toute la largeur qui a des pixels aléatoires et l'écran gèle. Je ferme et réallume et il boot correctement et le cycle revient à chaque fois que j'allume mon ordi

Carte:G33X86/MMX/SSE2
SUR UBUNTU 16.04 32BITS
COMME PROCESSEUR Intel® Pentium(R) Dual CPU E2200 @ 2.20GHz × 2

===
Google translation:

The first time I boot, there is about 2cm of all the width that has random pixels and the screen freezes. I close and turn on and boot properly and the cycle comes back every time I turn on my computer

Map: G33X86 / MMX / SSE2
ON UBUNTU 16.04 32BITS
AS PROCESSOR Intel® Pentium® Dual CPU E2200 @ 2.20GHz × 2
===

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1829634/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

There's too little information about your original installation to work on this bug report. If the problem has been resolved can we close this bug report?

[Christian Fortin (forc32)]

Yes you can close the report

[Paul White (paulw2u)]

Thanks Christian.

I'll mark the report "Invalid" as the cause of the problem was never ascertained and it's no longer possible to establish whether the cause was a configuration error or not.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]