Hi I'm using Maya and it sports tear-off menus in the interface. Unfortunately if I tear off menus they loose their window borders, and get stuck up in the upper left of the screen. This behavior doesn't occur in GNOME (metacity), and strange enough, if I disable the CIOverlay option in my xorg.conf the menus tear off correctly, though Maya doesn't work correctly, so it's not much of a work-around. My current work around is to quit maya and restart. I was going to take a screen shot, but it turns out the menu doesn't appear in the screen shots, I'm guessing because it's some kind of overlay visual. thanks.
My rough guess is that the frame window creation fails and so does the reparent, leaving a dangling undecorated client window. The parent frame is created with the same depth and visual as the client window, but as a child of the root window. That should not fail, but unfortunately, I have neither the hardware nor the software to reproduce this.
Although... Would you be willing to test a patch if I send you one?
(In reply to comment #2) > Although... Would you be willing to test a patch if I send you one? Sure, If you wouldn't mind helping me apply it. I'm guessing that I need to down load the source - I'm using CentOS 5. Should I grab the source RPM for xfwm4 or should I try this against the source on xfce.org? Thanks for looking at this.
I guess I can even build an rpm package if you want to test. http://www.foo-projects.org/~olivier/preview/xfwm4-4.4.3-1.i386.rpm This test package is built on RHEL5, it should install on Centos too. Please note that it says version 4.4.3, but that's not the final release, it's just a snapshot of current svn branch for xfce 4.4.
Of course, I failed to mention, that I'm running x86_64. Mind rebuilding for that architecture?
Sure, it's here (previous build removed): i386: http://www.foo-projects.org/~olivier/preview/xfwm4-4.4.3svn.r28121-1.i386.rpm x86_64: http://www.foo-projects.org/~olivier/preview/xfwm4-4.4.3svn.r28121-1.x86_64.rpm
Oliver this works beautifully! Thanks so much for making XFCE such a pleasure to use. I'm assuming I can use this release 'in production', I'm going to use it on my own machine before unleashing to the rest of the facility. Is this the sort of fix that would be back-ported to RHEL, or would I be fairly safe using this RPM?
(In reply to comment #7) > Oliver this works beautifully! Thanks so much for making XFCE such a pleasure > to use. Great to know that it fixes the issue! > I'm assuming I can use this release 'in production', I'm going to use it on my > own machine before unleashing to the rest of the facility. There is no guarantee of any kind, so the decision to use this package in a production environment is your decision. What I can say is that this package is built from the current status of the stable branch of xfwm4, so it should be as stable as I am aware of (it also contains other fixes, the NEWS file list the changes since xfwm4 4.4.2) > Is this the sort of fix that would be back-ported to RHEL, or would I be > fairly safe using this RPM? The fix by itself is simple, and could be backported to 4.4.2, but I am not going to do this myself as this is a decision that belongs to the packager of the Xfce for the distribution you use. Xfce 4.4.3 is not released yet, so other fixes may be included later, before 4.4.3 eventually comes out. I cannot really tell you if you should or should not deploy this package, but this fixes the issue you reported, among other annoying issues.