Project

General

Profile

Actions
Copy link

action #111752

closed

[leap][qe-core] test fails in xterm - mistyping test string due to lost focus

Added by mloviska over 2 years ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
dzedro
Category:
Bugs in existing tests
Target version:
QA - QE-Core: Ready
Start date:
2022-05-30
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
bugbusters

Description

Observation

openQA test in scenario opensuse-15.4-Leap-DVD-Incidents-x86_64-gnome@64bit fails in
xterm

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainer: slindomansilla

The standard scenario where we mainly just follow installation suggestions without any adjustments as long as the default desktop is gnome.

Reproducible

Fails since (at least) Build :24410:vim (current job)

Expected result

Last good: :24409:vim (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #110542: Try to mitigate "VNC typing issues" with disabled key repeatResolvedokurz2022-05-02

Actions
Actions
Copy link
 #1

Updated by punkioudi over 2 years ago

  • Tags set to bugbusters
  • Status changed from New to Workable
  • Target version set to QE-Core: Ready

It seems to me like a sporadical issue. I will add it in the bugbusters list, but with a normal priority :)

Actions
Copy link
 #2

Updated by mloviska over 2 years ago

Actions
Copy link
 #3

Updated by mloviska over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska
Actions
Copy link
 #4

Updated by okurz over 2 years ago

  • Related to action #110542: Try to mitigate "VNC typing issues" with disabled key repeat added
Actions
Copy link
 #6

Updated by mloviska over 2 years ago

Haven't seen a xterm failure lately

Actions
Copy link
 #7

Updated by mloviska over 2 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #9

Updated by mloviska over 2 years ago

xterm does not run as native Wayland application, but as XWayland.

localhost  gsd-xsettings
localhost.localdomain  gnome-shell
localhost.localdomain  spice-vdagent
localhost.localdomain  xterm
localhost.localdomain  xterm

AFAICT, the lost focus appears mostly right after reboot of the machine.
Adding a sleep call in updates_packagekit_gpk::setup_system before executing x11_start_program does not show the issue anymore. Maybe we are dealing with some race condition, however I have not reproduced the issue outside openQA

Actions
Copy link
 #10

Updated by mloviska over 2 years ago

Seems like the lost focus happens when a X11 application is started before Xwayland

UID        PID  PPID  C STIME TTY          TIME CMD
bernhard  1683  1253  0 09:29 ?        00:00:00 xcalc ---> started w/o focus
bernhard  1684  1253  0 09:29 ?        00:00:00 /usr/bin/Xwayland :0 -rootless -
bernhard  1824  1253  0 09:30 ?        00:00:00 xterm ---> started w/ focus

they all have a common parent 

UID        PID  PPID  C STIME TTY          TIME CMD
bernhard  1253  1172  2 09:29 ?        00:00:13 /usr/bin/gnome-shell
Actions
Copy link
 #11

Updated by mloviska over 2 years ago

GNOME focus default settings for new windows is set to smart, seemingly changing the option to strict might fix our sporadic stealing windows focus issue.

Actions
Copy link
 #13

Updated by mloviska over 2 years ago

  • Subject changed from [leap][qe-core] test fails in xterm - mistyping test string to [leap][qe-core] test fails in xterm - mistyping test string due to lost focus
Actions
Copy link
 #14

Updated by mloviska over 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #16

Updated by apappas about 2 years ago

  • Status changed from Feedback to Workable

This has been appearing a log lately, and the PR has stalled, so, after discussing it with Martin I am putting this back to the bug buster queue.

Actions
Copy link
 #17

Updated by apappas about 2 years ago

  • Assignee deleted (mloviska)
Actions
Copy link
 #18

Updated by apappas about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to apappas
Actions
Copy link
 #19

Updated by VANASTASIADIS almost 2 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (apappas)
Actions
Copy link
 #20

Updated by apappas almost 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to apappas
Actions
Copy link
 #21

Updated by dzedro almost 2 years ago

  • Assignee changed from apappas to dzedro
Actions
Copy link
 #22

Updated by zcjia almost 2 years ago

  • Status changed from In Progress to Resolved

I added 'x11_start_program_xterm' in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16339 .

I use it instead of 'x11_start_program(xterm)' in 'ensure_installed' already.

If this problem persists, for example in "updates_packagekit_gpk", then we do the replace there again to resolve the problem.

Actions
Copy link
 #23

Updated by openqa_review 6 months ago

  • Status changed from Resolved to Feedback

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: qam-gnome
https://openqa.suse.de/tests/14520928

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 92 days if nothing changes in this ticket.

Actions
Copy link
 #24

Updated by dzedro 6 months ago

  • Status changed from Feedback to Resolved

It failed because ssxhterm for some reason didn't kill all xterms. https://openqa.suse.de/tests/14520928#step/sshxterm/6

Actions
Copy link

Also available in: Atom PDF