Bug 1884418 - x2go MATE Compiz thick black window borders
Summary: x2go MATE Compiz thick black window borders
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: x2goserver
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-01 22:21 UTC by Robert Buffington
Modified: 2021-04-30 02:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-10-03 15:45:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
x2go MATE Compiz desktop showing thick black borders (604.17 KB, image/jpeg)
2020-10-01 22:21 UTC, Robert Buffington
no flags Details

Description Robert Buffington 2020-10-01 22:21:29 UTC
Created attachment 1718329 [details]
x2go MATE Compiz desktop showing thick black borders

Description of problem:
When using x2goclient to a Fedora MATE-Compiz desktop running x2goserver, all windows have a thick black border rather than a drop shadow.

Version-Release number of selected component (if applicable):
x2goserver-4.1.0.3-6.fc32.x86_64
First observed with x2goserver-4.1.0.3-3.fc30.x86_64  

How reproducible:
Happens every time.

Steps to Reproduce:
1. Install Fedora MATE-Compiz Spin
2. Install and enable x2goserver
3. Connect to x2goserver using a current x2go client.

Actual results:
see attachment (screen shot)

Expected results:
Windows with a thin gray border and a drop shadow as shown on the Fedora MATE-Compiz download page.

Additional info:
This may be related to another component. When first observed, I downgraded x2goserver to x2goserver-4.1.0.3-2.fc30.x86_64 and the problem still persisted. To resolve the issue, I needed to reinstall Fedora 30 without running any updates. The x2g0 client is using default settings with the WAN connection type.
System: Dell Precision T3500
Graphics card: Nvidia Quadro FX 580
Kernel driver: nouveau

Comment 1 Orion Poplawski 2020-10-02 01:59:05 UTC
Does this suggestion help:

If you have MATE Tweak installed, launch it, select Windows, and change the Window Manager (last option at the bottom) to "Marco (no compositor)".

From https://lists.x2go.org/pipermail/x2go-user/2020-August/006244.html

Comment 2 Robert Buffington 2020-10-03 01:55:28 UTC
Orion, thank you for leading me down the path to success.

I couldn't find a MATE-tweak anywhere for Fedora. In the meantime, I installed Fedora 33 Beta to see if this problem was fixed in that release. The problem still exists, which is why I updated the Version for this bug. However, I was able to find the Marco man pages and the steps on how to disable the Compositing Manager from the MATE menu.

One way I can remove the thick black borders is by going to the System/Preferences/Look and Feel/Windows and then unchecking "Enable software compositing window manager". However, I am unsure if this sets it systemwide for all users.

On a hunch, I thought I'd check dconf:
$ gsettings list-recursively | grep -i composit
org.mate.Marco.general compositing-fast-alt-tab false
org.mate.Marco.general compositing-manager true

From this, I was able to write this little snippit below. This immediately got rid of the black borders for me in my x2go session. This should also affect all users on the system.

#!/bin/sh
if [ ! -f "/etc/dconf/db/local.d/01-marco" ]
then
cat << EOF > /etc/dconf/db/local.d/01-marco
# Disable compositing-manager for x2go
[org/mate/marco/general]
compositing-manager=false
EOF
fi 
dconf update

This would take away nice effects that would normally work on a directly-attached display, but in my case, I run a headless system solely for x2go, so it would work nicely for me. Can we can really call this one "fixed" in this case?

Comment 3 Orion Poplawski 2020-10-03 15:45:07 UTC
Thank you for posting your workaround.  I'm going to close this here.  Any further discussion should take place on the X2Go list.  I'm not sure that there is really anything X2Go should do.  While it could ship a configuration like this, I'm not sure that it's appropriate to assume that just by installing x2goserver you want to always disable compositing for mate/marco.  But maybe upstream will have some more ideas.


Note You need to log in before you can comment on or make changes to this bug.