This is a discussion topic for the following Common Issue:
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
Please see the Common Issue for solution/workarounds:
Thanks for the writeup. Is this preinstalled on some desktop, or high-profile for some other reason? We’re trying to keep Ask Fedora > Common Issues limited to just high-profile issues only, that affect a large user base. Otherwise it would become just another Bugzilla, too long to read through. Thanks for info.
Probably not high-profile, but “your matrix homeserver does not come back up after upgrading to Fedora 44” is probably bad enough for people who are affected 
Yes, if I had knew about the problem, I wouldn’t have upgraded my server, especially since I use it to discuss with Fedora folks and others.
OK. As a suggested workaround, advising people to start a Fedora 43 container to run the server should be the easiest way forward, what do you think?
I hit this here also. ;(
I just used the f43 version of the package (it still works fine with f44).
I really hope the maintainer can finish sorting out the building issues and get it back up to date.
I managed to build the 1.145.0 package from koji that had been previously tried and failed locally once I had built the two python dependencies it needs which have been retired. The new version from koji had some additional dependency issues that I didn’t manage to resolve.
That’s what I’m running for now but I did add a comment the bugzilla ticket summarising the issues.
Folks, if you want to see this published, please provide at least some general steps in the Workarounds section, thanks. Anyone can edit it. Suggesting either a container or installing the F43 RPM sounds reasonable (provide a download link - is it enough to just use the synapse...f43 rpm, or some deps are needed as well?).
I guess a container could be a solution, but that’s non trivial. @kevin solution might requires some rpm hack (even if I guess “download the old rpm and run dnf install” should be ok). @tomh solution is not trivial for non packagers.
I would maybe write something along “do not upgrade to F44 if you depend on Synapse” and I guess whatever @kevin did if people are already on F44 ?
Yeah, nothing is great here. ;(
I just did a ‘dnf –releasever 43 install synapse-matrix synapse-matrix+postgres’ after the f44 update. (Then later a dnf update https://kojipkgs.fedoraproject.org//packages/matrix-synapse/1.151.0/1.fc43/x86_64/matrix-synapse-1.151.0-1.fc43.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/matrix-synapse/1.151.0/1.fc43/x86_64/matrix-synapse+postgres-1.151.0-1.fc43.x86_64.rpm to update to the 1.151.0 one thats not yet an update.
I mean ideally we would help the maintainer sort this and get proper builds, but synapse is tricky.
I published the common issue and moved this discussion here.