# paraview4.4 fail on debian 13
**URL:** https://discourse.paraview.org/t/paraview4-4-fail-on-debian-13/17078
**Category:** ParaView Support
**Created:** [August 14, 2025, 1:39pm UTC](https://discourse.paraview.org/t/paraview4-4-fail-on-debian-13/17078 "2025-08-14T13:39:57Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@yudai-patronai](https://discourse.paraview.org/u/yudai-patronai)
#### Post date: [August 14, 2025, 1:39pm UTC](https://discourse.paraview.org/t/paraview4-4-fail-on-debian-13/17078/1 "2025-08-14T13:39:57Z")
After the latest upgrade to debian 13 (kernel version 41), my old paraview 4.4 binaries, which used to work seamlessly for several years, - failed with the message
```auto
symbol lookup error: /lib/x86_64-linux-gnu/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var
```
WOrkarounds like those offered in [https://github.com/helloSystem/LinuxRuntime/issues/11](https://github.com/helloSystem/LinuxRuntime/issues/11) don’t work. The error remains.
What is it all about ? Can it be eliminated anyhow ?
---
### Author:  [@GregVernon](https://discourse.paraview.org/u/GregVernon)
#### Post date: [August 14, 2025, 5:57pm UTC](https://discourse.paraview.org/t/paraview4-4-fail-on-debian-13/17078/2 "2025-08-14T17:57:17Z")
You’re using binaries from ~10 years ago in an operating system that is 5 _days_ old. I’m not surprised that something broke. Is there a reason you can’t update ParaView?
FWIW, if I understand the issue correctly, Debian 13 is loading a `fontconfig` that expects a newer FreeType symbol (`FT_Done_MM_Var`), but ParaView ends up loading an older `fontconfig` that doesn’t have it – probably because ParaView 4.4 shipped its own `fontconfig` lbrary. You could probably do some `LD_LIBRARY_PATH` (or related) magic to hack a fix. But honestly probably fastest to just update ParaView.