Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] font-tamzen: cannot load font.
@ 2020-09-01 17:25 nihilismus
  2020-09-28  8:50 ` devvesa
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: nihilismus @ 2020-09-01 17:25 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

New issue by nihilismus on void-packages repository

https://github.com/void-linux/void-packages/issues/24590

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  `Void 5.6.19_1 x86_64 GenuineIntel uptodate rFFFFFF`
* package:  
  `font-tamzen-1.11.4_1`

### Expected behavior
`xterm` should use the `tamzen` bitmap font when one executes `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'`, 
### Actual behavior
`xterm` does not use the `tamzen` bitmap font and prints the message: `xterm: cannot load font "-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*"`
### Steps to reproduce the behavior
Execute `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'` in a terminal.
### Notes
- `tamzen` bitmap font is installed inside `/usr/share/fonts/misc`
- `/usr/share/fonts/misc` is not part of the *font path* when querying it with `xset q | grep -A 1 'Font Path:'`.
- A workaround is to add `/usr/share/fonts/misc` to the *font path* with `xset fp+ /usr/share/fonts/misc`.
- A solution to this package would be to move the `tamzen` bitmap font from `/usr/share/fonts/misc` to `/usr/share/fonts/X11/misc` since `terminus-font` (another bitmap font) does not present this issue with `xterm` and is installed inside this last directory.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: font-tamzen: cannot load font.
  2020-09-01 17:25 [ISSUE] font-tamzen: cannot load font nihilismus
@ 2020-09-28  8:50 ` devvesa
  2020-09-28  8:54 ` devvesa
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: devvesa @ 2020-09-28  8:50 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

New comment by devvesa on void-packages repository

https://github.com/void-linux/void-packages/issues/24590#issuecomment-699872557

Comment:
May it be that you have the config `no-bitmaps` enabled on your font configuration?

    file /etc/fonts/conf.d/70-no-bitmaps.conf                                                                                                                                                                 
    /etc/fonts/conf.d/70-no-bitmaps.conf: symbolic link to /usr/share/fontconfig/conf.avail/70-no-bitmaps.conf

If that's so, you can remove the link, but then don't expect Firefox to render pretty fonts. See: https://www.reddit.com/r/voidlinux/comments/izm3xb/firefox_ugly_fonts/

(I have had the same problem)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: font-tamzen: cannot load font.
  2020-09-01 17:25 [ISSUE] font-tamzen: cannot load font nihilismus
  2020-09-28  8:50 ` devvesa
@ 2020-09-28  8:54 ` devvesa
  2022-04-19  2:12 ` github-actions
  2022-05-03  2:13 ` [ISSUE] [CLOSED] " github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: devvesa @ 2020-09-28  8:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

New comment by devvesa on void-packages repository

https://github.com/void-linux/void-packages/issues/24590#issuecomment-699872557

Comment:
May it be that you have the config `no-bitmaps` enabled on your font configuration?

    file /etc/fonts/conf.d/70-no-bitmaps.conf                                                                                                                                                                 
    /etc/fonts/conf.d/70-no-bitmaps.conf: symbolic link to /usr/share/fontconfig/conf.avail/70-no-bitmaps.conf

If that's so, you can remove the link, but then don't expect Firefox to render pretty fonts. See: https://www.reddit.com/r/voidlinux/comments/izm3xb/firefox_ugly_fonts/

(I have had the same problem)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: font-tamzen: cannot load font.
  2020-09-01 17:25 [ISSUE] font-tamzen: cannot load font nihilismus
  2020-09-28  8:50 ` devvesa
  2020-09-28  8:54 ` devvesa
@ 2022-04-19  2:12 ` github-actions
  2022-05-03  2:13 ` [ISSUE] [CLOSED] " github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: github-actions @ 2022-04-19  2:12 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/24590#issuecomment-1101923606

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ISSUE] [CLOSED] font-tamzen: cannot load font.
  2020-09-01 17:25 [ISSUE] font-tamzen: cannot load font nihilismus
                   ` (2 preceding siblings ...)
  2022-04-19  2:12 ` github-actions
@ 2022-05-03  2:13 ` github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: github-actions @ 2022-05-03  2:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

Closed issue by nihilismus on void-packages repository

https://github.com/void-linux/void-packages/issues/24590

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  `Void 5.6.19_1 x86_64 GenuineIntel uptodate rFFFFFF`
* package:  
  `font-tamzen-1.11.4_1`

### Expected behavior
`xterm` should use the `tamzen` bitmap font when one executes `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'`, 
### Actual behavior
`xterm` does not use the `tamzen` bitmap font and prints the message: `xterm: cannot load font "-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*"`
### Steps to reproduce the behavior
Execute `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'` in a terminal.
### Notes
- `tamzen` bitmap font is installed inside `/usr/share/fonts/misc`
- `/usr/share/fonts/misc` is not part of the *font path* when querying it with `xset q | grep -A 1 'Font Path:'`.
- A workaround is to add `/usr/share/fonts/misc` to the *font path* with `xset fp+ /usr/share/fonts/misc`.
- A solution to this package would be to move the `tamzen` bitmap font from `/usr/share/fonts/misc` to `/usr/share/fonts/X11/misc` since `terminus-font` (another bitmap font) does not present this issue with `xterm` and is installed inside this last directory.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-05-03  2:13 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-01 17:25 [ISSUE] font-tamzen: cannot load font nihilismus
2020-09-28  8:50 ` devvesa
2020-09-28  8:54 ` devvesa
2022-04-19  2:12 ` github-actions
2022-05-03  2:13 ` [ISSUE] [CLOSED] " github-actions

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).