Hazardous displays when coming back from sleep state

Pierre Wilch, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect 1739322

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Pierre Wilch:

1) Could you please attach a picture of the display that demonstrates this problem?

2) Is this something that started to happen after an update?

3) Could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

A new xorg version has been installed yesterday 14.02.2018.
I could make a video of the problem on my screen before that installation, and have joined it.
The bug as posted is still active with the new version.
It is not easy to reproduce. Sometimes it comes often, sometimes not.
Open and close several windows, switch between tasks..., or verify source code.
So long I remember, this bug appeared before september 2017. No problem in year 2016.
On the video one can see that abnormal blinking stops on next going into sleep state.

Pierre Wilch:

1)
>"So long I remember, this bug appeared before september 2017. No problem in year 2016."

What version of Ubuntu were you using in 2016 when this was not reproducible?

2) To further root cause, could you please test for this problem by logging into a GNOME Flashback (Metacity) session via https://launchpad.net/ubuntu/+source/gnome-flashback and advise to the results?

Christopher M. Penalver,

Thank you for your help.

1)  I was using Ubuntu 16.04 since July 2016, and 14.04 before.
I think the problem appeared in spring or summer 2017 with an update.
I do not remember since when I put the seconds display in the upper bar.
I think already in 2014, but without warranty.
In May 2017 I changed my hard disk from a 320 GB with Windows 10 in dual
boot UEFI to a 1 TB without Windows, and made a fresh install of Ubuntu
16.04 only.
I do not remember if the problem came at that time or later. There were
many things to think about,... and other serious problems with the 16.04
(now solved) .

2)  I clicked on your link about GNOME Flashback, tried a couple of
clicks, but did not find the way to log in.
How should I do?
What is Metacity?

On the video I joined notice that the blinking of the screen happens
simultaneously with the display of the seconds. You can improve the
description in this way.

I discovered Ubuntu in April 2014.
At the beginning it worked by me on a SD card (legacy) to see what it
was about, and since that time I have learned a lot, and it is not finished.
With Ubuntu/linux it is never finished.

Le 15/02/2018 à 19:16, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> 1)
>> "So long I remember, this bug appeared before september 2017. No problem in year 2016."
> What version of Ubuntu were you using in 2016 when this was not reproducible?
>
> 2) To further root cause, could you please test for this problem by logging into a GNOME Flashback (Metacity) session via https://launchpad.net/ubuntu/+source/gnome-flashback and advise to the results?
>
> ** Description changed:
>
> - Ubuntu 16.04.3 LTS, every updates done.
> -
> Conditions:
> - in the upper bar the display of the seconds must be enabled
> - (in my case the entire date-and-time is displayed, excepted the week number);
> - - system has set himself automatically in sleep state after the selected delay
> - (in my case the option "lock the keyboard" is not enabled).
> +   (in my case the entire date-and-time is displayed, excepted the week number);
> + - system is set to automatically go into sleep state after the selected delay
> +   (in my case the option "lock the keyboard" is not enabled).
> On awakening, for example by using the shift touch, parts of the screen are blinking according to 1 second rate and 3 seconds cycle.
> - Coming back to normal behavior needs to close and re-open windows (no!, not M$), etc...
> + Coming back to normal behavior needs to close and re-open windows.
>
> To help to reproduce:
> - edit a message with thunderbird;
> - select ubuntu "parameters";
> - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
> - select "1 minute";
> - wait 1 minute and going into sleep state;
> - when in sleep state press the "shift" key;
> and then I have a blinking "Christmas tree", too complicated to be described.
> I tested it again 3 times why writing this post (firefox had also an opened window, under thunderbird; with firefox alone, the screen blinks only one time -should also not-).
> - When the seconds are not displayed in the upper bar there is no ...

Pierre Wilch:

Regarding GNOME Flashback, one would have to install it via a terminal:
sudo apt-get install gnome-session-flashback

Once installed, and you restart to the login screen, GNOME Flashback (Metacity) should be an option.

Christopher M. Penalver,

- I tried to reproduce the problem after login with GNOME Flashback
(Metacity) for 2 days.
I tried many things, but without success, everything worked perfectly.

- By awakening with Unity, the display comes back during one second,
then every time becomes black again during another second, and then
stays on with or without the blinking problem of parts of the screen.
With Metacity, as a normal behavior, the screen does not become black
again during one second, and the display is immediately good, as expected.
The screen becoming black again is not normal and is a sign for a not
mastered screen processing, pieces of code taking their liberty for
undesirable results.

- I have noticed that the problem has more chance to occur after opening
and closing several windows, and switching between them. Again today.

- It is possible that the problem appeared with the kernel release which
began to manage Intel graphic cards.
I remember, without warranty, having feared the worse at that moment,
_before_. Since, perhaps with Unity a crazy process is remaining on
awakening.

Pierre Wilch

Le 16/02/2018 à 01:20, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> Regarding GNOME Flashback, one would have to install it via a terminal:
> sudo apt-get install gnome-session-flashback
>
> Once installed, and you restart to the login screen, GNOME Flashback
> (Metacity) should be an option.
>

Pierre Wilch, given this issue only happens when using Unity, I'll reassign to Unity so a specialist may review.