FS#70305 - [lib32-fontconfig] errors reading /etc/fonts/conf.d since 2:2.13.93

Attached to Project: Community Packages
Opened by chu (chaika) - Monday, 05 April 2021, 18:22 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 27 April 2021, 07:49 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Since 2:2.13.93 running fc-cache-32 (either directly or from the pacman hook) returns the following error:
Fontconfig error: failed reading config file: /etc/fonts/conf.d: (errno 21)

downgrading to 2.13.91+48+gfcb0420 fixes the issue. fontconfig doesn't have this problem
Additional info:
version: 2:2.13.93

Steps to reproduce:
Install lib32-fontconfig 2.13.93-1 or later
run fc-cache-32
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 27 April 2021, 07:49 GMT
Reason for closing:  Not a bug
Comment by Jan Alexander Steffens (heftig) - Monday, 05 April 2021, 20:47 GMT
I can't reproduce this. It works for me.
Comment by chu (chaika) - Monday, 05 April 2021, 22:24 GMT
I certainly can't explain it, it just doesn't make sense that it only happens to the lib32 version, and the error suggests that it's trying to open the folder as a file (or that's how I took it) which just seems odd to me, for the sake of providing more information, my /etc/fonts folder contains: conf.avail, conf.d and fonts.conf

the first two being folders, and the last one a text file.
Comment by Chris Cortese (chrisco23) - Sunday, 25 April 2021, 21:50 GMT
I hit this problem when trying to install material-icons-git for a weather module for polybar.

But (and sorry if this sounds newbie) can you please explain how you accomplished this downgrade?

I have tried the "pacman -U" method, which failed with a great many errors such as "fontconfig: /etc/fonts/conf.d/10-hinting-slight.conf exists in filesystem".

I have tried both the "downgrade" and "downgrader-git" packages, and they fail in a similar way.

Obviously uninstalling "fontconfig" would break a great many other packages.

Hard to believe I've spent so much time just trying to install a font for my polybar, but yes I'm in the same boat here. I'm out of ideas and any other thing I might try doesn't feel safe.


Comment by Tom Englund (gulafaran) - Monday, 26 April 2021, 11:52 GMT
happends for me too.
Comment by Jan Alexander Steffens (heftig) - Monday, 26 April 2021, 12:02 GMT
Are there broken links in /etc/fonts/conf.d/? You might want to fix those (conf.avail was moved to /usr/share/fontconfig/conf.avail) or delete them.
Comment by Tom Englund (gulafaran) - Monday, 26 April 2021, 12:04 GMT
doesnt look like so https://gist.github.com/gulafaran/040af737dbc678253ee56901b54db6c5
Comment by Jan Alexander Steffens (heftig) - Monday, 26 April 2021, 14:49 GMT
What does `stat /etc/fonts/conf.d` show?
Comment by Chris Cortese (chrisco23) - Monday, 26 April 2021, 14:57 GMT
No broken links for me. Looks very similar to Tom's. I do notice that every single one of those links for me is dated March 30 on my system. Maybe that's a clue?

```
$ stat /etc/fonts/conf.d
File: /etc/fonts/conf.d
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 10303h/66307d Inode: 263307 Links: 2
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2120-01-15 05:08:53.864481007 -0800
Modify: 2021-04-25 14:09:21.218424333 -0700
Change: 2021-04-25 14:09:21.218424333 -0700
Birth: 2017-10-24 17:35:26.184515752 -0700
```
Comment by Jan Alexander Steffens (heftig) - Monday, 26 April 2021, 15:00 GMT
> Access: 2120-01-15 05:08:53.864481007 -0800

Welcome to a preview of the year 2038 problem. Change the access time (`touch` should do it) and this problem should go away (for now).
Comment by Tom Englund (gulafaran) - Monday, 26 April 2021, 15:07 GMT
yep my access time was at 2051-07-04 22:41:07.100088366 +0200 , changing it with touch solved it.
Comment by Chris Cortese (chrisco23) - Monday, 26 April 2021, 16:35 GMT
good catch! Thanks!
Comment by chu (chaika) - Monday, 26 April 2021, 22:59 GMT
I can also confirm that # touch /etc/fonts/conf.d
fixed the issue for me
Comment by chu (chaika) - Tuesday, 27 April 2021, 05:52 GMT
I can also confirm that # touch /etc/fonts/conf.d
fixed the issue for me

Loading...