RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1108322 - Qt menu placement problem with gnome-shell and vertical monitors
Summary: Qt menu placement problem with gnome-shell and vertical monitors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mutter
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-11 17:22 UTC by Matthias Clasen
Modified: 2015-03-05 13:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:21:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0535 0 normal SHIPPED_LIVE Low: GNOME Shell security, bug fix, and enhancement update 2015-03-05 16:32:34 UTC

Description Matthias Clasen 2014-06-11 17:22:10 UTC
We took a late fix for handling of vertically stacked monitors with gnome-shell into 7.0. This change is causing menus of qt applications to be mispositioned.

See https://bugzilla.gnome.org/show_bug.cgi?id=730527

Comment 1 Matthias Clasen 2014-06-11 17:31:02 UTC
Florian is work on a fix. Fixing this entirely may require changes to both gnome-shell and nautilus.

Comment 2 Florian Müllner 2014-06-11 20:35:08 UTC
(In reply to Matthias Clasen from comment #1)
> Florian is working on a fix. Fixing this entirely may require changes to both
> gnome-shell and nautilus.

I'm still testing (and need to write a proper commit message), but I'm cautiously optimistic that a single (and simple) mutter patch fixes all issues sufficiently well.
(apparently we were wrong about nautilus using the primary monitor, so there is no issue with system chrome overlaying desktop icons - I don't think the current behavior is right and will address it upstream, but I don't think it is an urgent problem we need to address in RHEL)

Comment 3 Florian Müllner 2014-10-09 11:26:51 UTC
The more important patches apply to mutter, so reassigning; I'll use bug 1075240 for the gnome-shell bits.

Comment 8 errata-xmlrpc 2015-03-05 13:21:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0535.html


Note You need to log in before you can comment on or make changes to this bug.