|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast Computer Role textmode screen not properly displayed for ppc64/ppc64le | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Michel Normand <normand> |
| Component: | YaST2 | Assignee: | YaST Team <yast-internal> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | gsouza |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Linux | ||
| URL: | http://openqa.opensuse.org/tests/385514/modules/logpackages/steps/2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Computer Role textmode screen not properly displayed | ||
|
Description
Michel Normand
2017-04-12 15:00:20 UTC
Sorry for the delay; we had a lot of issues in our incoming queue lately.
Is this a ppc-only problem? I guess if we had this problem in general, we would have seen a lot of similar bugs, but we didn't.
In this build
https://openqa.opensuse.org/tests/365272
the problem seems to be the test setup: iSCSI devices expected, but not available AFAICs; but that is a problem that is unrelated to this. It never even gets to the workflow step where this "role screen broken" problem occurs.
Here
https://openqa.opensuse.org/tests/385514#step/logpackages/2
I can see the problem, but it's a very weird one: One blank is missing at the start of the upper frame of that subwindow. I wouldn't even know how to get this programmatically; it must be broken on a deeper level, such as libncurses (unlikely IMHO) or the terminal emulation used here. Or some other program is spitting output to this terminal, thus disturbing the ncurses output.
In this "always latest" test case
https://openqa.opensuse.org/tests/latest?flavor=DVD&version=Tumbleweed&machine=ppc64&distri=opensuse&test=textmode&arch=ppc64
the problem is still there, but it's much too regular and predictable to be another program doing uncoordinated output on the same terminal; it's always that first blank just before the top left corner of that frame.
My personal guess is that it's a problem of the terminal emulation or (like in similar issues on aarch64) a problem in the virtualization drivers.
I asked our QA people here, and they have not seen this problem on other architectures. Frankly, I don't know how to continue here; I am pretty sure this is not a YaST problem, but we'll queue it for further investigation in our scrum backlog anyway. For the time being, I suggest to adapt the needle to exclude that frame line so tests can continue. Now tracking in Trello to integrate this task in our scrum team workflow: https://trello.com/c/f9kgnZ5j It's the same issue of bug #1025622. The problem persists during the entire installation problem. *** This bug has been marked as a duplicate of bug 1025622 *** |