Project

General

Profile

Actions

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.

Status:
Rejected
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 35+
Start date:
2018-11-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.1-NET-x86_64-update_Leap_42.1_gnome@64bit-2G fails in
gnome_control_center

Reproducible

Sporadic

Expected result

Last good: 350.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 7 (0 open7 closed)

Related to openQA Tests (public) - 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 displaymanagerResolvedmgriessmeier2019-01-23

Actions
Related to openQA Tests (public) - action #40112: [sle][functional][u][fast] test fails in consoletest_finish - ensure_unlocked_desktop seems to be failedResolvedmgriessmeier2018-08-22

Actions
Related to openQA Tests (public) - action #45131: [functional][u] test fails in worker to unlock the screen of openQA-in-openQA testRejectedmgriessmeier2018-12-13

Actions
Related to openQA Tests (public) - action #42665: [opensuse][functional[u] test fails in updates_packagekit_gpk - xscreensever is active when test switches back to x11Resolvedggardet_arm2018-10-18

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

Actions
Is duplicate of openQA Tests (public) - 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 ttyResolvedSLindoMansilla2019-01-04

Actions
Blocked by openQA Tests (public) - action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays)Resolvedszarate2019-01-042019-02-08

Actions
Actions #1

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
Actions #2

Updated by okurz about 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

Actions #3

Updated by okurz about 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

Actions #4

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

Actions #5

Updated by okurz almost 6 years ago

  • Priority changed from Normal to High

linked to currently failing tests

Actions #6

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
Actions #7

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

Actions #8

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
Actions #9

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
Actions #10

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
Actions #11

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
Actions #12

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
Actions #13

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))
Actions #14

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
Actions #15

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

Actions #16

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: gnome@Laptop_64-2G
https://openqa.opensuse.org/tests/862763

Actions #17

Updated by okurz almost 6 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
Actions #18

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 24 to Milestone 25
Actions #19

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.

Actions #20

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions #21

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 26 to Milestone 28
Actions #22

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 28 to Milestone 35+
Actions #23

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)
Actions #24

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
Actions #25

Updated by SLindoMansilla over 4 years ago

  • Status changed from Blocked to Rejected

As duplicate of #48110

Actions

Also available in: Atom PDF