Bugzilla – Bug 1226838
[Build 20240622] openQA test fails in consoletest_finish: unlocking screen, we see kde runner (?)
Last modified: 2024-06-24 09:13:51 UTC
## Observation The test fails in consoletest_finish, i.e when coming back from the console tests to the graphical environmentWe shortly see the desktop, then the 'screen locker', which is properly unlocked. But then we see the 'plasma runner' - i.e we do not match the 'clean desktop' I somewhat expect a race between switching back to GUI,pressing alt-f2 and the screen locker kicking in openQA test in scenario opensuse-Tumbleweed-KDE-Live-x86_64-kde-live@64bit-3G fails in [consoletest_finish](https://openqa.opensuse.org/tests/4294886/modules/consoletest_finish/steps/22) ## Test suite description jpupava: RAM increased to 3072 firefox needs half run time and general performance is much better, defined in medium types EXCLUDE_MODULES=glibc_sanity,salt,prepare_test_data setting moved to the medium (different between Leap and TW) ## Reproducible Fails since (at least) Build [20240622](https://openqa.opensuse.org/tests/4292655) ## Expected result Last good: [20240621](https://openqa.opensuse.org/tests/4290451) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=KDE-Live&machine=64bit-3G&test=kde-live&version=Tumbleweed)