Bug 827753

Summary: Menus aligned to the left on second monitor
Product: [Fedora] Fedora Reporter: Ian Pilcher <ipilcher>
Component: libreofficeAssignee: David Tardon <dtardon>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: caolanm, dtardon, erack, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 06:03:18 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Ian Pilcher 2012-06-02 16:30:15 EDT
This is already filed upstream as FDO #49650.  Opening this, since the upstream bug doesn't seem to be getting any attention, despite being bisected.

Here is the description from the upstream bug:

Problem description: On CentOS 6.2 (KDE 4.3.4), LibreOffice windows on the
second monitor open all menus (incl. context menus) to the *LEFT* instead of to
the *RIGHT*. This results in sub-menus opening *over* parent the menu instead
of to the right (see attached screenshot).
This has been reported so far for Ubuntu as well

Steps to reproduce:
1. Open LibreOffice on the second monitor
2. Click for any menu (e.g., File)
3. The menu is aligned to the left instead of to the right

Current behavior:
Menus aligned to the left on second monitor

Expected behavior:
Menus aligned to the right on the second monitor as they do on the primary
monitor (and all other applications, including OpenOffice 3.2 on the same
machine & OS).

Platform (if different from the browser): 
CentOS 6.2 KDE 4.3.4              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120425
Comment 1 Ian Pilcher 2012-06-02 16:44:10 EDT
BTW, the problem appears to have been introduced by this giant commit:

Comment 2 David Tardon 2012-06-20 06:03:18 EDT
the fix will be in 3.5.5 upstream release, so we will wait for it