Bug 2230202
| Summary: | Icons on desktop not clickable when display resolution is not same on mirrored monitors(displays) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Murali Prudhvi Ijjapureddi <mijjapur> |
| Component: | gnome-shell-extensions | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED MIGRATED | QA Contact: | Porygon <jsolomon> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.7 | CC: | aubin.guillemette, desktop-qa-list, jadahl, jsolomon, sbarcomb, tpopela |
| Target Milestone: | rc | Keywords: | 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-15 19:06:17 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: | |||
|
Description
Murali Prudhvi Ijjapureddi
2023-08-08 22:09:36 UTC
Can you provide a little more detail on what exact steps the customer is taking to change the resolution as well as mirror and extend the screens? As well, if they're running Wayland or Xorg for this? Wouldn't hurt to know which specific nvidia chip this is either. :) Gnome Settings GUI disables the button that lets you mirror monitors if you have more than 2 monitors, so I assume the customer is using a tool like xrandr or some kind of monitor config. I did check this on gnome-shell-3.32.2-48.el8.x86_64 with a fresh RHEL 8.7 image by extending and mirroring the monitors using xrandr, but I couldn't seem to reproduce the issue. Having a clearer idea of what the user is doing specifically would be very helpful! Setting needinfo for the above and I would also asked you to attach the customer case to the bug. Hello, I am the customer who opened the case with RH. The case number is 03538549. We are running Xorg and configuring the displays in xorg.conf. We have a /etc/xdg/monitors.xml in place to make sure what is set in xorg.conf cannot be changed dynamically. The GPUs are NVIDIA A2000. Lots more details in the case. I'm here if more info is needed. Thanks. (In reply to aubin.guillemette from comment #3) > Hello, > > I am the customer who opened the case with RH. The case number is 03538549. > > We are running Xorg and configuring the displays in xorg.conf. We have a > /etc/xdg/monitors.xml in place to make sure what is set in xorg.conf cannot > be changed dynamically. > > The GPUs are NVIDIA A2000. > > Lots more details in the case. I'm here if more info is needed. > > Thanks. Thanks for your response! Unfortunately, not quite sure where you mean that you've opened this "case" at or where this case number applies. If you've got a page link or just some logs you could post, that would be great. Could I see the contents of your xorg.conf and monitors.xml file as well, please? Thank you! It refers to the red Hat support case I opened a while back: https://access.redhat.com/support/cases/#/case/03538549 xorg.conf: Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 Option "Xinerama" "0" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "DELL U2412M" HorizSync 30.0 - 83.0 VertRefresh 50.0 - 61.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "nvidiaXineramaInfoOrder" "DFP-7" Option "metamodes" "DFP-3: 1920x1200 +0+0, DFP-1: 1920x1080 +0+0, DFP-7: 1920x1200 +0+1200, " Option "ConnectToAcpid" "off" SubSection "Display" Depth 24 EndSubSection EndSection ------------------------------------ monitors.xml: <monitors version="2"> <policy> <stores></stores> <dbus>no</dbus> </policy> </monitors> 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. 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. |