Project

General

Profile

Actions

action #51266

closed

[functional][u] test fails in shutdown as unexpected screenlock-password screen after unlocked

Added by michel_mno over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 30+
Start date:
2019-05-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

test fails in shutdown as unexpected screenlock-password screen after unlocked

On shutdown module, locked screen properly detected, and password typed correctly (step 3)
but a new screen is displayed (step 4) similar to a 'screenlock-password' needle that differ by "Unlock" button replaced by "Next" one.

https://openqa.opensuse.org/tests/927004#step/shutdown/3
https://openqa.opensuse.org/tests/927004#step/shutdown/4

I made a trial adding a new gnome-screenlock-next-password-Tumbleweed-20190507 needle but next runs failed as no change after this needle detected.
https://openqa.opensuse.org/tests/927008#step/shutdown/6

failure between 20190430 & 20190505 snapshots.

How to continue investigation ?

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-create_hdd_gnome@ppc64le fails in
shutdown

Test suite description

image creation job used as parent for other jobs testing based on existing installation. GUI-Installation and selecting the gnome desktop during installation.

Reproducible

Fails since (at least) Build 20190505

Expected result

Last good: 20190430

Further details

Always latest result in this scenario: latest


Related issues 2 (0 open2 closed)

Has duplicate openQA Tests (public) - action #51317: test fails in shutdown - Screenlock problemRejected2019-05-09

Actions
Blocked by openQA Tests (public) - action #52694: [sle][functional[[u] test fails in first_boot - boots up to desktop?Rejected2019-06-06

Actions
Actions #1

Updated by SLindoMansilla over 5 years ago

  • Subject changed from test fails in shutdown as unexpected screenlock-password screen after unlocked to [functional][u] test fails in shutdown as unexpected screenlock-password screen after unlocked
  • Priority changed from Normal to High

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions #2

Updated by SLindoMansilla over 5 years ago

  • Has duplicate action #51317: test fails in shutdown - Screenlock problem added
Actions #3

Updated by michel_mno over 5 years ago

the ppc64le and aarch64 tests both tests have gnome-shell error reported in journalctl as extracted below for 20190508

How to continue from there ?

# wait_serial expected: 'SysRq : Show Blocked State'

# Result:
gsd-color[2143]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
gsd-color[2143]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output
gdm-password][4083]: gkr-pam: unlocked login keyring
NetworkManager[1486]: <info>  [1557246359.9603] agent-manager: req[0x100107711c0, :1.21/org.gnome.Shell.NetworkAgent/1000]: agent registered
gnome-shell[1782]: Object Clutter.Text (0x10013297bd0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
org.gnome.Shell.desktop[1782]: == Stack trace for context 0x100130e8270 ==
org.gnome.Shell.desktop[1782]: #0    10015597590 i   resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7fff738c60d0 @ 25)
org.gnome.Shell.desktop[1782]: #1    100155974e8 i   resource:///org/gnome/shell/ui/main.js:491 (7fff738e1670 @ 290)
org.gnome.Shell.desktop[1782]: #2    10015597420 i   resource:///org/gnome/shell/ui/screenShield.js:1259 (7fff731c8280 @ 299)
org.gnome.Shell.desktop[1782]: #3    100155973a0 i   resource:///org/gnome/shell/ui/screenShield.js:1226 (7fff731c81f0 @ 17)
org.gnome.Shell.desktop[1782]: #4    10015597318 i   resource:///org/gnome/shell/gdm/authPrompt.js:493 (7fff731ee430 @ 61)
org.gnome.Shell.desktop[1782]: #5    10015597290 i   resource:///org/gnome/shell/ui/unlockDialog.js:129 (7fff731f8ca0 @ 25)
org.gnome.Shell.desktop[1782]: #6    10015597210 i   resource:///org/gnome/shell/ui/screenShield.js:1226 (7fff731c8160 @ 46)
org.gnome.Shell.desktop[1782]: #7    10015597190 i   resource:///org/gnome/shell/ui/screenShield.js:549 (7fff731c4670 @ 13)
org.gnome.Shell.desktop[1782]: #8    100155970c0 i   resource:///org/gnome/gjs/modules/signals.js:142 (7fff738d6670 @ 386)
org.gnome.Shell.desktop[1782]: #9    10015597020 i   resource:///org/gnome/gjs/modules/overrides/Gio.js:169 (7fff738ea3a0 @ 39)
sysrq: SysRq : Show Blocked State
Actions #4

Updated by michel_mno over 5 years ago

creating a new https://bugzilla.opensuse.org/show_bug.cgi?id=1135401 to GNOME looking for help.

Actions #5

Updated by okurz over 5 years ago

  • Subject changed from [functional][u] test fails in shutdown as unexpected screenlock-password screen after unlocked to [functional][u] test fails in shutdown as unexpected screenlock-password screen after unlocked
  • Status changed from New to Workable
  • Target version set to Milestone 25
Actions #6

Updated by zluo over 5 years ago

  • Assignee set to zluo

https://openqa.opensuse.org/tests/955235#step/shutdown/2 shows that the needle match 100%, in you case was 95% which failed.

So it means the issue looks different now. and recently test runs failed already at first_boot.
Take over for further investigation.

Actions #7

Updated by zluo over 5 years ago

  • Status changed from Workable to In Progress
Actions #9

Updated by zluo over 5 years ago

first_boot failed because of the issue https://progress.opensuse.org/issues/52694

Actions #10

Updated by zluo over 5 years ago

  • Blocked by action #52694: [sle][functional[[u] test fails in first_boot - boots up to desktop? added
Actions #11

Updated by zluo over 5 years ago

  • Status changed from In Progress to Blocked
Actions #12

Updated by michel_mno over 5 years ago

  • Status changed from Blocked to Feedback

problem disapeared at least since TW snapshot 20180626 and two other snapshots as per https://openqa.opensuse.org/tests/969680

so issue should be closed.

Actions #13

Updated by mgriessmeier over 5 years ago

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

Updated by zluo over 5 years ago

yes, it looks good now, but I want to keep it for a while since we had problem with first_boot when grub_test before it.

Actions #15

Updated by zluo over 5 years ago

  • Target version changed from Milestone 26 to Milestone 30+
Actions #16

Updated by SLindoMansilla over 5 years ago

  • Status changed from Feedback to Workable

Let's remove this from the "waiting for feedback" list

Actions #17

Updated by zluo over 5 years ago

  • Status changed from Workable to Rejected

no issue anymore, checked: https://openqa.opensuse.org/tests/985539

Actions

Also available in: Atom PDF