public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [PATCH xpdf] Add desktop menu entry
Date: Fri, 03 Nov 2017 13:11:00 -0000	[thread overview]
Message-ID: <7926ca52-9cee-346c-9c2d-7e04380bba3a@cornell.edu> (raw)
In-Reply-To: <3dbb6027-7cfc-3171-b982-1afaa0bf4e95@cygwin.com>

On 11/3/2017 2:52 AM, Yaakov Selkowitz wrote:
> On 2017-10-28 13:00, Ken Brown wrote:
>> On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
>>> ---
>>>    xpdf.cygport | 4 ++++
>>>    1 file changed, 4 insertions(+)
>>
>> After making this change I get the following warning when starting xpdf
>> in an xterm window:
>>
>> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
>> '/tmp/runtime-kbrown'
>>
>> I googled the message, but none of the solutions appeared to apply.  Do
>> you know how to suppress this warning?  I assume it results from the
>> fact that I'm not working in a desktop environment.
> 
> I don't see how adding a desktop menu entry would cause this; are you
> sure it wasn't happening before?  Or maybe the Qt 5.9.2 update caused
> it?  Either way, this isn't an xpdf specific issue, and would have to be
> fixed or worked around elsewhere.

You're right.  Moving the desktop entry out of the way doesn't make any 
difference.  It's just coincidence that I first noticed it after making 
that change.

In the meantime, I have another xpdf problem.  After my update of the 
ghostscript fonts, I get the following errors when starting xpdf:

Config Error: No display font for 'Courier'
Config Error: No display font for 'Courier-Bold'
Config Error: No display font for 'Courier-BoldOblique'
Config Error: No display font for 'Courier-Oblique'
Config Error: No display font for 'Helvetica'
Config Error: No display font for 'Helvetica-Bold'
Config Error: No display font for 'Helvetica-BoldOblique'
Config Error: No display font for 'Helvetica-Oblique'
Config Error: No display font for 'Symbol'
Config Error: No display font for 'Times-Bold'
Config Error: No display font for 'Times-BoldItalic'
Config Error: No display font for 'Times-Italic'
Config Error: No display font for 'Times-Roman'
Config Error: No display font for 'ZapfDingbats'

Reinstalling the old ghostscript-fonts-std-8.11-1 fixes it.  Copying the 
files from /usr/share/fonts/urw-base35 to /usr/share/ghostscript/fonts 
doesn't fix it.

Do you happen to know how Fedora handles this?  I didn't see anything 
obvious in xpdf.spec.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-11-03 13:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 21:00 Yaakov Selkowitz
2017-10-27 22:34 ` Ken Brown
2017-10-28 18:00 ` Ken Brown
2017-10-28 19:26   ` Brian Inglis
2017-10-28 19:55     ` Ken Brown
2017-10-30 18:59       ` Brian Inglis
2017-11-03  6:52   ` Yaakov Selkowitz
2017-11-03 13:11     ` Ken Brown [this message]
2017-11-03 17:05       ` Ken Brown
2017-11-06  9:48         ` Yaakov Selkowitz
2017-11-06 12:28           ` Ken Brown

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

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

  git send-email \
    --in-reply-to=7926ca52-9cee-346c-9c2d-7e04380bba3a@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /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.
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).