org.mate.Marco.general disable-workarounds 'true' makes panel invisible on next panel launch

[truboxl]

Taken from dconf Editor: "Description: Some applications disregard specifications in ways that result in window manager misfeatures. This option puts Marco in a rigorously correct mode, which gives a more consistent user interface, provided one does not need to run any misbehaving applications."

I thought Panel works well with Marco but looks like its not.

I am using Fedora 23 MATE-Compiz Spin (with Compiz removed, so that's out of the problem). If one set org.mate.Marco.general disable-workarounds to 'true' with dconf Editor, the panel is still there, however, at next reboot/login/launch, it completely disappears (top & bottom panels).

Though pressing Alt + F1 still able to trigger the menu down from an invisible panel...

EDIT: TLDR: Setting to TRUE caused problem...

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28979374-org-mate-marco-general-disable-workarounds-true-makes-panel-invisible-on-next-panel-launch?utm_campaign=plugin&utm_content=tracker%2F314880&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F314880&utm_medium=issues&utm_source=github).

[raveit65]

confirmed!

[raveit65]

You're not the only one https://bugzilla.redhat.com/show_bug.cgi?id=1288309 I can reproduce it now. Thanks for finding it.

[truboxl]

Glad to help. LOL

[raveit65]

More tests gives me different results with gt2 and gtk3 builds. With gtk2 build 1.10.1 release does not have the issue. With gtk3 build it fails with 1.10.0 too. So finding the culprit commit for gtk2 somwhere in 1.11 development will not help for gtk3 build. From the description of the key:

Some applications disregard specifications in ways that result in window manager 
misfeatures. This option puts Marco in a rigorously correct mode, which gives a more 
consistent user interface, provided one does not need to run any misbehaving applications.

That means for us that m-p gtk3 have more issues as we thought. @monsta Maybe we should disable this option.

[monsta]

Well, this key is well hidden, there's no UI for setting it. It can be left as is for debugging purposes.

[raveit65]

Did you ever use this option to debug something :smile: ? Here a comment from a user about the missleading description ;)

Given the instructions for disable-workarounds, this is probably worth fixing.
The instructions practically recommend setting it to true. And if someone did that
in an old version, they would be where I was. (I vaguely remember that even had a reason
for setting this, but it was years ago, and I forgot what that was. Seems to work now with
this set to false.)

Note, old version is 1.10.1 Well, maybe you need more linuxmint reports about. Anyway, i will ask you abaut to disable it in irc chanel. I'm not willing to ship 'better than auto-hide' in fedora.

[frankzen]

This bug caused me no end of problems today. A few days around I had set the Marco setting to "true"...then forgot about it. When I logged back into Mate (Debian Stretch) the panels were gone, and it wasn't until I find this bug through Google that I clued into what had happened. I did get the panel back briefly after I installed Mate-core ( I don't know why that package wasn't installed when I installed the mate-desktop). The side effects included panels that couldn't be moved to the bottom. The top panel wasn't visible until I made is more than 150 pixels wide. It could be dragged to the left or right but not the bottom. Mate-panel --reset did nothing. I was about to dump Mate for Cinnamon. Until I fixed I would vote for the key to be removed.