Looks like unity/compiz adds their own decorations also for CSD windows... Metacity does not do that and is should not do that - CSD windows are supposed to have their own shadows, borders and resize cursor area. Just because unity does that does not mean that there is bug in Metacity.
As you already know - Adwaita theme does work. So it is theme problem... But Ambiance theme can not be fixed... Ok, it can, but it will create problems for Unity session. And I am quite sure that Adwaita theme is not only theme that works. Any theme that have popper support for CSD windows will work. --- Are metacity only downgraded application? Is 'metacity --replace' problem reproducable in clean install? Dmitry, could this be regression after multiarchify library? Could it be build differently that triggers this bug? I see also this warning: Window manager warning: Log level 8: g_main_loop_is_running: assertion 'loop != NULL' failed --- Screenshot does not help me. I need reproducible steps with how to trigger this bug. In other bug you wrote that you can reproduce in virtualbox. I asked for steps that could lead to bug... Also if metacity crashes for you - then please try to get stacktrace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1557904 Title: 3 bugs from metacity 3.18.2 (for Ubuntu 16.04 xenial) Status in metacity package in Ubuntu: New Bug description: 1. Bug: Many Gtk3 Softwares don't show their border of window, based on Ubuntu Light-theme. (See attachment Bug1) sudo apt-get install gnome-session-flashback gnome-system-monitor gedit light-theme [Logout and login to Gnome Flashback Session (Metacity)] Open nautilus window browser, Open gnome-system-monitor, then open "Preference" item from menu. Open gedit, then open "Preference" item from menu. .. Non of these window have border, which is extremely unfit under metacity compositing mode (metacity -c --replace). Note: If I install an old version - metacity 3.14 (from Ubuntu 15.04 repository), it does have this problem. So it's metacity 3.18 that cause those border miss. 2. Bug: metacity are supposed to quit if a new window-manager replace it. Run: metacity -c --replace Then run: metacity -c --replace The previous metacity process doesn't quit, which both metacity 3.14 (from ubuntu vivid) and marco (from ubuntu xenial) doesn't happen. 3. Bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1538111 This bug still not fixed. There is a small possiblity that closing a certain window will make all of other windows disappear, nothing would do anymore expect killing metacity and run metacity again. Then disappearred windows display again! I only found out that if I frequently plugin and plugout external screen monitor, the possiblity of getting stuck into this bug becomes larger, and "close a window" operation is key that might cause this bug. (See attachment Bug3) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: metacity 1:3.18.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Mar 16 14:26:10 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1557904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
