action #64812
open[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
0%
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
Updated by okurz about 4 years ago
- Related to action #64896: [SLE][Migration][SLE15SP2][Regression]test fails in consoletest_finish added
Updated by SLindoMansilla about 4 years ago
- Description updated (diff)
- Status changed from New to Workable
- Estimated time set to 42.00 h
Updated by jorauch about 4 years ago
Created:
https://bugzilla.suse.com/show_bug.cgi?id=1168979
Workaround still needed
Updated by jorauch about 4 years ago
- Status changed from Workable to Feedback
Created:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10064
Waiting for Input and feedback
Updated by SLindoMansilla almost 4 years ago
- Related to action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenarios added
Updated by SLindoMansilla almost 4 years 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.
Updated by SLindoMansilla almost 4 years 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
Updated by SLindoMansilla almost 4 years ago
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_desktopaccepts 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)
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_desktopthinks 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_desktopthought that the authentication dialog was real and after typing the password is looking for the authenticate button toassert_and_click, then times out and fail
Updated by SLindoMansilla almost 4 years ago
- Status changed from Workable to In Progress
- Priority changed from Low to High
Updated by szarate over 3 years 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?
Updated by szarate over 3 years ago
- Related to action #71656: [functional][u] test fails in shutdown - Force shutdown module to use textmode for create_hdd scenarios added
Updated by SLindoMansilla over 3 years 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.
Updated by szarate over 3 years 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
Updated by szarate over 3 years ago
Updated by tjyrinki_suse over 3 years 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
Updated by geor about 3 years 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.
Updated by okurz about 3 years 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?
Updated by szarate about 3 years 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!
Updated by tjyrinki_suse almost 3 years 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
Updated by tjyrinki_suse almost 3 years ago
- Status changed from Workable to New
- Start date deleted (
2020-03-25)
setting to New until refined
Updated by okurz almost 3 years ago
- Related to action #89329: [qe-core] test fails in shutdown - Machine didn't shut down added
Updated by okurz over 2 years 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
Updated by slo-gin over 1 year ago
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.
Updated by slo-gin about 1 month ago
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.