infinality-bundle: good looking fonts made (even) easier

bohoomil · 2014-11-25 22:48:12

@X-dark Frankly speaking, I'm not sure why there are differences between bitmap fonts packaging standards in Arch. IIRC, terminus-font is the only package that works correctly with freetype2, including the ultimate version with upstream and Infinality patches applied. Freetype developers are introducing lots of changes and fixes now, which means that every freetype2-iu update reflects the scope of new features that sooner or later will be available in the new, major release. Maybe this should be the question to Arch maintainers, why the same packaging standards aren't used consistently across all packages providing fonts in pcf format?

X-dark · 2014-11-25 23:05:47

Good question.

Moter8 · 2014-11-27 17:40:33

Edit: So in the end after executing

mv /etc/pacman.d/gnupg{,.bak} ; pacman-key --init ; pacman-key --populate

I could verify keys again. Is this a arch bug?

Log of executed commands/terminal history: http://hastebin.com/raw/kuvewoniti

Having some Issue verifying the GPG Key.

Added the repos to the pacmand.conf file.
Then executed

# pacman-key -r 962DDE58
# pacman-key --lsign-key 962DDE58

But only got http://i.imgur.com/nH1tsIu.png back, eg the key could not get locally signed.

Another user on the IRC is having the same issue and pasted http://pastebin.com/HE2Jx5ck

Then some guy told us to try

sudo gpg --homedir /etc/pacman.d/gnupg --lsign-key 962DDE58

Then we tried to install pinentry but it still gives the same error: http://i.imgur.com/V6wNKT1.png

Troubleshooting steps done, all 3 failed:
Searched for pac{new,save} files. none found

killall -9 gpg-agent ; gpg-agent --homedir /etc/pacman.d/gnupg --use-standard-socket --daemon --pinentry-program /usr/bin/pinentry-curses ; gpg --homedir /etc/pacman.d/gnupg --lsign-key 962DDE58

su - root && gpg --homedir /etc/pacman.d/gnupg --lsign-key 962DDE58

Last edited by Moter8 (2014-11-27 18:06:39)

jasonwryan · 2014-11-27 17:58:21

Please don't post screenshots of text (especially errors), paste the actual errors...

Moter8 · 2014-11-27 18:05:24

jasonwryan wrote:

Please don't post screenshots of text (especially errors), paste the actual errors...

I've just edited the post. Sorry for the inconvenience. Commands / Terminal history: http://hastebin.com/raw/kuvewoniti

Last edited by Moter8 (2014-11-27 18:06:27)

parazyd · 2014-11-27 21:25:20

That could be happening because of the recent gnupg update...

vinadoros · 2014-11-28 03:21:12

Just a quick followup regarding the gnupg and pacman-key stuff, the instructions by Moter8 still don't seem to work on a fresh install, unless a /root/.gnupg folder already exists. If you do the following commands (such as from above), you will no longer be able to import the keys:

rm -rf /root/.gnupg
mv /etc/pacman.d/gnupg{,.bak} ; pacman-key --init ; pacman-key --populate

In order to fix the problem on my end (my situation was for a fresh Arch install), I executed dirmngr as root, and then importing the key with the following commands worked just fine:

sudo pacman-key -r 962DDE58
sudo pacman-key --lsign-key 962DDE58

Summary: Run dirmngr as root/sudo (not as a daemon), and it will create the /root/.gnupg folder. Kill it afterwards, and I believe everything should just work as before.

Side Question: Does anyone know why we need to do this since the recent gnupg upgrade? Does it require a change to pacman-key, since it doesn't seem to automatically take care of this as I would expect...

rumpelsepp · 2014-12-01 08:26:19

I once reported this issue on github: https://github.com/bohoomil/fontconfig- … /issues/56
Now I have figured out what's going on here. I use plasma 5 and it creates a .config/fontconfig/fonts.conf automatically based on the settings in the system settings:

its default is this one. It results in a strange hinting all over the place.

<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
 <match target="font">
  <edit name="rgba" mode="assign">
   <const>none</const>
  </edit>
 </match>
 <match target="font">
  <edit name="hinting" mode="assign">
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <edit name="hintstyle" mode="assign">
   <const>hintmedium</const>
  </edit>
 </match>
 <match target="font">
  <edit name="antialias" mode="assign">
   <bool>true</bool>
  </edit>
 </match>
</fontconfig>

Duplicating the settings as mentioned in the wiki (https://wiki.archlinux.org/index.php/Infinality#Usage) creates this file:

<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
 <match target="font">
  <edit mode="assign" name="rgba">
   <const>rgb</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hinting">
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hintstyle">
   <const>hintfull</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="antialias">
   <bool>true</bool>
  </edit>
 </match>
</fontconfig>

The result of this file is mentioned in the github issue.

What should I do here? Removing .config/fontconfig/ does not solve the issue as it is recreated automatically after login. Is there any possibilty to blacklist this file?

cju · 2014-12-01 14:32:27

Since the latest update, I got the problem that neither ~/.fonts.conf nor ~/.config/fontconfig/fonts.conf is recognized anymore: https://bbs.archlinux.org/viewtopic.php?id=190515

Setting aliases via /etc/fonts/conf.avail.infinality/35-repl-custom.conf works still fine, but I'd really like to keep user specific font aliases…

bohoomil · 2014-12-01 18:46:52

@cju Yes, I know about it. The old behaviour will be back in the next fontconfig-iu release. Sorry for the inconvenience (and the mess).

cju · 2014-12-01 19:11:08

bohoomil wrote:

@cju Yes, I know about it. The old behaviour will be back in the next fontconfig-iu release. Sorry for the inconvenience (and the mess).

Glad to hear, I almost doubted my own sanity.

Thanks for all your efforts.

bohoomil · 2014-12-01 21:20:48

@rumpelsepp Try changing hintfull to hintslight in your Plasma 5 system settings.

rumpelsepp · 2014-12-02 13:27:06

bohoomil wrote:

@rumpelsepp Try changing hintfull to hintslight in your Plasma 5 system settings.

It works, thanks!

cju · 2014-12-06 20:51:49

cju wrote:

bohoomil wrote:
@cju Yes, I know about it. The old behaviour will be back in the next fontconfig-iu release. Sorry for the inconvenience (and the mess).
Glad to hear, I almost doubted my own sanity.
Thanks for all your efforts.

Just wanted to confirm that with the latest update, the user-specific fonts.conf works again, so thanks again.

Carl Karl · 2014-12-08 05:28:01

Hello, I followed the official instructions about gnugpg and the pacman keyring https://www.archlinux.org/news/gnupg-21 … n-keyring/

pacman -Syu haveged
systemctl start haveged
systemctl enable haveged

rm -fr /etc/pacman.d/gnupg
pacman-key --init
pacman-key --populate archlinux

but now I have to re-add the key for infinality but I'm not able:

# pacman-key -r 962DDE58
gpg: keyserver receive failed: System error w/o errno
==> ERROR: Remote key not fetched correctly from keyserver.

What's the solution for that?

karol · 2014-12-08 12:44:02

I did it yesterday and it worked for me. Try again.
https://wiki.archlinux.org/index.php/Pa … mport_keys

Carl Karl · 2014-12-08 14:29:04

Adding and signing the key worked after I changed to the MIT keyserver:
/etc/pacman.d/gnupg/gpg.conf is now

no-greeting
no-permission-warning
lock-never
keyserver hkp://pgp.mit.edu:11371
keyserver-options timeout=10

Whyever. Maybe my ISP blocked the port to original keyserver? Seems so: https://wiki.archlinux.org/index.php/Pa … mport_keys

DebauchedSloth · 2014-12-08 16:02:24

Same problem here. Pretty sure that port is not blocked.

Switching to the mit gpg server solved it as well.

Reded · 2014-12-08 17:56:03

Just posting a 'me too'

I'm on Sky Broadband (In UK), though I wonder why they would block these ports...

bohoomil · 2014-12-08 22:53:40

Unfortunately, I have no idea why you are experiencing problems with the key. Generating a fresh keyring, importing and signing third-party keys in the usual way as described in the Wiki, finally issuing 'pacman -Syyu' worked for me on two independent Arch setups (both are set to use the default key server: hkp://pool.sks-keyservers.net). And that was it.

SimFox3 · 2014-12-10 04:19:11

For some reason, "fc-presets set" doesn't set the free fonts--only the "MS" fonts:

[root@Vaio-Saad conf.d]# fc-presets check
 [ combi ] is not set 
 :: Run <fc-presets help> for more information.
 [ free ] is not set 
 :: Run <fc-presets help> for more information.
 [ ms ] is not set 
 :: Run <fc-presets help> for more information.

[root@Vaio-Saad conf.d]# fc-presets set
1) combi
2) free
3) ms
4) reset
5) quit
Enter your choice... 2
 [ free ] preset chosen...
Done.

[root@Vaio-Saad conf.d]# fc-presets check
 [ combi ] is not set 
 :: Run <fc-presets help> for more information.
 [ free ] is not set 
 :: Run <fc-presets help> for more information.
 [ ms ] is not set 
 :: Run <fc-presets help> for more information.

[root@Vaio-Saad conf.d]# fc-presets set
1) combi
2) free
3) ms
4) reset
5) quit
Enter your choice... 3
 [ ms ] preset chosen...
Done.

[root@Vaio-Saad conf.d]# fc-presets check
 [ combi ] is not set 
 :: Run <fc-presets help> for more information.
 [ free ] is not set 
 :: Run <fc-presets help> for more information.

 5 symlinks found.
 The active preset seems to be [ ms ].
 Checking symlinks now...

30-metric-aliases-ms.conf is OK
37-repl-global-ms.conf is OK
60-latin-ms.conf is OK
65-non-latin-ms.conf is OK
66-aliases-wine-ms.conf is OK

Any ideas? I've tried "fc-presets set" reset many times.

Last edited by SimFox3 (2014-12-10 04:19:57)

bohoomil · 2014-12-10 08:08:40

Go to '/etc/fonts/conf.d' and see if

1. there are any broken symlinks with 'free' in their names,
2. there are any regular files with 'free' in their names.

When you set the 'free' preset, you should have 5 symbolic links in '/etc/fonts/conf.d' to 5 targets in '/etc/fonts/conf.avail.infinality/free'. If the preset hasn't been set correctly, it means that either there are not enough links or there are too many of them (e.g. there's yet another file--a regular one or a link--recognized as a valid one, but which probably doesn't belong to the selected group).

If you track the bad guy down, you can try running 'fc-presets' again or set the preset the manual way:

# cd /etc/fonts/conf.d
# rm *-free.conf
# ln -sf ../conf.avail.infinality/free/*.conf .

In either case, isolate the culprit first.

SimFox3 · 2014-12-10 17:49:56

bohoomil wrote:

Go to '/etc/fonts/conf.d' and see if
1. there are any broken symlinks with 'free' in their names,
2. there are any regular files with 'free' in their names.
In either case, isolate the culprit first.

Thanks! There was an extra 93-final-lang-spec-free.conf symbolic link that didn't point to anything. I deleted it and now I get the correct output:

[root@Vaio-Saad conf.d]# fc-presets check
[ combi ] is not set
:: Run <fc-presets help> for more information.
5 symlinks found.
The active preset seems to be [ free ].
Checking symlinks now...
30-metric-aliases-free.conf is OK
37-repl-global-free.conf is OK
60-latin-free.conf is OK
65-non-latin-free.conf is OK
66-aliases-wine-free.conf is OK

Thanks again!

rcrath · 2014-12-11 21:32:28

I also had the key problem. Switching to MIT keyserver fixed it. oceanic timewarner cable here.

bohoomil · 2014-12-12 00:32:53

@rcrath Did you try importing and signing the key right after the new keyring had been created and before you run 'pacman -Syu' again?

Arch Linux

#1501 2014-11-25 22:48:12

Re: infinality-bundle: good looking fonts made (even) easier

#1502 2014-11-25 23:05:47

Re: infinality-bundle: good looking fonts made (even) easier

#1503 2014-11-27 17:40:33

Re: infinality-bundle: good looking fonts made (even) easier

#1504 2014-11-27 17:58:21

Re: infinality-bundle: good looking fonts made (even) easier

#1505 2014-11-27 18:05:24

Re: infinality-bundle: good looking fonts made (even) easier

#1506 2014-11-27 21:25:20

Re: infinality-bundle: good looking fonts made (even) easier

#1507 2014-11-28 03:21:12

Re: infinality-bundle: good looking fonts made (even) easier

#1508 2014-12-01 08:26:19

Re: infinality-bundle: good looking fonts made (even) easier

#1509 2014-12-01 14:32:27

Re: infinality-bundle: good looking fonts made (even) easier

#1510 2014-12-01 18:46:52

Re: infinality-bundle: good looking fonts made (even) easier

#1511 2014-12-01 19:11:08

Re: infinality-bundle: good looking fonts made (even) easier

#1512 2014-12-01 21:20:48

Re: infinality-bundle: good looking fonts made (even) easier

#1513 2014-12-02 13:27:06

Re: infinality-bundle: good looking fonts made (even) easier

#1514 2014-12-06 20:51:49

Re: infinality-bundle: good looking fonts made (even) easier

#1515 2014-12-08 05:28:01

Re: infinality-bundle: good looking fonts made (even) easier

#1516 2014-12-08 12:44:02

Re: infinality-bundle: good looking fonts made (even) easier

#1517 2014-12-08 14:29:04

Re: infinality-bundle: good looking fonts made (even) easier

#1518 2014-12-08 16:02:24

Re: infinality-bundle: good looking fonts made (even) easier

#1519 2014-12-08 17:56:03

Re: infinality-bundle: good looking fonts made (even) easier

#1520 2014-12-08 22:53:40

Re: infinality-bundle: good looking fonts made (even) easier

#1521 2014-12-10 04:19:11

Re: infinality-bundle: good looking fonts made (even) easier

#1522 2014-12-10 08:08:40

Re: infinality-bundle: good looking fonts made (even) easier

#1523 2014-12-10 17:49:56

Re: infinality-bundle: good looking fonts made (even) easier

#1524 2014-12-11 21:32:28

Re: infinality-bundle: good looking fonts made (even) easier

#1525 2014-12-12 00:32:53

Re: infinality-bundle: good looking fonts made (even) easier

Board footer