openQA Project (public) » openQA Tests (public)

Created:
https://bugzilla.suse.com/show_bug.cgi?id=1168979

Workaround still needed

New occurrence found.

gnome build 205.1:

• Screen got locked and screen saver executed after several minutes of inactivity
• After switching to TTY with graphical session, the screen buffer (outdated) shows generic-desktop
  • https://openqa.suse.de/tests/4314536#step/consoletest_finish/11
  • ensure_unlocked_desktop accepts the generic-desktop without causing the module to fail nor recording a soft-fail.
• After some delay, the screen shows the real screen content (screen lock)
  • https://openqa.suse.de/tests/4314536#step/consoletest_finish/12

gnome build 209.2:

• Screen got locked and screen saver executed after several minutes of inactivity
• After switching to TTY with graphical session, the screen buffer (outdated) shows desktop with authentication dialog for repository updates
  • https://openqa.suse.de/tests/4349081#step/consoletest_finish/11
  • ensure_unlocked_desktop thinks it is real and try to type the password
• After some delay, the screen shows the real screen content (screen lock) and the typed password went actually to the unlock dialog
  • https://openqa.suse.de/tests/4349081#step/consoletest_finish/12
  • but unsure_unlocked_desktop thought that the authentication dialog was real and after typing the password is looking for the authenticate button to assert_and_click, then times out and fail

Here we go again: https://openqa.suse.de/tests/4711944#step/shutdown/7

That gives more time to think about an implementation of the bug detection that everyone can agree with.

Have you thought about something?

szarate wrote:

Here we go again: https://openqa.suse.de/tests/4711944#step/shutdown/7

That gives more time to think about an implementation of the bug detection that everyone can agree with.

Have you thought about something?

I didn't have time to look at it yet.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11180 is related

A recommended approach for this issue is to create a new module that will disable the screensaver.
The implementation is probably not as straightforward, since disabling the screensaver is different for different environments.

geor wrote:

A recommended approach for this issue is to create a new module that will disable the screensaver.
The implementation is probably not as straightforward, since disabling the screensaver is different for different environments.

maybe you try to solve a different problem and I misunderstood but there is already https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/x11/disable_screensaver.pm for multiple, different environments. I assume you maybe suggested to create a new module because you simply did not know about the already existing one?

geor wrote:

A recommended approach for this issue is to create a new module that will disable the screensaver.
The implementation is probably not as straightforward, since disabling the screensaver is different for different environments.

Another is simply uninstall the screensaver as soon as the installation is finished, the dpms capabilities are still to be disabled.

okurz wrote:

geor wrote:

A recommended approach for this issue is to create a new module that will disable the screensaver.
The implementation is probably not as straightforward, since disabling the screensaver is different for different environments.

maybe you try to solve a different problem and I misunderstood but there is already https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/x11/disable_screensaver.pm for multiple, different environments. I assume you maybe suggested to create a new module because you simply did not know about the already existing one?

In general the problem is that having the screensaver causes a lot of side problems, so ideally we'll only run it on default scenarios to avoid having to deal with https://bugzilla.suse.com/show_bug.cgi?id=1168979 for instance

I was not aware of such module, thanks oli!

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.