Bug 8455 - The linux client doesn't handle reset-dirs directive from fontconfig
Summary: The linux client doesn't handle reset-dirs directive from fontconfig
Status: RESOLVED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.19.0
Assignee: Pierre Ossman
URL:
Keywords: prosaic
Depends on:
Blocks:
 
Reported: 2024-11-22 10:51 CET by Alexander Zeijlon
Modified: 2025-05-13 11:11 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Alexander Zeijlon cendio 2024-11-22 10:51:49 CET 
We get this warning when starting tlclient from a terminal on linux:
> Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"

It doesn't seem to affect anything but it looks bad that we arent handling reset-dirs.

This is on Fedora 40 that provides a newer fontconfig than we currently have in cenbuild.
Comment 1 Alexander Zeijlon cendio 2024-11-22 10:55:58 CET 
I also found a discussion which indicate that we should build the client against a newer fontconfig: https://bugzilla.redhat.com/show_bug.cgi?id=1770450
Comment 2 Alexander Zeijlon cendio 2024-11-22 11:17:09 CET 
"Just for fun" I tested to build the client with fontconfig 2.15 and the warning disappears. So this is likely an easy fix.
Comment 4 Pierre Ossman cendio 2025-05-13 10:59:55 CEST 
Doing this now because we need a new fontconfig for bug 8584.
Comment 5 Pierre Ossman cendio 2025-05-13 11:00:50 CEST 
Tested the server on Ubuntu 24.04. With ThinLinc 4.18.0, I get:

> ...
> --- End system information ---
> Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
> Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
> ...

But with an updated fontconfig, I get no such warning lines.
Note You need to log in before you can comment on or make changes to this bug.