On Thu, Apr 12, 2018 at 07:08:23PM +0200, Emilio Pozuelo Monfort wrote:
> On 12/04/18 04:01, brian m. carlson wrote:
> > I've also seen these errors, except that they're showing up in my tmux
> > panes, which is significantly more annoying than .xsession-errors.  This
> > is probably because vim-gtk3 (gvim) links to libfontconfig1.
> > 
> > libfontconfig definitely shouldn't be producing errors to stdout or
> > stderr unless specifically requested by the calling application.
> Have you restarted your applications? AFAICS this is caused by old 
> libfontconfig
> reading the new conf files. If you restart them the warnings should go away.
> (I know this isn't an ideal solution)

No, I haven't.  I upgraded from within my tmux session and suddenly all
my panes had junk in them.  I don't normally log out or reboot except
for kernel updates.

I would appreciate it if you'd work with upstream to get them to remove
the code that prints these messages.  There's no legitimate reason for a
shared library to print anything unless explicitly requested by the
calling application .

This would be less of an issue if fontconfig didn't reload config files
in existing processes.
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

Attachment: signature.asc
Description: PGP signature

Reply via email to