[PATCH xpdf] Add desktop menu entry

[PATCH xpdf] Add desktop menu entry

[Yaakov Selkowitz]

---
 xpdf.cygport | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/xpdf.cygport b/xpdf.cygport
index 7382054..dba7994 100644
--- a/xpdf.cygport
+++ b/xpdf.cygport
@@ -86,4 +86,8 @@ src_install() {
 	sed -e 's#/usr/local/share/xpdf#/usr/share/xpdf#g' -i ${D}/etc/xpdfrc
 
 	make_etc_defaults /etc/xpdfrc
+
+	insinto /usr/share/icons/hicolor/scalable/apps
+	newins ${S}/xpdf-qt/xpdf-icon.svg xpdf.svg
+	make_desktop_entry xpdf XpdfReader xpdf "Viewer;Office" "" "MimeType=application/pdf;application/x-pdf;image/pdf;"
 }
-- 
2.14.3


--
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

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

On 10/27/2017 5:00 PM, Yaakov Selkowitz wrote:
> ---
>   xpdf.cygport | 4 ++++
>   1 file changed, 4 insertions(+)

Thanks!

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

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

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.

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

Re: [PATCH xpdf] Add desktop menu entry

[Brian Inglis]

On 2017-10-28 12: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.

Normally set to /run/user/$(id -u)/, sometimes .../$(id -un)/, created by first
app after login.
I have a postinstall script to create /run/{,blkid,lock,user}/ directories with
mode a+rwxt, remove /var/{run,lock} directories and create symlinks from those
to /run/{,lock}/, to provide a more normal Unix/Linux environment for ported apps.

From https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html:

"$XDG_RUNTIME_DIR defines the base directory relative to which user-specific
non-essential runtime files and other file objects (such as sockets, named
pipes, ...) should be stored. The directory MUST be owned by the user, and he
MUST be the only one having read and write access to it. Its Unix access mode
MUST be 0700.

The lifetime of the directory MUST be bound to the user being logged in. It MUST
be created when the user first logs in and if the user fully logs out the
directory MUST be removed. If the user logs in more than once he should get
pointed to the same directory, and it is mandatory that the directory continues
to exist from his first login to his last logout on the system, and not removed
in between. Files in the directory MUST not survive reboot or a full
logout/login cycle.

The directory MUST be on a local file system and not shared with any other
system. The directory MUST by fully-featured by the standards of the operating
system. More specifically, on Unix-like operating systems AF_UNIX sockets,
symbolic links, hard links, proper permissions, file locking, sparse files,
memory mapping, file change notifications, a reliable hard link count must be
supported, and no restrictions on the file name character set should be imposed.
Files in this directory MAY be subjected to periodic clean-up. To ensure that
your files are not removed, they should have their access time timestamp
modified at least once every 6 hours of monotonic time or the 'sticky' bit
should be set on the file.

If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement
directory with similar capabilities and print a warning message. Applications
should use this directory for communication and synchronization purposes and
should not place larger files in it, since it might reside in runtime memory and
cannot necessarily be swapped out to disk."

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

On 10/28/2017 3:26 PM, Brian Inglis wrote:
> On 2017-10-28 12: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.
> 
> Normally set to /run/user/$(id -u)/, sometimes .../$(id -un)/, created by first
> app after login.
> I have a postinstall script to create /run/{,blkid,lock,user}/ directories with
> mode a+rwxt, remove /var/{run,lock} directories and create symlinks from those
> to /run/{,lock}/, to provide a more normal Unix/Linux environment for ported apps.
> 
>  From https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html:
[...]

Thanks for all the information, Brian, but I think you misunderstood the 
context of my question.  I'm the maintainer of xpdf, and Yaakov 
suggested a modification to my .cygport file.  This results in a warning 
(presumably when xpdf is not run under a desktop environment).  I'm 
simply asking if there's an easy way to suppress the warning so that 
users aren't annoyed by it.

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

Re: [PATCH xpdf] Add desktop menu entry

[Brian Inglis]

On 2017-10-28 13:55, Ken Brown wrote:
> On 10/28/2017 3:26 PM, Brian Inglis wrote:
>> On 2017-10-28 12: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.
>>
>> Normally set to /run/user/$(id -u)/, sometimes .../$(id -un)/, created by first
>> app after login.
>> I have a postinstall script to create /run/{,blkid,lock,user}/ directories with
>> mode a+rwxt, remove /var/{run,lock} directories and create symlinks from those
>> to /run/{,lock}/, to provide a more normal Unix/Linux environment for ported
>> apps.
>>
>>  From https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html:
> [...]
> 
> Thanks for all the information, Brian, but I think you misunderstood the context
> of my question.  I'm the maintainer of xpdf, and Yaakov suggested a modification
> to my .cygport file.  This results in a warning (presumably when xpdf is not run
> under a desktop environment).  I'm simply asking if there's an easy way to
> suppress the warning so that users aren't annoyed by it.

It's part of the desktop environment support, even if that is only dwm, so I
don't think you can eliminate the message, except by exporting
XDG_RUNTIME_DIR=/run/user/`id -u` or equivalent for it to use; you may have to
create it.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: [PATCH xpdf] Add desktop menu entry

[Yaakov Selkowitz]

[-- Attachment #1.1: Type: text/plain, Size: 832 bytes --]

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.

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

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

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

On 11/3/2017 9:11 AM, Ken Brown wrote:
> 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.

As a (temporary?) workaround, I've added the *.pfb files from the old 
ghostscript-fonts-std-8.11-1 package to urw-base35-fonts.  If I find out 
that Fedora has a better way of handling it, I can always change this.

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

Re: [PATCH xpdf] Add desktop menu entry

[Yaakov Selkowitz]

[-- Attachment #1.1: Type: text/plain, Size: 1697 bytes --]

On 2017-11-03 12:05, Ken Brown wrote:
> On 11/3/2017 9:11 AM, Ken Brown wrote:
>> 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.
> 
> As a (temporary?) workaround, I've added the *.pfb files from the old
> ghostscript-fonts-std-8.11-1 package to urw-base35-fonts.  If I find out
> that Fedora has a better way of handling it, I can always change this.

This needs to be properly fixed in xpdf itself:

https://bugzilla.redhat.com/show_bug.cgi?id=1509862

The patch I posted there *appears* to work, but hasn't been tested much yet.

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [PATCH xpdf] Add desktop menu entry

[Ken Brown]

On 11/6/2017 4:48 AM, Yaakov Selkowitz wrote:
> On 2017-11-03 12:05, Ken Brown wrote:
>> On 11/3/2017 9:11 AM, Ken Brown wrote:
>>> 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.
>>
>> As a (temporary?) workaround, I've added the *.pfb files from the old
>> ghostscript-fonts-std-8.11-1 package to urw-base35-fonts.  If I find out
>> that Fedora has a better way of handling it, I can always change this.
> 
> This needs to be properly fixed in xpdf itself:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1509862
> 
> The patch I posted there *appears* to work, but hasn't been tested much yet.

It appears to work for me too.  Thanks.

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