Diagnostic fails at Access URL https://127.0.0.1/_matrix/client/versions on tcp4
Update log in web interface shows
Preparing to unpack …/matrix-synapse_1.74.0-1~bpo11+1_amd64.deb …
Unpacking matrix-synapse (1.74.0-1~bpo11+1) over (1.73.0-1~bpo11+1) …
Setting up matrix-synapse (1.74.0-1~bpo11+1) …
Job for matrix-synapse.service failed because the control process exited with error code.
See “systemctl status matrix-synapse.service” and “journalctl -xe” for details.
Running journalctl -xe shows nothing dated this year.
Usually when this happens, I’m hundred of miles away from home driving and someone has posted a fix before I could even try troubleshoot or look to revert myself.
This is the first time its happened where I was actually in a place to try do something about it. But I’m in the middle of a big project and its going to be a slammed work day so I can only check the phone and hope someone posts something I can try run during a 5min brain break.
Looks like the latest version of matrix-synapse made available in bullseye-backports today ( 1.74.0-1~bpo11+1) seems to depend on python3-icu >=2.10.2. However, only an older version is available. This is a bug in matrix-synapse packaging. The solution is for the matrix-synapse maintainer to upload a later version to bullseye-backports and bump the version requirement.
Could someone please report a bug against the matrix-synapse package?
Follow up - Removal of python3-icu may break push notifications or perhaps presence or read-receipt?
Posted notice on my server but no one appears to have noticed so following up with them via out-of-band channels to see what might be nonfunctional, if anything. Could just be they are all at lunch and not paying attention.
Yes, it happened to me to after the upgrade to Element 1.11.24. It seems that it’s an old problem reappearing. After trying multiple things (incl. deleting settings and reinstalling) the only thing that helped was downgrading to version 1.11.23. So I guess I’ll stick with the Appimage until the problem is resolved.