action #44153
closed[functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock
Added by mlin7442 about 6 years ago. Updated over 4 years ago.
0%
Description
Updated by okurz about 6 years ago
- Subject changed from test fails in gnome_control_center - fails to unlock screenlock to [functional][u] test fails in gnome_control_center - fails to unlock screenlock
- Target version set to future
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: update_Leap_42.1_gnome@64bit-2G
https://openqa.opensuse.org/tests/809859
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: zdup-Leap-42.1-gnome@64bit-2G
https://openqa.opensuse.org/tests/817384
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: update_Leap_42.1_gnome@64bit-2G
https://openqa.opensuse.org/tests/825037
Updated by okurz almost 6 years ago
- Priority changed from Normal to High
linked to currently failing tests
Updated by okurz almost 6 years ago
- Related to action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays) added
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: system_performance@64bit-2G
https://openqa.opensuse.org/tests/842027
Updated by okurz almost 6 years ago
- Related to action #46532: [functional][u] test fails in keymap_or_locale as the test fails to unlock the screenlock when it should not even care about the displaymanager added
Updated by okurz almost 6 years ago
- Related to action #40112: [sle][functional][u][fast] test fails in consoletest_finish - ensure_unlocked_desktop seems to be failed added
Updated by okurz almost 6 years ago
- Related to action #45131: [functional][u] test fails in worker to unlock the screen of openQA-in-openQA test added
Updated by okurz almost 6 years ago
- Related to action #42665: [opensuse][functional[u] test fails in updates_packagekit_gpk - xscreensever is active when test switches back to x11 added
Updated by okurz almost 6 years ago
- Related to action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenarios added
Updated by okurz almost 6 years ago
- Related to deleted (action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays))
Updated by okurz almost 6 years ago
- Blocked by action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays) added
Updated by okurz almost 6 years ago
- Subject changed from [functional][u] test fails in gnome_control_center - fails to unlock screenlock to [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock
- Description updated (diff)
- Status changed from New to Blocked
- Assignee set to okurz
- Target version changed from future to Milestone 24
As this is very specific to gnome I think we run into the same self-made problem as mentioned in #45710 . In the test module "gnome_control_center" we have an explicit "select_console" x11 which I think resolves to the tty where we have the login screen running, not the logged in session so we do the pretty useless effort to login which we could save by selecting the right tty from the beginning -> "Blocked" by #45710
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: gnome@Laptop_64-2G
https://openqa.opensuse.org/tests/862763
Updated by okurz over 5 years ago
- Blocked by action #48110: [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty added
Updated by okurz over 5 years ago
- Target version changed from Milestone 24 to Milestone 25
Updated by okurz over 5 years ago
- Assignee changed from okurz to mgriessmeier
Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25 to Milestone 26
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 26 to Milestone 28
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 28 to Milestone 35+
Updated by SLindoMansilla over 4 years ago
- Blocked by deleted (action #48110: [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty)
Updated by SLindoMansilla over 4 years ago
- Is duplicate of action #48110: [functional][u][sporadic] test failed in different modules that switch from textmode terminal to graphical terminal - unable to login into the gnome session again but we should not even need to login when selecting the correct tty added
Updated by SLindoMansilla over 4 years ago
- Status changed from Blocked to Rejected
As duplicate of #48110