Matrix was the only application I use, and now because of another shitty update is the only application that doesn’t work. I have no idea what is wrong this time, but I can’t turn it on in any way. The problem with sure is not from me because I have not changed anything since it worked. My patience with Freedombox has long been exhausted to continue to deal with it, let alone reinstall it again. I don’t hope for adequate support anymore. Thinking about how long I lost to solve problems … This is not freedom at all. I will wait a little longer, then I take my freedom and the box goes to the bin.
I agree with your sentiments. I’ve spent many, many hours tinkering with freedombox for it to be all for nothing when an update blows the system to pieces.
Are there no tests before they are released?
I appreciate freedombox is free, but there seems to be very little engagement from freedombox towards the users who are using and testing their product.
Sorry to hear your frustration with Matrix. Can you provide us with the logs of your server? You can do that by opening Cockpit and in Logs menu searching for “matrix”.
Alternatively, you can also share with us the most recent content of /var/log/matrix-synapse/homeserver.log, removing any data that might be sensitive.
It would also be very useful to run sudo systemctl status matrix-synapse in the terminal of your FreedomBox and show us the output.
The FreedomBox team only maintains and releases the freedombox package. We don’t control the many other packages from Debian that make up the system.
The only recent change related to Matrix Synapse is that in FreedomBox 22.11, we changed the apt configuration so that new dependencies for matrix-synapse will be installed from bullseye-backports. This is required for the latest matrix-synapse package to be installable on bullseye.
Normally, packages in Debian stable are very “stable”, meaning that there are very few updates except for security fixes. However, the matrix-synapse package is only in stable backports, not in stable. This is because it needs to be updated often to keep up with the rest of the Matrix network, and they cannot provide long-term support to older versions just yet.
It is no longer necessary. I reinstalled it once again (I lost the count already). This practice reminds me of Windows XP you need to force restart it and reinstall it regularly. I hope this time it lasts longer than the previous one. I wonder if I should ban the updates.
<sunilmohan> emorrp1: So, this is an upstream issue?
<emorrp1> yes and no, yes upstream has merged a code change in develop that will incidentally fix it, but no it's a packaging upload that caused the problem to start occurring yesterday
<emorrp1> https://github.com/matrix-org/synapse/commit/f30bcbd84a651de59777b2a749850f6ca56ce3f0
<emorrp1> Copying details from other channel:
<emorrp1> Error: Synapse 1.57.1 needs matrix-common~=1.1.0, but got matrix-common==1.2.1
<emorrp1> Fix: `sudo sed -i '/common/s/~=/>=/' /usr/lib/python3/dist-packages/matrix_synapse-1.57.1.dist-info/METADATA`
4ff:fe83:360%eth0]/_matrix/client/versions on tcp6