# Matrix broken again
**URL:** https://discuss.freedombox.org/t/matrix-broken-again/2473
**Category:** Support
**Created:** [February 20, 2023, 1:34pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473 "2023-02-20T13:34:12Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 1:34pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/1 "2023-02-20T13:34:12Z")
Update last night to 23.3
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.
systemctl status matrix-synapse.service shows
> ● matrix-synapse.service - Synapse Matrix homeserver\>
> Loaded: loaded (/lib/systemd/system/matrix-synapse.service; enabled; vendor preset: enabled)
> Drop-In: /usr/lib/systemd/system/matrix-synapse.service.d
> └─freedombox.conf
> Active: activating (start-pre) since Mon 2023-02-20 07:15:58 CST; 1s ago
> Docs: file:/usr/share/doc/matrix-synapse/README.rst
> Cntrl PID: 30430 (python3)
> Tasks: 1 (limit: 9504)
> Memory: 12.6M
> CPU: 1.236s
> CGroup: /system.slice/matrix-synapse.service
> └─30430 /usr/bin/python3 -m synapse.app.homeserver --config-path=/etc/matrix-synapse/homeserver.yaml --config-path=/etc/matrix-synapse/conf.d/ --generate-keys
Looking through old fixes-
One fix was correcting matrix-common line -
> [@Matrix stopped working](https://discuss.freedombox.org/t/matrix-stopped-working/2143/2):
>
> Hi, I encountered the same issue. There seems to be an issues with the dependencies for synapse in bullseye-backports. Synapse 1.57.1 needs matrix-common~=1.1.0, but got matrix-common==1.2.1 So the only (safe)thing to do is to wait until it has been resolved on the packaging side of things. Until then, no synapse on freedomboxes.
This appears fine in METADATA file (apparently correct \>= arrangement with `>=1.3.0,<2.0.0`)
1.3.0-2 installed. (you can check debian-based builds w/ `sudo apt list | grep matrix-common`
Other was a lack of require python-matrix-common package -
> [@Matrix-synapse.service: Control process exited](https://discuss.freedombox.org/t/matrix-synapse-service-control-process-exited/2293):
>
> After a freedombox update last night the matrix-synapse wont start. This is the ´journalctl -xe´ output: Okt 09 08:24:40 freedombox python3[25914]: Traceback (most recent call last): Okt 09 08:24:40 freedombox python3[25914]: File "/usr/lib/python3.9/runpy.py", line 188, in \_run\_module\_as\_main Okt 09 08:24:40 freedombox python3[25914]: mod\_name, mod\_spec, code = \_get\_module\_details(mod\_name, \_Error) Okt 09 08:24:40 freedombox python3[25914]: File "/usr/lib/python3.9/runpy.py", line 111…
I don’t see the required specification in METADATA nor do I see a similar/same error (or any error at all) in journal.
---
### Author:  [@matthewguy](https://discuss.freedombox.org/u/matthewguy)
#### Post date: [February 20, 2023, 3:06pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/2 "2023-02-20T15:06:06Z")
Thank you for posting. I guess I can stop rebooting, uninstalling, reinstalling rebooting again until it’s fixed.
Is there a “revert to previous version” option so I can get it working again?
M.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 3:13pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/3 "2023-02-20T15:13:42Z")
Good question. And one I don’t know the answer.
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.
---
### Author:  [@Sunil](https://discuss.freedombox.org/u/Sunil)
#### Post date: [February 20, 2023, 3:52pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/4 "2023-02-20T15:52:21Z")
Looks like the latest version of matrix-synapse made available in bullseye-backports today ( [1.74.0-1~bpo11+1](https://packages.debian.org/source/stable-backports/matrix-synapse)) 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?
---
### Author:  [@Sunil](https://discuss.freedombox.org/u/Sunil)
#### Post date: [February 20, 2023, 3:57pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/5 "2023-02-20T15:57:16Z")
Removing python3-icu package seems to allow matrix-synapse to start. Although I am not sure if that would lead to any loss of functionality.
```plaintext
sudo apt remove python3-icu
sudo systemctl restart matrix-synapse
```
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 5:28pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/6 "2023-02-20T17:28:43Z")
I see.
Anyone had a chance to test and see if ~~the older version of~~ removing python3-icu breaks anything?
---
### Author:  [@matthewguy](https://discuss.freedombox.org/u/matthewguy)
#### Post date: [February 20, 2023, 5:45pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/7 "2023-02-20T17:45:11Z")
I have not found anything broken but it got Matrix working and that was my main concern. Have not poked about too much to see if anything has dropped out.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 6:46pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/8 "2023-02-20T18:46:52Z")
Thanks. Looks to be working fine for me so far as well.
Hope matrix-synapse packaging can resolve the issue soon.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 7:18pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/9 "2023-02-20T19:18:36Z")
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.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 20, 2023, 7:47pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/10 "2023-02-20T19:47:26Z")
Belay my last - Read receipt, presence, and notifications all appear to work.
No one was paying attention to their phones. 😆
---
### Author:  [@matthewguy](https://discuss.freedombox.org/u/matthewguy)
#### Post date: [February 23, 2023, 11:54pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/11 "2023-02-23T23:54:05Z")
" Hi Matthew,
The Synapse bullseye-backport is maintained by Debian, not us. You need to raise this issue with them at [bugs.debian.org](http://bugs.debian.org/)
PS, one of the Synapse team members added this when I asked about your issue:
> if the tests on develop and in a icu-related PR pass under the lower version, we’d accept a PR allowing the lower bound on python3-icu.
Best wishes
[Matrix.org](http://Matrix.org) Support"
---
### Author:  [@matthewguy](https://discuss.freedombox.org/u/matthewguy)
#### Post date: [February 23, 2023, 11:56pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/12 "2023-02-23T23:56:33Z")
I think I am already way outside my comfort level and technical knowledge. Hopefully someone else can report this to Debian as I have no idea what I am communicating.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 24, 2023, 12:15am UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/13 "2023-02-24T00:15:08Z")
Good to know. I’ll have to read up and try report the issue to Debian. I’ve not done this too many times either.
Usually, if I have a bug report to raise, I just yell at my coworker to fix his bug.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 24, 2023, 2:56am UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/14 "2023-02-24T02:56:08Z")
Alright. Bug report in.
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [February 24, 2023, 5:54pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/15 "2023-02-24T17:54:28Z")
Looks like freedombox pulled in bpo11+2 this morning, which included a change to matrix-synapse that relaxed the optional dependency python3-icu to version 2.5.
I went to test the version package maintainer recommended that was explicitly supposed to handle this issue and found I was already updated.
---
### Author:  [@matthewguy](https://discuss.freedombox.org/u/matthewguy)
#### Post date: [March 1, 2023, 11:36am UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/16 "2023-03-01T11:36:56Z")
I am getting an error accessing video chat on Matrix saying “unable to access microphone”. Happening on a windows and a Mac (both ends of the attempted call). Rebooted Mac and Freedombox to no avail.
Anyone else having this problem?
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [March 1, 2023, 1:32pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/17 "2023-03-01T13:32:37Z")
Sorry, I’ve not enabled/used voice calling on mine yet so I will be of no help.
If a forum search has turned up nothing, make a new thread. Hopefully one of these our active guys can point the way.
---
### Author:  [@jonny](https://discuss.freedombox.org/u/jonny)
#### Post date: [March 3, 2023, 9:27am UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/18 "2023-03-03T09:27:29Z")
@matthewguy
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](https://github.com/srevinsaju/element-appimage/releases). So I guess I’ll stick with the Appimage until the problem is resolved.
---
### Author:  [@jonny](https://discuss.freedombox.org/u/jonny)
#### Post date: [August 24, 2023, 11:56am UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/19 "2023-08-24T11:56:58Z")
We’ve approached version 1.11.39 now and on my computer the problem still persists. Does anybody have a different experience?
---
### Author:  [@timmy](https://discuss.freedombox.org/u/timmy)
#### Post date: [August 24, 2023, 12:54pm UTC](https://discuss.freedombox.org/t/matrix-broken-again/2473/20 "2023-08-24T12:54:58Z")
Is this for the matthewguy described or my original issue w/ synapse?
[Next page](https://discuss.freedombox.org/t/matrix-broken-again/2473.md?page=2)