Actions
action #107371
closed[desktop][qe-core] Leap 15.4 test fails in xterm - the expected string is not typed into xterm as the windows is not focused
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-02-23
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
Observation¶
Seems like xterm starts just fine, but either the text is incorrectly passed to the stdin or there is a bug in xterm.
openQA test in scenario opensuse-15.4-NET-x86_64-gnome@64bit-2G fails in
xterm
Test suite description¶
Revert schedule to working settings - dleuenberger, 20211117
Reproducible¶
Fails since (at least) Build 135.2
Expected result¶
Last good: 130.2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by zcjia about 2 years ago
- Subject changed from Leap 15.4 test fails in xterm - the expected string is not typed into xterm to [desktop] Leap 15.4 test fails in xterm - the expected string is not typed into xterm
The xterm window is not focused.
Updated by lkocman almost 2 years ago
- Subject changed from [desktop] Leap 15.4 test fails in xterm - the expected string is not typed into xterm to [desktop] Leap 15.4 test fails in xterm - the expected string is not typed into xterm as the windows is not focused
Updated by lkocman almost 2 years ago
Updated by mloviska almost 2 years ago
- Is duplicate of action #109924: [qe-core] Leap 15.4 / arm test fails in xterm - no text is written into xterm on aarch64 added
Updated by mloviska almost 2 years ago
Fails also in another modules that are using xterm https://openqa.suse.de/tests/8909744#step/keymap_or_locale_x11/23
Updated by mloviska almost 2 years ago
- Subject changed from [desktop] Leap 15.4 test fails in xterm - the expected string is not typed into xterm as the windows is not focused to [desktop][qe-core] Leap 15.4 test fails in xterm - the expected string is not typed into xterm as the windows is not focused
Updated by zcjia about 1 year ago
- Status changed from New to Resolved
Similar to https://progress.opensuse.org/issues/107386, this should be resolved as well.
Actions