Skip to main content ↑ ↓
Topic: Fontconfig warning: using without calling FcInit() (Read 6353 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Fontconfig warning: using without calling FcInit()

I get this warning if I open for example geany or libreoffice from terminal since last update to fontconfig. What can I do to get rid of this warning? I didn't find anything useful from searching.

Re: Fontconfig warning: using without calling FcInit()

Reply #1 –
Quote from: XyzzyX – on
I get this warning if I open for example geany or libreoffice from terminal since last update to fontconfig. What can I do to get rid of this warning? I didn't find anything useful from searching.


FWIW - I can ***not*** confirm this.  All I get is a bunch of the normal gtk warnings.... at least from Libreoffice

Re: Fontconfig warning: using without calling FcInit()

Reply #2 –
I am sorry - is this what you are talking about?

(soffice:5231): Gtk-WARNING **: 01:31:22.830: Theme parsing error: gtk.css:187:34: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.
Fontconfig warning: using without calling FcInit()
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.sun.star.lib.util.NativeLibraryLoader in an unnamed module (file:/usr/lib/libreoffice/program/classes/libreoffice.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled



When I opened a spread sheet, this came up.  My inclination is to say, "Why does this bother you".  I mean that sincerely.  I assume you have a good reason why this bothers you, and I am sincerely interested in what that reason is, because functionality does not seem to be affected. 

It seems like just more broken FreeDesktop stuff that is broken.  It happens so frequently I stopped paying attention to these events somewhere about 2006.

Re: Fontconfig warning: using without calling FcInit()

Reply #3 –
It's a warning that suddenly started to show up, and I just assumed it meant something is wrong and needs to be fixed. But if it's just some useless nonsense warning i can live with it.

Re: Fontconfig warning: using without calling FcInit()

Reply #4 –
Quote from: XyzzyX – on
It's a warning that suddenly started to show up, and I just assumed it meant something is wrong and needs to be fixed. But if it's just some useless nonsense warning i can live with it.


It is a good theoretical question as to what has changed.  It is not like the initialization function is particularly new that is affects a dozen different programs that depend on it.  Something changed, probably upstream.  It is possibly a one line solution to the code base.

Re: Fontconfig warning: using without calling FcInit()

Reply #5 –
fwiw, I get it as well with any gtk2 app and some gtk3 apps

Re: Fontconfig warning: using without calling FcInit()

Reply #6 –
Quote from: strange – on
fwiw, I get it as well with any gtk2 app and some gtk3 apps


the thing to do at this point is to look at the source code for libreoffice et al to see if fnctl() is actually called.  If not, then we have a bug report to make.  If it is called, then something is wrong with gtk/gnome's compiler

Re: Fontconfig warning: using without calling FcInit()

Reply #7 –
i just got this message when launching a virtual machine with qemu-system-x84_64
fortunately, it seems to be just a warning, and it's not blocking :)

Re: Fontconfig warning: using without calling FcInit()

Reply #8 –
I'm also getting this message when running simply ANY app from the console:

Fontconfig warning: using without calling FcInit()

Looks like it's a bug somewhere in fontconfig: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/472

Or pango, cairo... not sure. Here's a GTK issue as well: https://gitlab.gnome.org/GNOME/gtk/-/issues/7639

Re: Fontconfig warning: using without calling FcInit()

Reply #9 –
I think it's a message to the developers that they should call FcInit() in their code, not a warning to the user.

Re: Fontconfig warning: using without calling FcInit()

Reply #12 –
Quote from: nous – on
@XyzzyX oh, the lore behind this username...
I don't understand. I'm from Sweden. I was just playing around with the letters x, y and z. Does it mean something? 

Re: Fontconfig warning: using without calling FcInit()

Reply #13 –
Quote from: XyzzyX – on
I don't understand. I'm from Sweden. I was just playing around with the letters x, y and z. Does it mean something? 
It was the legendary magic word of the early computer era, along with a couple less memorable ones.

Re: Fontconfig warning: using without calling FcInit()

Reply #14 –
Quote from: nous – on
Quote from: XyzzyX – on
I don't understand. I'm from Sweden. I was just playing around with the letters x, y and z. Does it mean something? 
It was the legendary magic word of the early computer era, along with a couple less memorable ones.
Thanks for telling me. Funny I choose that without knowing it. But I have an X at the and so not exactly the same, but very close.