mate-display-properties hangs on startup ever since my DisplayPort port suffered a hardware failure

[geekosaur]

Expected behaviour

Ideally it would start up and (if necessary) I could clean up whatever garbage might need to be cleaned.

Actual behaviour

Hangs on startup, and my wm (xmonad) tells me it is repeatedly creating windows that I'm not seeing on screen. monitors.xml is not re-created.

Steps to reproduce the behaviour

Not sure this is helpful; it's only happened since the DisplayPort on an older laptop suffered a hardware failure.

MATE general version

1.26.2-1.1build3 (Ubuntu 24.04 mate-desktop package version)

Package version

1.26.1-1.1build3 (Ubuntu build)

Linux Distribution

Ubuntu 24.04 LTS

Link to bugreport of your Distribution (requirement)

https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/2083128

[geekosaur]

It looks like it does occasionally start up, but it's extremely slow. I'm going to instrument the handleEventHook when I get a chance, to see what's going nuts… but the next few days will be filled with doctor appointments so it's not likely to happen until the weekend.

[geekosaur]

Also, I should mention that I use xmonad as window manager for MATE. In general it works well, and mate-display-properties used to work fine with it.

[geekosaur]

KeyPress keycode 33 sym 112  ( 0x70  " p ") mask 0x40 (mod4) clean 0x40 (mod4)
MapNotify (deleted window 010001a9)
MapNotify (deleted window 010001b3)
Unmap (deleted window 010001b3)
DestroyWindow (deleted window 010001b3)
MapNotify (deleted window 010002b4)
Unmap (deleted window 010002b4)
DestroyWindow (deleted window 010002b4)
MapNotify (deleted window 01000322)
Unmap (deleted window 01000322)
DestroyWindow (deleted window 01000322)
MapNotify (deleted window 010003ef)
Unmap (deleted window 010003ef)
DestroyWindow (deleted window 010003ef)
Unmap (deleted window 010001a9)
DestroyWindow (deleted window 010001a9)
Property on 05200006 "‹C› hilfy  «crawl:master» [~////source ~///work]" 1276x1403+2@1280,0 mate-terminal/Mate-terminal (318417)@hilfy (normal)
  atom _NET_WM_STATE (ATOM) = []
Property on 05400006 "[10/01-22:59] hilfy  cabal:more-changelog-d-tweaks$ [~//cabal ~//xmonad ~//ghc]: " 1276x1403+2@0,0 mate-terminal/Mate-terminal (318414)
@hilfy (normal)
  atom _NET_WM_STATE (ATOM) = []
Property on 05600003 "~/Dropbox/Congregation/work/1/2-earth.txt (1) - Sublime Text (UNREGISTERED)" 2252x1451+2@2560,0 sublime_text/Sublime_text (318430)@hilf
y (normal)
  atom _NET_WM_STATE (ATOM) = []
Property on 05e00008 "Inbox - allbery.b@gmail.com - Gmail - Google Chrome" 2876x1596+2@4816,20 google-chrome/Google-chrome (318796)@hilfy (normal)
  atom _NET_WM_STATE (ATOM) = []

and then it loops reporting _NET_WM_STATE changes on all the mapped top level windows over and over again. (The KeyPress event was me launching mate-display-properties.) What is mate-display-properties doing that is causing these windows to update their EWMH state property? And why is it creating and immediately destroying windows?