Disabling ALL animations on MATE 22.04

Support & Help Requests
1

I've tried various gsetting values under gnome, mate, marco, gtk using dconf editor or the gsettings command directly, and none disable them even temporarily, let alone permanently!!!

Pray tell how?

Thank you

Window Manager: Marco (picom: GLX)

Linux OasisMega1 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Release 22.04.4 LTS (Jammy Jellyfish) 64-bit
Kernel Linux 5.15.0-116-generic x86_64
MATE 1.26.0
Memory: 3.6 GiB
Processor: AMD Phenom(tm) II X4 810 Processor × 4
Graphics: AMD RS780 (DRM 2.50.0 / 5.15.0-116-generic, LLVM 15.0.7)

2

It's unclear to me what animations you are referring to. When I think of animations on the MATE desktop I think of the checkbox in MATE Tweaks.

Screenshot at 2024-07-22 14-09-29
Screenshot at 2024-07-22 14-09-29704×601 48.6 KB

The top check box. Is this what you're looking for?

2 Likes
3

That was the first thing I tried.

I did not see any guidance on the MATE site that dealt with a "stubborn" computer scenario.

Places where I looked for guidance (among others) were:

The other references all seemed to duplicate the above.

So ... I went looking using dconf-editor, under org for each of

  • ArcticaProject
  • gnome
  • gtk
  • mate
  • onboard
    and toggled ALL properties anywhere to ON, then OFF, to ensure I told the system what I wanted, and that it would register somewhere. Unfortunately, all that was to no effect! ::

Please HELP!

4

i dont think u can disable all animations. Even if u do u can cause errors to your Ubuntu Mate Session. If u manage to disable all animations. Like i said. could cause errors or even damage Ubuntu Mate. But if u still want to try then good luck.

1 Like
5

In earlier versions of UbuntuMATE, including 20.04, I was fully able to disable animations, everywhere, for everything.

Now, I am being told that, because of some developer who feels that animations should be mandatory, that I can no longer disable any of that ?

WHY take out functionality that reflects a "smaller code footprint", and leave only functionality for a larger, non-beneficial, code footprint ??? Because they want to do things to impress ?

Any animations should be limited to where animations are relevant, like for plank, where it is specifically relevant, or the sound volume bars on an equalizer visualization.

IMHO, it has no place for basic functionality like display a new window. Just show that thing, or just close it. I don't want, nor appreciate, fade-in or swipe to the left to disappear, like you sometimes have on an android tablet.

To make such animations mandatory, is to imply that keyboards are more than passé, they are fossils ! That perspective is so off-base as to be laughable, if it weren't for the fact that it is impacting those of us who know better.

Let those who want their animations on touch screens, tablets and phones have their way, but PLEASE, bring back the option for proper disabling of ALL animations !

If people knew how much animations chewed up their battery charge, they might not be so keen on having those animations.

Thank you.

6

Hi, @ericmarceau !

Why are you using standalone compositor in the first place? It is designed to provide window effects and has its own configuration files. Even more, you are using heavy GLX backend for it.

Use Marco built-in compositor or no compositing at all.
MATE Tweak -> Windows -> Window Manager

2 Likes
7

I am using the GLX because I have CAD/CAM applications working with OpenGL (FreeCAD).

The choice seems self-evident, or am I missing a point that is not documented regarding when to use, or not, the GLX ?

8

OpenGL is just the API, picom is using GLX backend for window compositing purposes. It has nothing to do with your other applications.
Your initial complaint was about window animations in MATE. Picom is not a part of MATE desktop, it is a standalone compositor. You can study documentation and configure it.
https://wiki.archlinux.org/title/Picom

Based on your initial request, I suggest switching to the built-in compositor or disabling compositing altogether.

3 Likes
9

It seems that I did not fully understand the fact of the actual separation of Application-related GL activities and the Window-Manager's compositor "level".

I have disabled all compositing by choosing the "no compositor" option. That appears to be providing me what I was looking for.

Thank you very much for that hint. I can work with the results.

As for compositors and future capabilities, I came across this link, from another post, which introduces Wayfire.

I am far from being that skilled as a programmer, but I have enough experience to recognize the creativity, dedication, effort, long-hours, frustrations, challenges, and elation of satisfaction at creating what can only be characterized as a beautiful work of artistry!

I know that some developers have accepted the labeling of such work as "eye-candy", but I am sure that many have, justifiably, struggled with the challenge of presenting the flood of input from our complex world within a manageable appliance. I will add my voice to those who say that the achievement is breathtaking, surpassing by far the compiz of a decade ago!

And while I can recognize, and appreciate, that technical/process achievement, I am still driven to raise the specter of what impact so much dynamic visual input can have on the human brain, and whether that

  • pushes the brain to greater adaptation and achievement, or
  • if, from a long-term exposure, strain and degrade the brain's ability for cognition and sense-making.

Unless that impact is specifically researched, we will only discover what will transpire as the years, and symptoms, emerge, as they always seem to, too late to reverse any negative impact that may arise.

10

You are welcome, @ericmarceau !

2 Likes