You are not logged in.
Pages: 1
Topic closed
Today I updated the system regularly and got the error "Unable to open this file in the current system configuration", while trying to open .m scripts in MATLAB. It has worked normally up to today's update.
I have tried the solution from ArchWiki as here, but unfortunately, this didn't help. ![]()
cd matlab_root/bin/glnxa64/
mv libfreetype.so.6 libfreetype.so.6.oldDoes anyone have an idea how to fix this or how to debug this?
Last edited by Halunke098 (2026-05-13 23:00:47)
Offline
Mod note: Moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
After downgrading to 05/10 using pacman -Syyuu
Server = https://archive.archlinux.org/repos/2026/05/10/$repo/os/$archMATLAB now opens .m files again normally.
One of the following packages is causing the issue
warning: gnutls: downgrading from version 3.8.13-2 to version 3.8.13-1
warning: gst-plugins-bad-libs: downgrading from version 1.28.2-2 to version 1.28.2-1
warning: gst-plugins-base: downgrading from version 1.28.2-2 to version 1.28.2-1
warning: gst-plugins-base-libs: downgrading from version 1.28.2-2 to version 1.28.2-1
warning: gst-plugins-good: downgrading from version 1.28.2-2 to version 1.28.2-1
warning: gstreamer: downgrading from version 1.28.2-2 to version 1.28.2-1
warning: libelf: downgrading from version 0.195-1 to version 0.194-2
warning: libmd: downgrading from version 1.2.0-1 to version 1.1.0-2
warning: nettle: downgrading from version 4.0-1 to version 3.10.2-1Does anyone have an idea how to figure out which one makes MATLAB unhappy? ![]()
[Update:]
It turns out nettle 4.0-1 is causing the issue. Downloading older version from here and export it to MATLAB fixed this.
export LD_LIBRARY_PATH="/opt/MATLAB/nettle-3.10.2-1/usr/lib/:$LD_LIBRARY_PATH"Last edited by Halunke098 (2026-05-13 22:58:03)
Offline
Thank you for this. I just hit the issue today. We really should add something to the Wiki about how to bisect the ALA to find the problematic package and then how to download it and add it to the path some people don't try and run the library system wide.
Offline
Moderator Note
Closing this thread.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1
Topic closed