Bug 2012447

Summary: [RHEL9] [Hyper-V]There is no confirm dialog display when change orientation on non-wayland display server
Product: Red Hat Enterprise Linux 9 Reporter: xxiong
Component: xorg-x11-serverAssignee: José Expósito <jexposit>
Status: CLOSED MIGRATED QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 9.0CC: cavery, cgarnach, huzhao, jadahl, ndegraef, tpopela, vkuznets, vtosodec, xuli, yacao, yuxisun
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-11 17:43:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot1 none

Description xxiong 2021-10-09 10:26:28 UTC
Created attachment 1831144 [details]
screenshot1

Description of problem:
Login with non-wayland display server(like GNOME Classic), Change the orientation, click Apply, there will no confirmation dialog display


Version-Release number of selected component (if applicable):

Host: 
Hyper-V 2022

Guest: 
RHEL-9.0.0-20211006.6
xorg-x11-server-Xorg-1.20.11-4.el9_b.x86_64 


How reproducible:
100%


Steps to Reproduce:
1. Create an new VM with  GEN1 or GEN2
2. Open the VM Console GUI
3. Login with non-wayland display server
4. Display Settings->Change orientation, click Apply button
5. Check the result

Actual results:
1. The GUI desktop display as the changed orientation without confirmation dialog on step 5, and will display  back after timeout (20s)--this will cause cannot change orientation
2.  This issue occurs as below:
Standard (Wayland display server)--not occur
GNOME Classic-occurs
Custom-occurs
Standard(X11 display server)--occurs
User script--occurs

Expected results:
1. The confirm dialog should display well

Additional information:

The screenshot attached

Comment 4 Niels De Graef 2022-12-23 11:22:48 UTC
Changing this to gnome-control-center but tbh, I suspect g-c-c might be using XRandr here so that might be expected behavior. I'll let the g-c-c maintainers decide what to do with the bug though

Comment 6 Jonas Ådahl 2023-03-10 11:44:53 UTC
(In reply to Niels De Graef from comment #4)
> Changing this to gnome-control-center but tbh, I suspect g-c-c might be
> using XRandr here so that might be expected behavior. I'll let the g-c-c
> maintainers decide what to do with the bug though

gnome-control-center doesn't use RANDR, it always uses the mutter D-Bus API. I can reproduce something similar to this with RHEL-9.2.0 (but not RHEL-9.0.0). What appears here is that clicking "Apply" makes gnome-shell apply the RANDR configuration (e.g. flipped), and continues to render like normal (confirmed with gdb breaking in cogl_onscreen_swap_region, as well as taking a screenshot which shows the confirmation dialog), but the content shown on screen doesn't update. It looks like it was applied, but if you e.g. run 'glxgears' somewhere on screen, it'll freeze, and if you press 'Esc' it will effectively activate the Restore button and things will go back to the configuration before pressing Apply.

Thus, this is likely a bug in the X server, the kernel or spice-vdagent.

Comment 7 Jonas Ådahl 2023-03-10 12:48:22 UTC
Moving to spice-vdagent for further investigation.

Comment 12 RHEL Program Management 2023-09-11 17:33:17 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 13 RHEL Program Management 2023-09-11 17:43:29 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.