After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768717 - Possible race condition with fontconfig cache update mechanism
Possible race condition with fontconfig cache update mechanism
Status: RESOLVED INCOMPLETE
Product: gnome-settings-daemon
Classification: Core
Component: xsettings
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2016-07-12 10:03 UTC by Raphael Hertzog
Modified: 2017-01-16 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raphael Hertzog 2016-07-12 10:03:11 UTC
During a package upgrade done in a graphical terminal, the update of the fonts-cantarell package can lead to a desktop showing squares instead of the expected text labels. The reason is that dpkg unpacks files with .dpkg-tmp extensions and when it has unpacked all the files, it renames them back into their definitive name. Unfortunately, it seems that the gnome-settings-daemon monitoring of the directory can trigger in during this process and fontconfig will happily register the .dpkg-tmp files which are then removed shortly afterwards.

For some reason (and that's what I call the race condition), the removal of those .dpkg-tmp files is not caught by gnome-settings-daemon and the cache is not updated a second time. In parallel, the Debian packaging will run "fc-cache -s" after the unpack has been finished.

Somehow I have the feeling that the removal of the timeout in https://bugzilla.gnome.org/show_bug.cgi?id=748776 makes this race condition much more likely to happen...

Related links/bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=96896 (asking fontconfig to ignore .dpkg-tmp files)
https://bugs.debian.org/828037
Comment 1 Bastien Nocera 2017-01-16 03:17:51 UTC
The patch from bug 773556 probably helps. Please see whether you can reproduce the problem with that patch.

There's a reason why we don't support online updates though...
Comment 2 Raphael Hertzog 2017-01-16 11:33:41 UTC
Sorry, I don't have the time to check this and it's not 100% reproductible since it's a bit timing dependent (and we made our fontconfig configuration a bit more robust as well).

Feel free to close the ticket as the fix for #748776 looks likely to fix this issue as well.