Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2023-12-18 Thread Vincent Lefevre
On 2023-12-18 23:58:24 +0100, Florian Schlichting wrote: > I'm wondering if there's anything left to do in xpdf here, or if I can > close this bug now? The original segfault is fixed and the font setting > much improved. In my testing it's still possible to confuse Motif with > using different

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2023-12-18 Thread Florian Schlichting
Hi Vincent and Adam, On Wed, Dec 01, 2021 at 08:23:07PM +, Adam Sampson wrote: > (in the original report) > > Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > > On Fri, Oct 22, 2021 at 02:34:44AM +0200, Vincent Lefevre wrote: > > And if I give an explicit UTF-8 font

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-12-01 Thread Vincent Lefevre
On 2021-12-01 20:23:07 +, Adam Sampson wrote: > On Fri, Oct 22, 2021 at 02:34:44AM +0200, Vincent Lefevre wrote: > > I'm also wondering how Xft fonts can be used. Syntax like > > xft:Bitstream:size=9 (as used by fvwm) doesn't work. > > I've just made some changes to the xpdf man page to

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-12-01 Thread Adam Sampson
(in the original report) > Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set On Fri, Oct 22, 2021 at 02:34:44AM +0200, Vincent Lefevre wrote: > And if I give an explicit UTF-8 font such as > Xpdf*font: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1 > I get

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-21 Thread Vincent Lefevre
On 2021-10-22 02:34:44 +0200, Vincent Lefevre wrote: > Thanks for the quick fix, but there is still an issue. The segfault > is gone, and the chosen font is taken into account, but if a > Xpdf*font resource is given (even with a non-existing font, > such as "foo"), the printed contents is

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-21 Thread Vincent Lefevre
Hi Florian, On 2021-10-21 15:08:51 +0200, Florian Schlichting wrote: > I've just uploaded xpdf 3.04+git20211021-1 including this fix (thanks > Adam!). Can you confirm that it fixes this issue? Thanks for the quick fix, but there is still an issue. The segfault is gone, and the chosen font is

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-21 Thread Florian Schlichting
Hi Vincent, On Thu, Oct 21, 2021 at 01:17:32AM +0100, Adam Sampson wrote: > On Tue, Oct 19, 2021 at 02:49:40PM +0200, Vincent Lefevre wrote: > > Xpdf*font: foo > [...] > > $ xpdf > > Warning: Cannot convert string "foo" to type FontStruct > > Segmentation fault (core dumped) > > I've been able

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-20 Thread Adam Sampson
On Tue, Oct 19, 2021 at 02:49:40PM +0200, Vincent Lefevre wrote: > Xpdf*font: foo [...] > $ xpdf > Warning: Cannot convert string "foo" to type FontStruct > Segmentation fault (core dumped) I've been able to reproduce the crash -- it's occurring in Motif when xpdf tries to create the text widgets

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-19 Thread Vincent Lefevre
Control: retitle -1 xpdf: segmentation fault in case of existing Xpdf*font X resource On 2021-10-19 14:49:40 +0200, Vincent Lefevre wrote: > When an incorrect Xpdf*font X resource is used, xpdf segfaults. Actually it doesn't even need to be incorrect... > For instance, I have the XAPPLRESDIR

Bug#996832: xpdf: segmentation fault in case of incorrect Xpdf*font X resource

2021-10-19 Thread Vincent Lefevre
Package: xpdf Version: 3.04+git20211001-1 Severity: normal When an incorrect Xpdf*font X resource is used, xpdf segfaults. For instance, I have the XAPPLRESDIR environment variable set to $HOME/.app-defaults, and in this directory, if the "Xpdf" file contains Xpdf*font: foo I get $ xpdf