unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: 30655@debbugs.gnu.org
Subject: bug#30655: xset(1) not accepting symlink to font path
Date: Wed, 28 Feb 2018 22:54:29 +0100	[thread overview]
Message-ID: <20180228225429.09cd9fd8@jasniac.instanton> (raw)

Hello,

When I follow the manual at
https://www.gnu.org/software/guix/manual/html_node/Application-Setup.html#X11-Fonts ,
I get the message that there is something wrong with the directory I'm
trying to add it:


gast@graviton ~$ xset +fp ~/.guix-profile/share/fonts/truetype
xset:  bad font path element (#0), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax
gast@graviton ~$ ls -l ~/.guix-profile/share/fonts/truetype/fonts.dir 
lrwxrwxrwx 2 root root 84 Jan  1  1970 /home/gast/.guix-profile/share/fonts/truetype/fonts.dir -> /gnu/store/5kp6hj8mk6pgfl4x3cgabl7z379jyyrl-fonts-dir/share/fonts/truetype/fonts.dir
gast@graviton ~$ xset +fp /gnu/store/5kp6hj8mk6pgfl4x3cgabl7z379jyyrl-fonts-dir/share/fonts/truetype


The last command exits with code 0.  Apparently, xset(1) does not want
me to add symlink(2)s that point to valid directories.

—Marco

             reply	other threads:[~2018-02-28 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 21:54 Marco van Hulten [this message]
2018-03-01 16:52 ` bug#30655: xset(1) not accepting symlink to font path Ludovic Courtès
2018-03-01 21:17   ` Marco van Hulten
2018-03-02 12:45     ` Ludovic Courtès
2018-03-01 17:47 ` Alex Kost
2018-03-01 21:27   ` Marco van Hulten
     [not found] ` <handler.30655.D30655.151999474622089.notifdone@debbugs.gnu.org>
2018-03-03 15:26   ` bug#30655: closed (Re: bug#30655: xset(1) not accepting symlink to font path) Marco van Hulten
2018-03-04 21:41     ` Ludovic Courtès
2020-06-17  2:47 ` bug#30655: xset(1) not accepting symlink to font path Royce Strange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180228225429.09cd9fd8@jasniac.instanton \
    --to=marco@hulten.org \
    --cc=30655@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).