Bug 489697

Created attachment 171343 [details]
Screenshot of Tellico

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
After an update of Manjaro Stable (no update of Tellico, but update of lib32-libxslt, lib32-libxml2, ...),Tellico seems to be working correctly, but the content display section is now blank.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
In console : 
null stylesheet pointer for  "/home/goupil2/.local/share/tellico/entry-templates/Berean_Bottin-Gd_format-marron.xsl"
invalid xslt handler
I/O warning : failed to load "%2Fhome%2Fgoupil2%2F.local%2Fshare%2Ftellico%2Fentry-templates%2FBerean_Bottin-Gd_format-marron.xsl": No such file or directory
null stylesheet pointer for  "/home/goupil2/.local/share/tellico/entry-templates/Berean_Bottin-Gd_format-marron.xsl"
invalid xslt handler
I/O warning : failed to load "%2Fhome%2Fgoupil2%2F.local%2Fshare%2Ftellico%2Fentry-templates%2FBibliography.xsl": No such file or directory
null stylesheet pointer for  "/home/goupil2/.local/share/tellico/entry-templates/Bibliography.xsl"
invalid xslt handler
I/O warning : failed to load "%2Fhome%2Fgoupil2%2F.local%2Fshare%2Ftellico%2Fentry-templates%2FBerean_Bottin-Gd_format-marron2.xsl": No such file or directory
null stylesheet pointer for  "/home/goupil2/.local/share/tellico/entry-templates/Berean_Bottin-Gd_format-marron2.xsl"
invalid xslt handler
I/O warning : failed to load "%2Fhome%2Fgoupil2%2F.local%2Fshare%2Ftellico%2Fentry-templates%2FBerean_Bottin-Gd_format-marron2.xsl": No such file or directory

EXPECTED RESULT
A display of the content of entries in my Tellico database (but nothing is displayed anymore)

SOFTWARE/OS VERSIONS
Linux Manjaro
Desktop environment: X-Cinnamon (6.2.2) / Xorg 11.0 (1.21.1.13)


ADDITIONAL INFORMATION
The model files are still there, but none of them seem to be recognized.
I think the problem is due to an XML-related library update, but I don't know which one exactly.
Do you have any idea please?