Bug 74123

Summary: [NVE7] windows maximize behind xfce4-panel until settings viewed
Product: xorg Reporter: Jamin Collins <jcollins>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
window maximizing behind panel
none
window maximizing behind panel
none
correct behavior with intel driver none

Description Jamin Collins 2014-01-27 18:48:29 UTC
Created attachment 92873 [details]
window maximizing behind panel

Running a 3.13 kernel, built from upstream git repository (commit d8ec26d7f8287f5788a494f56e8814210f0e64be) and the associated nouveau driver from the kernel source tree.

When any window is maximized before first viewing the xfce4-panel settings, it maximized behind the xfce4-panel(s).  Once the panel settings have been viewed, the windows no longer maximize behind the panel.  The settings for each panel have to be viewed, but only once per session.

Normally, I would consider this an issue with xfce4 (either the panel or window manager).  However, changing the video driver (from nouveau to intel) prevents the problem.
Comment 1 Jamin Collins 2014-01-27 18:50:25 UTC
Created attachment 92874 [details]
window maximizing behind panel

Attaching with correct file type.
Comment 2 Jamin Collins 2014-01-27 18:51:58 UTC
Created attachment 92875 [details]
correct behavior with intel driver

By switching the display graphics from discrete to integrated and thus the video driver from nouveau to intel, the problem goes away.
Comment 3 Ilia Mirkin 2014-01-27 18:55:37 UTC
This sounds like some sort of minor bug in the nouveau DDX wrt how it's reporting screen heights wrt WM fixups/etc. Unfortunately I don't know enough about those details to tell what's going on... perhaps you could get an xfce dev to clue us into what we're doing wrong?

Although it's telling that _after_ you run the settings, it all starts working. So perhaps we're missing some bit of initialization? Would be nice to know exactly what these things are doing.
Comment 4 Jamin Collins 2014-02-25 17:56:21 UTC
To further complicate things, this doesn't appear to be a problem with the driver version shipping with the 3.13 Linux kernel tree.
Comment 5 Jamin Collins 2014-02-27 17:20:46 UTC
I'm not able to replicate this behavior when using the 3.13 kernel releases from kernel.org and their associated nouveau driver.  I can reliably reproduce this when using the 3.11 kernel from Ubuntu's 13.10 release and their associated nouveau driver.  Going to close this as resolved/fixed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.