Project

General

Profile

action #64812

[qe-core][functional][sporadic][needs-refining] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later

Added by SLindoMansilla over 1 year ago. Updated 6 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Reproducible

  • In scenario sle-15-SP2-Online-aarch64-create_hdd_gnome@aarch64
  • Fails since Build 150.1
  • Current occurrence: 164.1

Expected result

Last good: 155.1

Suggestions

- Create a product bug about the screen buffer still showing the last screen instead of the locked screen (security issues + bad UX) bsc#1168979

  • Workaround ensure_unlocked_desktop to take into account an outdated screen buffer.

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #64896: [SLE][Migration][SLE15SP2][Regression]test fails in consoletest_finish Resolved2020-03-27

Related to openQA Tests - action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenariosWorkable2018-08-31

Related to openQA Tests - action #71656: [functional][u] test fails in shutdown - Force shutdown module to use textmode for create_hdd scenariosRejected2020-09-22

Related to openQA Tests - action #89329: [qe-core] test fails in shutdown - Machine didn't shut downNew2021-03-02

Has duplicate openQA Tests - action #67885: [sle][functional][u] test fails in consoletest_finish - ensure_unlocked_desktop still looks for "authenticate" when login screen is shownRejected2020-06-09

History

#1 Updated by SLindoMansilla over 1 year ago

  • Description updated (diff)

#2 Updated by okurz over 1 year ago

  • Related to action #64896: [SLE][Migration][SLE15SP2][Regression]test fails in consoletest_finish added

#3 Updated by SLindoMansilla over 1 year ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 42.00 h

#4 Updated by jorauch over 1 year ago

  • Assignee set to jorauch

#5 Updated by jorauch over 1 year ago

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

Workaround still needed

#6 Updated by jorauch over 1 year ago

  • Status changed from Workable to Feedback

#7 Updated by SLindoMansilla over 1 year ago

  • Related to action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenarios added

#8 Updated by SLindoMansilla over 1 year ago

  • Status changed from Feedback to Workable
  • Assignee changed from jorauch to SLindoMansilla
  • Priority changed from High to Low
  • Target version changed from Milestone 30 to future

Since https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10217 was merged
test will not fail.

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

#9 Updated by SLindoMansilla about 1 year ago

  • Has duplicate action #67885: [sle][functional][u] test fails in consoletest_finish - ensure_unlocked_desktop still looks for "authenticate" when login screen is shown added

#10 Updated by SLindoMansilla about 1 year ago

New occurrence found.

gnome build 205.1:

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
  • After some delay, the screen shows the real screen content (screen lock) and the typed password went actually to the unlock dialog

#11 Updated by SLindoMansilla about 1 year ago

  • Status changed from Workable to In Progress
  • Priority changed from Low to High

#12 Updated by szarate 12 months ago

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?

#13 Updated by szarate 12 months ago

  • Related to action #71656: [functional][u] test fails in shutdown - Force shutdown module to use textmode for create_hdd scenarios added

#14 Updated by SLindoMansilla 12 months ago

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.

#15 Updated by szarate 11 months ago

  • Description updated (diff)
  • Status changed from In Progress to Workable
  • Assignee deleted (SLindoMansilla)
  • Target version changed from future to Milestone 30

I'm thinking to catch it here:

https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/x11utils.pm#L77

if it's the first loop, and the screen is not, display manager, screen locked or something like this, try again, if the matches belong to something post auth, report the soft failure

#17 Updated by tjyrinki_suse 11 months ago

  • Subject changed from [functional][u][sporadic] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later to [qe-core][functional][sporadic] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later

#18 Updated by geor 7 months ago

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.

#19 Updated by okurz 7 months ago

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?

#20 Updated by szarate 7 months ago

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!

#21 Updated by tjyrinki_suse 5 months ago

  • Subject changed from [qe-core][functional][sporadic] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later to [qe-core][functional][sporadic][needs-refining] test fails in shutdown - Screen buffer shows old display state instead of locked screen, ensure_unlocked_desktop thinks it is unlocked and test fails later

#22 Updated by tjyrinki_suse 4 months ago

  • Status changed from Workable to New
  • Start date deleted (2020-03-25)

setting to New until refined

#23 Updated by okurz 2 months ago

  • Related to action #89329: [qe-core] test fails in shutdown - Machine didn't shut down added

#24 Updated by okurz 20 days ago

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

#25 Updated by tjyrinki_suse 6 days ago

  • Priority changed from High to Normal

Also available in: Atom PDF