action #45710
closed
[functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays)
Added by mlin7442 over 5 years ago.
Updated about 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
- Subject changed from test fails in NM_wpa2_enterprise - screenlock displays to [functional][u] test fails in NM_wpa2_enterprise - screenlock displays
- Related to action #45131: [functional][u] test fails in worker to unlock the screen of openQA-in-openQA test added
- Related to action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added
- Related to action #40490: [qe-core][functional] Implement test for screensaver and disable it in other scenarios added
- Related to action #39734: [aarch64] test fails in updates_packagekit_gpk / updates_packagekit_kde due to locked screensaver added
- Related to action #36652: [sle][functional][u] test fails in first_boot - screensaver already active after boot to desktop? added
- Priority changed from Normal to High
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.opensuse.org/tests/841035
- Due date set to 2019-02-08
ping! this keeps failing. we need an ETA for a fix
- Status changed from New to Workable
- Priority changed from High to Urgent
- Target version set to Milestone 22
- Subject changed from [functional][u] test fails in NM_wpa2_enterprise - screenlock displays to [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays)
- Description updated (diff)
- Status changed from Workable to In Progress
- Assignee set to SLindoMansilla
- Priority changed from Urgent to High
- Status changed from In Progress to Workable
- Assignee deleted (
SLindoMansilla)
Hm, I am not exactly sure what fixed the scenario but definitely not your PR as it is not yet merged. https://openqa.opensuse.org/tests/844167 is the latest job that worked again after a longer time. I don't think your PR is a good idea though. The switching to the text terminal and back happens within a minute so the screen shouldn't even be locked unless this is some feature that I do not know about. @SLindoMansilla it seems you have ignored all my suggestions from the description? Leaving for someone else during his absence.
- Related to deleted (action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock)
- Blocks action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added
- Target version changed from Milestone 22 to Milestone 23
Do we run this scenario for SLED?
- Status changed from Workable to Feedback
- Assignee set to szarate
yes, what I suggested as an alternative. Feel free to extract the part about "switching back to x11 does needs re-login" into another ticket or solve it within this one.
- Status changed from Feedback to Resolved
- Copied to 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
ok, I guess you somehow missed my comments so I will create a new ticket for the further improvement. -> #48110
@okurz sorry! my bad! I was going to put those on a separate ticket, but thanks for taking care!
- Has duplicate action #42740: [functional][u] test fails in NM_wpa2_enterprise - console switch fails because of messages on the console added
Also available in: Atom
PDF