Bug 1122804 - [Build 20190121] openQA test fails in user_settings with high occurence of mistyping of capital letters, potentially since submission of Qt 5.12
[Build 20190121] openQA test fails in user_settings with high occurence of mi...
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other
Current
Other Other
: P5 - None : Major (vote)
: ---
Assigned To: E-mail List
E-mail List
https://openqa.opensuse.org/tests/835...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-22 19:27 UTC by Oliver Kurz
Modified: 2020-03-22 06:52 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Kurz 2019-01-22 19:27:42 UTC
## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-RAID0@64bit fails in
[user_settings](https://openqa.opensuse.org/tests/835389/modules/user_settings/steps/3)
to type the username correctly. Very frequently, the name 'Bernhard M Wiedemann' is mistyped in openQA, most commonly with a lower-case M for the middle name. In many cases, this 'could be ignored', but often there are modules further down the line that have a login mask where the name then mismatches.


## Reproducible

Fails since about the snapshot 20181214 often but not always


## Problem

Dimstar et al also looked into this issue. Neither Leap (same openqa instance) nor SLE (different instance) seem to show this kind of issue - which in turn seems to point towards a product issue.
This issue seems to have started around snapshot 1214 - which co-incides with the checkin date of Qt 5.12

Qt 5.12 is thus a suspect for this failure.


## Further details

Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?distri=opensuse&arch=x86_64&flavor=NET&version=Tumbleweed&machine=64bit&test=RAID0)
Comment 1 Stefan Hundhammer 2019-01-23 10:09:47 UTC
I agree that this is much more likely in the area of Qt or even lower (X?).
So why is this assigned to component "Installation"?
Comment 2 Oliver Kurz 2019-01-23 12:51:40 UTC
I guess if you ask yourself you know the reason: Because "bnc-team-screening@forge.provo.novell.com" is no real person that understands the system and fix it but you can :)

I don't know enough about the whole "installation system" to judge which component is included and could have which impact. For me I can state that the installer does not work. Any choice of framework or library is internally yours. You might have even configured the library or framework somewhat. I do not know all this. So who within SUSE do you think is a better team or person to further investigate and fix it?
Comment 4 Ruediger Oertel 2019-02-15 09:18:10 UTC
trying qt maintainer
Comment 5 Max Lin 2019-02-15 09:27:45 UTC
Yes, this is an known issue, and openSUSE KDE team has been informed. As this is an issue on qt 5.12/TW, re-assign to kde-maintainers.
Comment 14 Oliver Kurz 2019-07-06 07:55:14 UTC
https://github.com/os-autoinst/os-autoinst/pull/1174 might help as a workaround on the openQA side.
Comment 17 Oliver Kurz 2020-02-06 16:41:21 UTC
Just to make sure this is not lost. In the meantime, since about 2019-10 the issue also appeared on SLE15-SP2 which was mentioned in https://progress.opensuse.org/issues/46190#note-39 as the progress ticket was used as label in https://openqa.suse.de/tests/3462442 which IMHO should have referenced this bug directly. Since then the issue can be repeatedly reproduced within SLE tests.