Project

General

Profile

action #111752

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

Added by mloviska 3 months ago. Updated 9 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-05-30
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

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

History

#1 Updated by punkioudi 3 months 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 :)

#2 Updated by mloviska 2 months ago

#3 Updated by mloviska 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska

#4 Updated by okurz 2 months ago

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

#6 Updated by mloviska about 1 month ago

Haven't seen a xterm failure lately

#7 Updated by mloviska about 1 month ago

  • Status changed from In Progress to Resolved

#9 Updated by mloviska 21 days 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

#10 Updated by mloviska 20 days 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

#11 Updated by mloviska 19 days 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.

#13 Updated by mloviska 16 days 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

#14 Updated by mloviska 16 days ago

  • Status changed from In Progress to Feedback

Also available in: Atom PDF