Created attachment 1511696 [details] Panel menu is not right above the panel Description of problem: I have a 1600x1200 monitor that I have rotated to the right, so in the Settings > Display I have it configured with Rotation Left. So I have 1200 (w) x 1600 (h) display and xdpyinfo thinks so as well: $ xdpyinfo | grep dimensions dimensions: 1200x1600 pixels (318x423 millimeters) After upgrade from Fedora 28 to 29 via https://fedoraproject.org/wiki/DNF_system_upgrade, it looks as some operations like maximizing windows or displaying menu for panel think that the height of the display is only 1200, not 1600. However, the panel itself is placed correctly to the bottom of the screen, and I can also manually place windows there. However, even if I manually drag the bottom corner of window to cover the whole display with the window, clicking the "maximize" button will shrink the height again. Version-Release number of selected component (if applicable): xfce4-panel-4.13.3-20.fc29.x86_64 How reproducible: Deterministic, at least on this one machine. I don't have another machine to try. Steps to Reproduce: 1. Have working XFCE environment on Fedora 28 with rotated monitor, 1200x1600 display. 2. Upgrade to Fedora 29 dnf system-upgrade 3. Click the "menu" button in panel. Actual results: The menu is displayed way high. Expected results: The menu is displayed right above the panel. Additional info: I've chosen the xfce4-panel component simply because the problem is most easily demonstrated with panel. But it's rather likely that the ultimate component which is the root of the problem is somewhere else.
I should add that workspace margins are set to 0 (I did not touch them) and the behaviour is as if the window manager thought that the bottom margin is set to 400. Or something similar.
Thinking about it some more, xfwm4 feels like better component.
After today's upgrade from xfwm4-4.13.1-6.fc30.x86_64 to xfwm4-4.13.1-8.fc30.x86_64, the issue seems fixed. Looking at the diff, it seems like https://src.fedoraproject.org/rpms/xfwm4/c/67b2c274d1765836e6080dc44e91991e3c23b7a8?branch=master introduced the fix for bug 1666735 and it also fixed this issue.